FlickerTalk

Security

Privacy depends on both what we encrypt and what we choose not to keep. FlickerTalk uses established cryptographic protocols and libraries, keeps no activity logs and publishes its app and server source code for inspection.

Building blocks

No trackers

No advertising, analytics of our own, third-party crash-reporting services or activity logs in FlickerTalk. The Translator tool translates on the 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. On iPhone the translation is done by iOS. This website also uses no cookies or trackers and keeps no access logs. The trailer on the home page is a YouTube player in privacy-enhanced mode: Google sees that your browser loaded it.

Threat model

FlickerTalk is designed to protect against a breach of our database, anyone running our servers reading chats, central collection of messages, exposure of a cloud history (we keep none, and a backup in your own Google Drive is encrypted on your phone), and push services reading messages.

It cannot fully protect against a compromised phone or operating system, malware, screenshots, the people you write to copying messages, someone holding your unlocked phone, or network metadata held by third parties. How it works lists who can see what.

Open source

The app and the server are published under the AGPL-3.0 licence.

Report a security issue

Please report suspected security vulnerabilities privately through the app or server repository's “Report a vulnerability” option, or by email to info@flickertalk.com.

Include the affected version and steps to reproduce the issue where possible. Do not include private conversations, private keys or other people's personal information.

We do not keep activity logs and cannot reconstruct a user's past conversations or connections.