Privacy policy
Effective 15 November 2026
FlickerTalk does not store conversations, address books, private keys or communication histories on its servers. Messages that cannot be delivered directly are kept encrypted end to end, so that we cannot read them, only until they are delivered or expire. The service keeps only the minimum technical information needed to route notifications and deliver those pending messages.
1. Who is responsible
The controller of your data is ERPLORA CLOUD SL, NIF B27593136, Avda. de Lisboa, 17, Pta. C, 28822 Coslada (Madrid), Spain. Contact: info@flickertalk.com.
2. What stays on your device
Your chat history, call history, contacts and the names you give them are stored on your device. Messages and files you send are transmitted to the person you choose, and messages in a circle to each of its members; undelivered messages may temporarily wait on our server, end-to-end encrypted, as described below. We do not keep a backup of your history or a copy of your private key. When you use “Move to a new phone”, your identity and history go directly from your old phone to your new one, never through our servers.
In a circle (a small, closed group of contacts), every member of the circle receives your contact card, the same one you hand over when someone scans your code: your FlickerTalk ID, the name on your card, your public keys and the routing code that lets their phone reach yours. A member who is not your contact can therefore write to you; their message arrives as a request, and they cannot call you unless you accept them. When a member's phone connects directly to yours, it can see your public IP address. We keep no record of circles or of who is in them.
If you set up a backup (Settings → Backup), the app keeps a copy of your phone, with your history, your keys and your files, in your own Google Drive. It is encrypted on your phone before it leaves, and on another phone only the recovery phrase you choose opens it; the phrase is not stored anywhere, and we never see it. Google sees how many encrypted files there are, their sizes and dates, and that you use FlickerTalk, never their names or contents. Our server is not involved.
If you use the Translator tool, it translates a message or your draft on your phone. On Android the translator is Google's ML Kit, built into the app: the text stays on the phone. Google receives which languages are used and diagnostic data about the app, not the text. That diagnostic data includes the phone's model and system version, its country, language and time zone, the app's version, performance figures, error codes and identifiers for this installation of the app; Google uses it to configure and diagnose ML Kit and to measure how it is used. On iPhone the translation is done by iOS. Language packs are downloaded once, from Google or Apple, which see which language your phone asks for and its IP address, never the text.
FlickerTalk does not upload your phone's address book or ask for your date of birth.
3. Data our servers process
| Data | Purpose and legal basis | Kept |
|---|---|---|
| Device ID, public key and a hash of your routing code | Authenticate your phone's requests and let only your contacts reach you. Performance of the contract (GDPR art. 6.1.b). | Until you use “Erase this phone” |
| A list of coded values, one for each contact you have blocked, muted or turned calls off for | Not ring your phone when one of them calls. A value does not name the contact, and our server keeps nothing that would tell it who it is. Art. 6.1.b. | Until you undo it or use “Erase this phone” |
| Push token and provider, encrypted | Wake your phone when a message or call arrives. Art. 6.1.b. | Until you erase the phone, turn notifications off, or the provider says the token expired |
| Undelivered messages, end-to-end encrypted, without sender | Deliver them when your phone comes back. Art. 6.1.b. | Until picked up, at most 7 days; never in backups |
| IP address of an open connection | Route it and limit abuse. Legitimate interest in the security of the service (art. 6.1.f). | Not stored; the abuse limits use a salted hash held in memory for one minute |
| IP addresses seen by our relay and STUN servers | Connect two phones that cannot reach each other directly. Art. 6.1.b. | Not logged |
| Reports and emails you send us | Handle abuse reports and answer you. Art. 6.1.f. | As long as needed to handle them |
| Suggestions you send from the app | Read your ideas to improve FlickerTalk. Art. 6.1.f. | As long as needed to handle them; our server does not store them |
When someone calls you, their phone signs the request, so for that moment our server sees which FlickerTalk ID is calling which. It uses this only to check the list of coded values above, and does not store or log it. Messages are sent without that signature.
A report is an email you send from your own mail app to info@flickertalk.com, with only the evidence you choose to include.
A suggestion is what you write in the app under Settings → “Suggest something”. Our server forwards it by email to info@flickertalk.com without your name, FlickerTalk ID or IP address: the email carries only your text, the app version and the platform. The server does not store it. To limit how many each phone can send in a day, it counts them per FlickerTalk ID, in memory only, never on disk or in a log. Because we do not know who sent a suggestion, we cannot reply.
4. Who else takes part
- Hetzner Online GmbH (Germany) hosts our servers in its data centre in Falkenstein, Germany.
- Google (Firebase Cloud Messaging) delivers the wake-up notifications on Android, and Apple (Apple Push Notification service) on iPhone. They receive your push token and the time of each notification, never its content or sender.
- Google (ML Kit), on Android, if you use the Translator: it receives the languages used and the diagnostic data described in section 2, never the text.
- OVH (France) hosts the mailbox of info@flickertalk.com.
- Google Play and the App Store distribute the app and handle payments under their own privacy policies. We receive no payment data: your phone checks the subscription locally.
Google and Apple may process data outside the European Economic Area, under the safeguards they provide (the EU-US Data Privacy Framework or standard contractual clauses).
5. No tracking
No analytics of our own, and no advertising or crash-reporting services, in the app. On Android, the Translator uses Google's ML Kit, which sends Google the languages used and diagnostic data, never the text (section 2). This website sets no cookies, loads nothing from other sites except the trailer on the home page, and keeps no access logs. The trailer is a YouTube player in privacy-enhanced mode: Google sees that your browser loaded it, and YouTube's terms apply if you play it. This website counts how many times each tool or game package is downloaded, in totals per package, version and month, never linked to a person or device.
6. Your rights
You can ask for access to, rectification or erasure of your data, restrict or object to its processing, and ask for its portability (GDPR arts. 15 to 22). You can delete everything yourself in the app with Settings → “Erase this phone”. Because we do not know who you are, we will need your FlickerTalk ID (shown in the app) to find your record. Write to info@flickertalk.com.
You can also complain to the Spanish Data Protection Agency (AEPD), www.aepd.es.
7. Children
If you are under 14, you need your parent or guardian's permission to use FlickerTalk.
8. Security
End-to-end encryption, keys sealed by the phone's secure key store, signed requests, encrypted push tokens and no logs of content, identifiers or IP addresses. See Security.
9. Changes
If this policy changes, the new version will be published here with its date.