How Clinky handles your data. The app is offline-first with no accounts, so your meet-ups and friends stay on your device.
Clinky ("the app", "we", "us") is an iOS application developed by an individual developer based in Belarus. Clinky helps friends see each other more often and have a good time together. It remembers who you met and when, offers question games for get-togethers, and adds a coffee or tea cup to your collection for every meeting.
If you have any question about this policy or your data, contact us at [email protected].
The core content you create in Clinky never leaves your device through us. It is stored in a local database inside the app’s private container on your iPhone. This includes:
We have no copy of this data, no ability to read it remotely, and no way to recover it for you. If you delete the app, this data is removed from your device.
To run subscriptions, understand how the app is used, and fix crashes, the app sends limited data to three processors. We instruct them to process data only on our behalf.
When you view the Clinky Pro paywall, purchase, or restore a subscription, the Adapty SDK communicates with Adapty’s servers. Adapty processes, by its design: an anonymous Adapty profile identifier, App Store transaction / receipt data, your subscription state, and standard device, locale and storefront information. The Adapty SDK can also access device identifiers such as the IDFV (vendor identifier) and your IP address.
TelemetryDeck receives aggregate, anonymous usage events (for example: app opened, meeting created, paywall shown), with parameters limited to bucketed counts, types and flags. The app does not send your typed text, friend names, contact identifiers, or any raw IDs in these events. The TelemetryDeck SDK additionally generates its own anonymized, salted-and-hashed identifier (not reversible, not shared across apps) plus device/OS/app-version metadata. TelemetryDeck does not store IP addresses. By the vendor’s own assessment, the data it handles falls outside GDPR/CCPA scope; we nonetheless disclose it here for transparency.
Sentry receives crash and error reports: stack traces, breadcrumbs (such as navigation and lifecycle events), and device / OS / app-version metadata, plus a per-install random identifier. We have configured Sentry to not send personal information by default (sendDefaultPii = false) and to strip user data from events. We do not attach your identity to crash reports.
Purchases are handled by Apple via the App Store / StoreKit, and are governed by Apple’s privacy policy. Planned meetings you choose to save go into your own Apple Calendar (see Section 6).
If you join the waitlist or write to us on clinkyapp.com, we keep the email you enter (for support messages, also your name and message), the country and city your request comes from, your browser and type of device, the site that sent you to us, and a short summary of the visit: the first page, how many pages and cards you looked at and the time spent on the site. We use this only to write to you about Clinky and to see, in total, where visitors come from. It is stored in a private Google Sheet, emails are sent through Resend, and Cloudflare Turnstile checks the forms against spam.
The website also counts anonymous usage: which pages and question cards are opened and how long they stay on screen. These counts carry no email, name or IP address, use no cookies and are kept by Cloudflare. The clink counter on the home page runs on the Abacus service. To have your data deleted, write to [email protected].
Clinky does not track you in the App Store sense: there is no IDFA / advertising identifier, no AppTrackingTransparency prompt, no ad networks, and no data brokers. Adapty processes the IDFV (vendor identifier) as disclosed in Section 4.1 — this is a per-vendor device identifier, not an advertising identifier and not a cross-app tracking signal. None of the services above are configured to track you across other apps or websites. We do not sell or share your personal information.
Each permission is optional and is used only for the purpose described. iOS will ask before any permission is granted, and you can change or revoke each one at any time in iOS Settings → Clinky.
Clinky is rated 12+ in the App Store. This is a content rating, not a data-processing age. Separately, we do not knowingly process personal data of anyone below the applicable digital-consent age in their country (which is 13 to 16 depending on the jurisdiction, 16 by GDPR default). The app is not directed to children. If you believe a child has used the app, contact us at [email protected] and we will help with deletion where applicable. Note that most of the app’s data is on-device only and under your control.
If you are in the European Economic Area or UK, we rely on:
If you are in the EEA / UK (GDPR): you have the right to access, rectify, erase, restrict, port, and object to processing, to withdraw consent, and to lodge a complaint with your local data protection authority.
If you are in California (CCPA/CPRA): you have the right to know what we collect, to delete and correct it, to opt out of "sale" or "sharing" (we do neither), to limit use of sensitive personal information, and to not be discriminated against for exercising these rights.
Important limitation (GDPR Art. 11). Because Clinky has no accounts and your core data is stored only on your device, and because the data shared with our processors is anonymized or pseudonymized (anonymous Adapty profile, hashed TelemetryDeck ID, scrubbed Sentry events), we generally cannot identify a specific individual’s records within that processor data. Where we cannot identify you from the data we hold, we may be unable to act on an access, correction or deletion request for that processor data, and we may ask you for additional information to enable identification, or decline where identification remains impossible. The primary and most effective way to delete your data is on-device: delete a friend, a meeting, or the entire app at any time. For matters within our control, contact us at [email protected]. We do not sell or share your personal information.
You can stop most off-device data sharing by revoking permissions in iOS Settings, by turning off analytics consent in the app (where offered), or by uninstalling the app. To make a request regarding data held by our processors, email [email protected], noting the identification limitation described in Section 9.
The developer (the data controller) is based in Belarus, which is outside the EEA and is not covered by an EU adequacy decision. This means that personal data of EEA users is processed by a controller located in a third country without adequacy. We address this through the data-minimization described in this policy (no accounts, on-device-only core data, anonymized/pseudonymized processor data) and, where required, appropriate safeguards.
Our processors operate servers in the EU and/or the United States. Where data is transferred outside the EEA/UK to a processor, we rely on appropriate safeguards such as the EU–US Data Privacy Framework (where the processor is certified) and Standard Contractual Clauses (SCCs).
EU representative (GDPR Art. 27). Clinky is operated by an individual developer and processes only minimal, anonymized or pseudonymized data through the processors described above. We have not appointed a representative in the Union under Article 27; if that changes, we will name our representative here. You can contact us directly about any data matter at [email protected].
Your core data stays on your device, protected by iOS. Data sent to our processors is transmitted over encrypted (HTTPS) connections. No method of transmission or storage is 100% secure, but we keep the data we share to a minimum.
We may update this policy from time to time. We will change the "Last updated" date above and, for significant changes, provide a notice in the app or on the policy page. Continued use after an update means you accept the revised policy.
Questions or requests: [email protected]