Privacy Policy

Wrapp, previously called Enigma X, is operated by Martekings OY (Business ID 3327882-6, Työpajankatu 17 A 207, 00580 Helsinki, Finland), which is the data controller for the processing described here. You can reach us at support@wrappapp.app.

1. The short version

• Your account is a cryptographic key pair generated on your device. We never ask for your name, email address or phone number to use the app.
• Your private keys, recovery phrase and encryption keys never leave your device. We cannot read your encrypted messages: not by policy, by design.
• Your typing is processed entirely on your device. The keyboard does not transmit keystrokes anywhere.
• Our servers do store some data to make the product work: your public address and public key, subscription tier, usage counters, reward balances, push tokens, a log of key exchanges between accounts, anything you write to our support chat, which setup steps you completed, and daily usage totals linked to your account. Section 4 lists all of it.
• The apps contain no advertising networks. Two exceptions are named plainly rather than buried: a purchase-attribution service in the iOS app when you subscribe (section 10), and analytics on this website if you accept them (section 9).

2. What we can never see

Private keys and recovery phrase. Generated and stored only on your device. They are never transmitted to us, and we have no mechanism to recover them for you.

The content of your messages. Text is encrypted on your device by the Wrapp keyboard before it enters the messenger you are using. The encrypted text travels through that messenger (WhatsApp, Telegram, SMS or any other), not through our servers. We never see your messages in either form, and the messenger sees only ciphertext.

Your keystrokes. The keyboard processes typing locally. Word suggestions and completions come from dictionary files shipped inside the app and are computed on the device. Release builds contain no keystroke logging. To make taps land where you aim, the keyboard can keep a small typing calibration: an average tap offset per keyboard layout (a few numbers, with no letters, words or tap history). It stays on your device and can be reset in the app.

Your address book. We never access the contact list on your phone. Contacts you add inside Wrapp are stored locally on your device.

Your identity. An account is a public address derived from a key pair. Unless you tell us who you are, for example in support chat, we do not know it.

3. Data processed only on your device

Encryption keys, the recovery phrase, your Wrapp contact list, message drafts, privacy mode text, received and decrypted files, the suggestion dictionaries and the keyboard's typing calibration. You can delete all of this at any time by deleting your account in the app or uninstalling it.

4. Data our servers store

To run the service we operate a backend, hosted on Supabase with media files on Amazon Web Services. It stores the following, keyed to your public address:

Account record

Public address, public key, subscription tier and its expiry date, app version, interface language, last sync time, usage counters such as how many times encryption was used against your plan's limit, reward and token balances, your referral code and, if you signed up through one, the referring account, and in-app quest progress.

Key-exchange log

When you exchange encryption keys with a contact, the key itself is sealed to the recipient's public key and we cannot read it. The record of the exchange (sender address, recipient address and time) is stored in readable form and kept while your account exists. This is what makes account recovery possible: a restored device rebuilds its contact list and regains access to its own history from this log. Stated plainly: we hold metadata about which Wrapp accounts exchanged keys with each other and when. We do not hold the content of any conversation.

Devices and push tokens

A push notification token for your device (see section 8) and a device record used to enforce the one-device-per-account model, including authentication challenges signed by your key.

Encrypted media

Voice messages and media attachments are encrypted on your device and uploaded to cloud storage; recipients fetch them through time-limited links. The storage holds ciphertext, and the decryption key travels inside your encrypted message, which we cannot read. The file's name and type are not encrypted: they are sent to our media server in readable form when a file is uploaded and downloaded. If a file name is itself sensitive, rename the file before sending it.

Support chat and reports

Messages and attachments you send to our in-app support chat or through "Send a report" are readable by our support team; that is what they are for. We receive your message, the app version and, only if you enter it, your email address, which we use only to answer that report. They are stored linked to your public address and are not end-to-end encrypted. Please do not include sensitive information you would not want us to see.

Crash reports (Android)

After a crash the Android app can offer to send a report. It is sent only if you tap Send. It contains a technical description of the crash and is linked to your public address if you already have an account. It does not contain your messages or keys.

Subscription linkage

When you subscribe, we link the store transaction to your public address so that your tier follows your account. We never see your payment details (see section 7).

Setup progress

