Your data

We do not use third-party advertising trackers. Where a feature does not need to know who you are, direct account identifiers are replaced with server-generated pseudonymous keys or combined into aggregate totals.

Personal details remain linked to your account only where that is necessary for sign-in, your profile, settings, social features, support, security, or another feature you actively use.

We do not give venue operators your identity, individual activity history, or location. They receive aggregate engagement totals only.

Tommy Szewczuk
Max-Brauer-Allee 8
22765 Hamburg
Germany

For privacy requests, contact takt@merou.de.

takt. processes the identity details needed for sign-in, such as your email address, name, and provider account identifier when supplied by Apple or Google.

The app stores the profile, favorites, attendance plans, friendships, feedback, and other settings you choose to create so those features work across your sessions.

Only after you grant location permission, takt. may store an approximate, coarsely rounded city presence for no more than six hours to match you with local Moments. The Nearby Moments setting controls those discovery notifications independently; location permission controls whether city presence can be recorded. Venue operators do not receive this location.

In the native app, if you separately enable background location for Pulse prompts, the operating system can monitor geofences around up to 20 relevant venues while the app is not open. takt. uses current precise location on the device to select and check those venue regions and can schedule a notification after a longer stay. It does not send a continuous location history to takt.; monitored venue regions and pending prompt state are kept in protected storage on your device and are removed when the feature is disabled or the account is deleted.

If you choose to confirm that you are still at a venue and submit a Pulse update, takt. requests a fresh precise location and sends the coordinates, accuracy, and observation time to the server. The server uses them to check that the update was made near the venue. Raw coordinates are not stored as account data; the derived distance, accuracy, observation time, and confidence may be stored as the limited presence proof needed for abuse prevention, rewards, and Pulse integrity.

Public profile information is shown only according to the visibility settings and relationship rules available in the app.

takt. records first-party interactions such as venue and event profile views, favorites, RSVPs, ticket-link clicks, and directions clicks. Signed-in account identifiers are converted into server-side pseudonymous keys before analytics events are stored.

Raw engagement events are deleted after 91 days or when the associated account is deleted, whichever happens first. The pseudonymous browser-session keys used only to prevent duplicate sponsored impressions or clicks are deleted after the campaign's local reporting day ends.

Startup and Web Vitals diagnostics use a fixed product-area label instead of the page URL and do not include a metric identifier. Search terms for people and home cities are sent in private request bodies, used only to return the current result, and are not retained as search history by takt.

Venue operators receive aggregated reports only, including totals grouped by home city. They do not receive names, email addresses, pseudonymous visitor keys, session identifiers, exact locations, or an individual activity feed.

Applications contain your first and last name, email address, selected platform and device, optional operating-system version, optional motivation, consent time, and application decision.

If approved for iOS, takt. sends your name and email address to Apple through App Store Connect and stores the beta-tester identifier and invitation state needed to manage access. If approved for Android, takt. emails you links to join the private Google Group yourself, opt in to the closed Google Play test, and install the app. takt. does not add you to, inspect, or store your membership in that Google Group; it stores only the application, approval, email-delivery, and activation state needed to operate the beta.

Application data is visible only to takt. administrators and is retained while needed to operate the beta program. You can request its removal through the privacy contact above.

An Early Access request contains your name, email address, consent time, language, referral invitation if used, review decision, activation-email delivery state, and account-activation state.

Personally invited requests are marked as priority in the administrator review queue. This changes review order only; every account still requires a manual approval.

When approved, takt. sends a private activation link. If you choose Apple or Google, that provider identity is linked to the email-verified takt. account. Apple private-relay linking is performed only after your explicit consent. takt. does not silently merge accounts.

Early Access data is visible only to takt. administrators, is included in account-data requests, and is deleted with the activated account or upon a verified removal request.

Carefully selected service providers support sign-in, secure hosting and storage, media and map delivery, email, and beta distribution. They may process data only to provide those services for takt. and not for their own advertising.

Venue subscriptions and credit purchases made on the website use Stripe-hosted checkout. takt. stores the venue billing contact and legal name, Stripe customer and transaction identifiers, subscription state, purchased and granted credit balances, credit-ledger activity, campaign spending, and the records needed to handle checkout completion, refunds, disputes, and support. Payment-card or bank-account details are entered directly with Stripe and are not stored by takt. Native apps can display and use access or credits already assigned to a venue, but do not offer purchase or billing-management controls.

Account and app data is retained while your account and its features remain active, and longer only where necessary for security, abuse prevention, operational records, or legal obligations.

While signed in, you can download a machine-readable copy of your personal data or delete your account with a 30-day recovery window. You may also request access, correction, restriction, portability, objection, or deletion through the privacy contact. Some data may need to be retained where a legal obligation applies.

Venue operators and takt. administrators can connect professional Facebook, Instagram, or WhatsApp Business accounts for event distribution. takt. stores encrypted provider access credentials, the selected business destination, publishing history, and delivery or insight records needed to operate that connection. Disconnecting disables publishing and revokes the stored credentials. Meta data-deletion requests remove the connection credentials, destination configuration, and associated provider publication records.