To find out where people get stuck setting up Wrapp, the app records which setup and tutorial steps you reached, for example "keyboard setup screen shown", "tutorial step 3 completed" or "tutorial skipped", with the time, the app version and your platform. These records carry a random installation identifier created by the app on first launch; once you have an account, they also carry your public address. They never contain anything you type, your messages, your keys or your clipboard. The installation identifier is not your device's advertising identifier (IDFA) and is not derived from it; it changes if you reinstall the app or erase your account in the app. Setup records are deleted automatically after 12 months.

Usage statistics

To understand how the app is used, the app and the keyboard count a few daily totals on your device: for example how many times the keyboard was opened in each mode, how many characters were typed and messages sent in each mode, how often encryption was switched on, how many messages were decrypted, how many voice messages, videos, photos, files and locations were sent, and how often word suggestions and corrections were used. Only the totals per calendar day leave the device, together with the platform, app version, interface language, subscription tier and whether the keyboard is enabled. They are sent together with your public address, so they are linked to your account. They never contain what you type, your messages, your contacts or your keys, and no times within the day.

Sending these statistics is part of how the app is provided and improved and is described in our Terms of Use (section 11); there is no separate setting to turn it off. Deleting your account in the app ("Logout and clear") deletes the totals still stored on your device; the records on our servers are deleted when you ask us to delete your account (see section 11). Daily records are deleted after 13 months in any case; totals across all users, which describe no individual, may be kept longer. Statistics sent by app versions before 22 October 2026 carry a random identifier instead of the address and cannot be linked to an account.

5. Device permissions and location

Each permission is requested when you use the feature that needs it, and everything else in the app works without it.

• Microphone: to record voice messages, which are encrypted on your device.
• Camera (Android): to scan a contact's QR code when adding them in person.
• Photos (iOS): to pick media to send and to save received media.
• Notifications: for the push notifications in section 8.
• Location: see below.

Sending your location is optional and happens only when you tap the location button and grant the operating system's location permission. The app takes a single fix at that moment; there is no background tracking. The coordinates are encrypted on your device into the message like any other text and are not sent to our servers. When a recipient opens a received location, the coordinates are handed to the maps application on their device.

6. The keyboard and "Full Access"

On iOS the system asks you to grant the keyboard "Full Access"; Android shows a similar warning when you enable a third-party keyboard. Wrapp needs this so the keyboard can encrypt and decrypt on the device and exchange data with the main app, not to send your typing anywhere. Keystrokes are processed locally, dictionaries live on the device, and the keyboard uses the network only for the functions described in section 4, such as uploading an encrypted voice message.

7. Payments

Subscriptions are bought through the Apple App Store or Google Play. Payment is processed entirely by Apple or Google under their own privacy policies. We never receive your card number or billing details, only confirmation that a transaction took place, which we link to your account as described in section 4.

8. Push notifications

Delivery uses the platform push services: Apple Push Notification service and Google Firebase Cloud Messaging. These services receive a device token and, as with any network traffic, technical connection data. Notifications are delivery signals; they do not contain decrypted message content. The Firebase SDK in our apps is configured with analytics disabled.

9. This website

This section concerns visitors to wrappapp.app only. It is entirely separate from the apps: website analytics have no connection to your Wrapp account, your keys or your messages, and nothing in the apps reports to these services.

Analytics and cookies

We use Google Analytics to count visits and see which pages are read. It loads only if you choose Accept in the cookie banner. If you choose Reject or make no choice, no analytics script is requested and no analytics cookie is set. You can change your choice at any time with "Cookie settings" at the bottom of every page. The cookies are listed in our Cookie Policy.

If you accept, Google receives the pages you view, the referring page, browser and device information, your approximate location derived from your IP address, and a random identifier stored in a cookie. Google Signals and ad personalisation are turned off. Analytics data is kept for no longer than 14 months.

Search and hosting

We use Google Search Console to see how the site appears in Google Search. It gives us aggregated figures such as search terms and clicks, and places nothing on your device.

The site is hosted by Netlify, whose standard server logs (IP address, browser user agent and pages requested) may be kept briefly for security and operations. Fonts and images are served from this site itself, not from third parties. Links to the App Store and Google Play take you to Apple or Google under their own privacy policies.

Contacting us

This website has no accounts, contact form or newsletter. If you email us, we use your address and message only to answer you. If you subscribed to updates or used the contact form on our former website, ifonly.tech, what you submitted remains in the backend described in section 4 until you ask us to delete it.

10. Service providers

We use a small set of providers to run Wrapp: Supabase (database and server functions), Amazon Web Services (encrypted media storage), Google Firebase (push notification delivery), Apple and Google (app distribution and payments), Google Analytics (website analytics, only if you accept), GoMarketMe (iOS app only, purchase attribution: it receives store transaction confirmations and device information so that affiliate partners can be credited for subscription purchases, and never receives your messages, keys or account contents), Netlify (hosting for this website) and our email hosting provider (messages you send to our address).

They process data on our behalf under their own security and data-processing terms. We do not sell or rent any data to anyone, and we share data with no one else, except as required by law (see section 13). Some providers process data outside the EU and EEA, notably in the United States; where that happens, transfers rely on the safeguards those providers offer, such as the EU standard contractual clauses or the EU-US Data Privacy Framework.

11. Retention and deletion

• On your device: delete data at any time in the app, or by uninstalling it.
• On our servers: the records in section 4 are kept while your account exists, because they are what makes the account work and recoverable. The exceptions are setup progress records, which are deleted after 12 months, and usage statistics, which are deleted after 13 months or together with your account. Uninstalling the app does not by itself delete server records.
• Deletion on request: write to us from the app's support chat, or email us with your public address, and we will delete your account record, push tokens, support history and reports, crash reports, stored media, setup progress records, usage statistics and key-exchange log. After that, account recovery is impossible: we cannot restore what we no longer have. Step by step: Delete your account.

12. Security

All message encryption and decryption happens on your device, using AES symmetric encryption with public-key cryptography for key exchange. Keys are stored in the platform's secure storage and are never transmitted to us. Connections to our backend use TLS, and stored media is ciphertext. No system is perfectly secure and we do not promise otherwise, but we have designed the service so that the most sensitive data never reaches us at all.

13. What we could disclose if legally compelled

Because of the design above, the complete list of what we could produce in response to a lawful request is the server-side data in section 4: account records, the key-exchange metadata log, push tokens, support chat history and reports, crash reports, setup progress records, usage statistics, the names and types of stored files, and encrypted media we cannot decrypt. We cannot produce message content or keys, because we do not have them, and we know your identity only if you have told us who you are.

14. Age

You must be at least 18 to use the Wrapp apps (see section 4 of our Terms of Use). Wrapp is not directed at children and we do not knowingly collect data from them. If you are a parent and believe your child has provided us with personal information, please contact us.

15. Your rights and our legal bases

If you are in the EU or EEA, or another jurisdiction granting data-protection rights, you may request access to, correction of or deletion of the data we hold about you, restriction of or objection to its processing, and a portable copy. Contact us at support@wrappapp.app; we will need your public address to locate app data. You also have the right to complain to a supervisory authority: in Finland, the Office of the Data Protection Ombudsman (tietosuoja.fi), or the authority in your own country.

The legal bases we rely on are:

• Performing our contract with you for the data needed to provide the service: the account record, key-exchange log, devices and push tokens, encrypted media and subscription linkage.
• Our legitimate interests in understanding, improving and securing the service for usage statistics, setup progress, crash reports, support and reports, and server logs. You have the right to object to this processing at any time by writing to us.
• Your consent for website analytics, which you can withdraw at any time with "Cookie settings" at the bottom of every page.

16. Open source and acknowledgements

Wrapp builds on open-source software. In particular:

• Russian word frequencies: FrequencyWords by Hermit Dave, licensed CC BY-SA 4.0. The adapted word list ships inside the app and is likewise available under CC BY-SA 4.0. The dictionary is used entirely on your device.
• The Android app is built on FlorisBoard, licensed Apache 2.0. Its license and copyright notices are preserved, and the app's About screen includes the project license and a full list of third-party licenses.
• The iOS app uses open-source components under their respective licenses, including web3swift, CryptoSwift, swift-sodium, secp256k1.swift, BigInt, Lottie, Hero, MultipartFormData, and the Supabase, Firebase and Apple Swift libraries.

17. Changes to this policy

We will post updates on this page with a new "last updated" date, and announce material changes in the app before they take effect.

18. Contact

• Martekings OY, Business ID 3327882-6
• Työpajankatu 17 A 207, 00580 Helsinki, Finland
• Email: support@wrappapp.app, or the support chat inside the app