Privacy policy

Fjord Studio ("we", "us", "our") values your privacy. This privacy policy explains how we collect, use and protect personal data when you use the Reread Android app ("Reread" or "the app") and this website.

Reread helps with messages. Decode shows what a message you received likely means, why, and three replies you could send. Check shows how a draft of yours is likely to land with its reader, which phrases cause it, and three fixes.

This policy explains what Reread sends, what stays on your phone, who processes data on our behalf, how long it is kept, your rights, and how to contact us. Fjord Studio is a trading name of Langsæter Labs, a sole proprietorship registered in Norway, so the EU General Data Protection Regulation (GDPR) applies, and the UK GDPR applies to users in the United Kingdom. Langsæter Labs is the data controller. You can contact us any time at support@getreread.app.

1Summary (the short version)

2What data we collect and why

2.1Messages you decode

When you share a message or a screenshot to Reread, choose a screenshot in the app, or paste a message, Reread reads it on your phone. Screenshots are read by on-device text recognition (Google ML Kit, which runs on the phone) and are never uploaded or saved; only the text Reread finds in them is used.

To decode, Reread sends up to 12 messages of the conversation (3,000 characters in total), including messages the other person wrote, after masking them on your phone (see 2.3). With them it sends which messages are yours and which are theirs, the sender type you pick (for example manager, landlord or family) and, if you saved one in People, your masked note about that sender (see 2.4). Only share conversations you're allowed to share (see Section 3).

Reread reads the clipboard only when you tap a Paste button in the app, the Reread tile or the Check copied text shortcut (the tile and the shortcut check your own copied text, see 2.2). It never reads the clipboard in the background.

2.2Drafts you check

When you select text and pick Reread from the text-selection menu, share text to it, paste or type into it, copy your draft and tap the Reread tile in Quick Settings, or use the Check copied text shortcut, Reread masks the text on your phone and sends it (up to 1,500 characters) to our server.

With every check or decode we also send the settings that shape the result: the reader or sender type, your masked note about them from People if you saved one (up to 80 characters), whether English is your first language, the kind of app you're writing in (work chat, email, messaging or other, never the app's name), the list of placeholders used in the masked text (for example [PHONE_1]), the app version and a random request ID. For the free preview it also sends the app's Firebase Installation ID, which our server stores only as a one-way hash (see 2.9).

Results are shown on your phone. Reread keeps your last 50 results in History on your phone, never on our servers (see 2.6).

Legal basis (2.1 to 2.4): performance of our contract with you, to provide the result you asked for (GDPR Art. 6(1)(b)). Before the first message is sent, Reread asks you to agree to AI processing; you can withdraw that at any time in Settings → Privacy and data → AI processing. Without it Reread can't check or decode messages, but the rest of the app keeps working and your subscription isn't affected.

Note on sensitive data: messages, and notes you save in People, can contain sensitive details about you or others (for example health, sex life, relationships or beliefs). You decide what to send, and we ask you to leave such details out unless the result needs them. They're processed only to produce the result you asked for and are not stored by us. For sensitive details about yourself, the legal basis is your explicit consent (GDPR Art. 9(2)(a)): the AI processing screen names these details (health, sex life and beliefs) and asks you to agree explicitly to Reread processing them, and you give that consent by accepting it and then choosing to send the text. If you accepted an earlier version of that screen, which didn't name them, Reread asks you again before it sends anything. You can withdraw it at any time in Settings → Privacy and data → AI processing. For details about other people, see Section 3.

2.3Masking on your phone

Before anything is sent, Reread looks for private details in the text on your phone and replaces them with placeholders such as [PHONE_1] or [EMAIL_1]. It does this in two layers, both on the phone; nothing is sent to do either. The first is a set of fixed patterns, which always runs and catches details written in common formats:

• phone numbers of 9 to 15 digits, email addresses and web links;
• street addresses written as a house number, up to three capitalised words and a street word such as Street, Road, Avenue or Lane (for example "14 Harbour Road"); UK and Canadian postcodes; and US ZIP codes and Australian postcodes written after a state;
• card numbers, IBANs, UK sort codes and other numbers of 8 digits or more, such as account numbers;
• UK National Insurance numbers and US Social Security numbers;
• codes of 4 to 8 digits near a word such as "code", "PIN" or "password", and UPS tracking numbers.

The second is Google ML Kit's entity extraction, a small model that runs on the phone. Reread downloads it (about 6 MB) after you first open the app and uses it when it's there and answers within 1.5 seconds. It looks for addresses, phone numbers, email addresses, card numbers, IBANs, web links, parcel tracking numbers and flight numbers, including some the patterns miss, such as a street address written in lower case. When the model isn't available, the patterns and names still run. It looks only at the message or draft itself: your note about someone and the note in a report are masked with the patterns and saved names.

Names you saved in People, and the name you give for the person you're writing to, are replaced too (with [READER] for the person you're writing to, and [NAME_1] and so on for the others). Before sending, Reread runs the same patterns over the masked text; if anything is left, or masking fails, nothing is sent. When the result comes back, Reread puts the original details back on your phone.

What masking may miss: details written another way, especially when the ML Kit model isn't available, for example a street address in lower case ("12 high street"), with an ordinal or an apostrophe in the street name ("57th Street", "O'Connell Street") or without a house number; short local phone numbers ("555-0123"); other names in the text, such as a name in a screenshot or a greeting like "Hi Tom"; and other details that can identify someone, such as an employer, a school or a place. Amounts of money and dates are deliberately left as they are, because they matter to how a message reads. These are sent as written, so check what you share.

2.4People: names and notes

In Settings → People you can give each of the eight reader types (manager, coworker, client, recruiter, landlord, co-parent, family and date) an optional name and an optional note of up to 80 characters, choose a default reader, and pick up to three to show in Android's share menu. All of this is stored only on your phone.

• Names are never sent. Results can say "How Dana hears it" on your phone, but before anything leaves it, every name you saved is replaced (see 2.3).
• Notes are sent, masked. When you check or decode for a reader you wrote a note about, the note goes with the request so the result fits the relationship. It's masked on your phone first, with the same fixed patterns and saved names as messages (the ML Kit layer looks only at the message): saved names are replaced, and details in the formats listed in 2.3 are hidden. Other names in the note are sent as written. Like your messages, it isn't stored on our servers.
• The reader you last picked in each app (for example in com.whatsapp), up to 20 apps, is remembered on your phone so Reread can preselect it next time. This list is never sent.

2.5AI processing by Google

Our server runs on Google Cloud (Cloud Functions for Firebase). It passes the masked text and settings to Google's Gemini models through Vertex AI and returns the result to your phone. Google processes them to produce your result and doesn't use them to train its models. Google may keep requests in a short-lived cache (up to 24 hours) to speed up responses, and may log requests flagged by its safety systems to check for abuse. We don't store your messages, notes or the results on our servers, and our server logs never contain message text.

2.6History on your phone

Reread keeps your last 50 checks and decodes in History, in a database on your phone. When there are more, the oldest goes first.

• What's kept: your draft (for a check) or their message and the conversation Reread read from a screenshot or paste (for a decode), the result as you saw it, the reader type and any name you saved for them, and the time. For a check it also keeps a masked copy of your draft (up to 300 characters).
• What isn't kept: results that showed a safety message, and the built-in examples. A locked free preview isn't in History: Home keeps it on your phone for its locked card (see 2.15), and it moves to History once you subscribe and it unlocks.
• It never leaves your phone. History isn't sent to us, a saved result re-opens offline without sending anything again, and it's excluded from Android cloud backup and device transfer.
• You decide: swipe a result away (with Undo), tap Clear all, or turn off Keep history on this phone at the top of History (Settings → History), which stops saving and deletes what's there, including a kept preview. Deleting your account in the app, clearing the app's data or uninstalling Reread deletes it too.

2.7Your anonymous account and Reread ID

When you first open Reread, Firebase Authentication creates an anonymous account ID for this installation. We don't collect your name, email address, phone number or password. Your Reread ID (a short code in Settings → Privacy and data) is derived from the account ID by a one-way calculation, so you can quote it when you contact us without sharing anything else.

If you uninstall Reread or change phones, you get a new anonymous account. A subscription bought with the same Google Play account comes back when you tap Restore. The old account isn't deleted by itself (see Section 6), so delete your account in the app before you uninstall if you don't want it kept.

Legal basis: performance of our contract with you (Art. 6(1)(b)).

2.8Settings and setup answers

We store with your account: your setup answers if you gave them (the kinds of people you write to and whether English is your first language), your AI processing consent (its version and when you gave or withdrew it), your usage-statistics choice, the app version, and your language and country. With usage statistics on, we also store Google Analytics' app instance ID and the campaign that led to your install, if any (see 2.11); turning usage statistics off removes both.

Why: to tailor results, to keep a record of your AI processing consent, and to support you. Legal basis: performance of our contract with you (Art. 6(1)(b)) and our legal obligation to be able to show consent (Art. 6(1)(c)); for the analytics fields, the same basis as usage statistics (see 2.11).

2.9Free preview, fair use and security

• Free preview: to give each person one free preview, our server stores a one-way hash of your account ID and of the app's Firebase Installation ID, with the time the preview was used. The hashes can't be turned back into the IDs and are deleted after 90 days.
• Usage counters: how many checks and decodes you ran each day (and the AI cost of each day), kept for 90 days, a short-term rate-limit record (recent request IDs and counters) and how many reports you sent that day, kept while your account exists. These never include message text. They enforce the fair-use limits and control costs. Our server also keeps daily totals of AI cost across all users, which aren't linked to anyone.
• App Check: Reread uses Firebase App Check with Google Play Integrity, so each request carries a short-lived Google token confirming it comes from the real app on a genuine device.
• Access codes: if you redeem an access code, we store which code was used (as a hash) and when your access ends.

Legal basis: our legitimate interest in preventing abuse of the free preview, keeping the service secure and affordable, and protecting it from automated use (Art. 6(1)(f)).

2.10Reports

If you report a result with Report this result, we store the report for about 90 days: the category you picked, your note if you wrote one (masked on your phone with the same patterns and saved names as the text, see 2.3), the mode (check or decode), the model and prompt version, the result's label, the app version and your account ID. The masked text and the result are included only if you tick Include the masked text so we can look at it. Other names in your note are sent as written, so please leave them out. The app sets the deletion date from your phone's clock, so a phone set to the wrong date can move it a little (we accept 80 to 100 days).

Legal basis: our legitimate interest in finding and fixing harmful or wrong results (Art. 6(1)(f)).

2.11Usage statistics, crash reports and performance data

Reread has two switches for this, both in Settings → Privacy and data: Share usage stats and Send crash reports.

Usage statistics (Google Analytics for Firebase) and performance data (Firebase Performance Monitoring) follow Share usage stats. Nothing is collected until you've made your choice on the setup screen. In the EU and the EEA (including Norway, Iceland and Liechtenstein), the United Kingdom and Switzerland the switch starts off, so nothing is collected unless you turn it on. Reread counts your phone as being there if its SIM card, mobile network or language settings point to one of these countries, or if it can't tell. Elsewhere it starts on, and you can turn it off there or at any time later. When it's on, Reread sends:

• Events about how the app is used, described only by codes, counts and timings. For example: which setup step or screen you saw, how Reread was opened (share, text menu, tile or shortcut), the kind of app you opened it from (messaging, email, social, browser, work or other, never the app's name), the reader type, a result's tone label and score, how long a result took, whether the plans were shown and which plan you tapped, purchase and restore results, and your choices in the post-purchase setup, including your answer to "Where did you find Reread?" if you give one.
• User properties: your main reader type and whether English is your first language (from setup), whether the Reread tile is added and notifications are allowed, your consent version, the kind of app you use Reread from most and whether it supports Replace, your subscription state and plan, the plan and preview layout you were shown, the campaign that led to your install (see below), a rough device tier (low, mid or high, worked out from memory and processor cores, never the model), and whether it's a test build.
• A pseudonymous user ID: the first 32 characters of a one-way hash (SHA-256) of your anonymous account ID, never the account ID itself, so events from your installation can be counted together.
• What Google Analytics adds itself: an app-instance identifier, device and app information, and an approximate location derived from your IP address.
• Performance data: speed measurements, such as how long the app took to start and a result took to arrive, with device, app and network details and the Firebase Installation ID.

Usage statistics and performance data never include message text, screenshots, the names or notes you saved, or purchase tokens.

Install attribution: once per install, Reread reads Google Play's install referrer, which says which campaign, if any, led to the install. It keeps only the source, medium, campaign and content fields and, if Google Play gives one, the time of the click (never ad click IDs), on your phone. They go to Google Analytics only while usage statistics are on. While they're on, we also store the four campaign fields (not the click time) and Google Analytics' app instance ID with your account, so subscription events our server records can be matched to the app's statistics. Our server may record those events (such as a trial starting or a plan renewing) in Google Analytics with the same pseudonymous user ID, never your account ID itself, and only while usage statistics are on.

Turning usage statistics off stops collection straight away and removes the app instance ID and campaign fields from your account. Deleting your account in the app also resets this installation's analytics data and deletes its Firebase Installation ID, but it doesn't erase statistics already sent (see Section 6). Reread doesn't collect the advertising ID, keeps Google's advertising consent settings denied, and uses this data only to understand and improve the app, never for ads.

Crash reports (Firebase Crashlytics) follow Send crash reports. In the EU/EEA, the UK and Switzerland, they follow your usage-statistics choice until you set this switch yourself, so nothing is sent before you say yes. Elsewhere the switch is on, from the first launch, until you turn it off. When the app crashes, it sends a report: the stack trace, device model, Android version, app version and a Crashlytics installation identifier. Turning the switch off applies from the next time Reread starts and deletes reports still waiting on your phone. Firebase Sessions, which Crashlytics and Performance Monitoring use, notes when a session starts so crash-free and speed figures can be worked out; it sends nothing while both crash reports and usage statistics are off. Crash reports and performance data aren't linked to your account ID and never include message text.

Legal basis: usage statistics, performance data and install attribution: in the EU/EEA, the UK and Switzerland, your consent (Art. 6(1)(a), and the rules on storing and reading information on your device, such as Art. 5(3) of the ePrivacy Directive); elsewhere, our legitimate interest in improving Reread, with the switch to opt out at any time (Art. 6(1)(f)). Crash reports: in the EU/EEA, the UK and Switzerland, your consent, on the same terms; elsewhere, our legitimate interest in finding and fixing crashes (Art. 6(1)(f)), and you can object at any time by turning off Send crash reports.

2.12App and server settings (Remote Config)

Reread gets some of its settings from Firebase Remote Config: for example how soon the plans appear over a free preview, which preview layout to show, the order of the post-purchase setup steps, and switches that pause Decode or show a maintenance message. The app fetches them when you open it. The request identifies the installation by its Firebase Installation ID, with basic app and device details (such as the app version, language and country) and, while usage statistics are on, the analytics user properties in 2.11, so a setting can go to a group of users. It carries no message content and not your account ID.

Our server reads its own settings (usage limits, switches and cost limits) from Remote Config too. To give a setting to a share of users, it uses your account ID in the server's memory only; the ID isn't sent to Remote Config or stored. These settings contain no personal data.

Legal basis: our legitimate interest in running Reread reliably and changing its settings without an app update (Art. 6(1)(f)).

2.13Subscription and purchase data

Purchases go through Google Play Billing. Google processes your payment; we never see your card or payment details. So a purchase can be matched to your Reread account, the app gives Google Play a one-way hash of your account ID. Our server checks each purchase with Google Play and Google Play notifies it of renewals, cancellations and refunds. We store: the purchase token and order number, plan and offer, start, renewal and expiry dates, whether it's a trial or test purchase, the country of purchase, cancellation and refund status, and your cancellation reason if you gave one to Google Play.

When you delete your account, your purchase records are unlinked from it and reduced to what we need to handle refunds, chargebacks and abuse (the purchase token and order number, the plan, its dates and status, any refunds and, if you used Reread that day, the day's usage counts, so restoring the purchase the same day doesn't reset the daily limit), and kept until the subscription's expiry date plus 90 days (or, for a paused subscription that resumes later, its resume date plus 90 days). See Section 6.

Legal basis: performance of our contract with you (Art. 6(1)(b)); after deletion, our legitimate interest in handling refunds, chargebacks and fraud (Art. 6(1)(f)) and our accounting obligations (Art. 6(1)(c)).

2.14Notifications, calendar, tile and share shortcuts

After a purchase, Reread may show a short setup, once, with steps you can skip. Everything it sets up stays on your phone.

• Trial reminder: Reread asks for permission to show notifications, so it can remind you the day before a free trial ends. The reminder is scheduled on your phone; we don't use push notifications or store a notification token. While a trial runs, you can turn reminders off in Settings → Trial reminders.
• Add to calendar: if you don't allow notifications, Reread can open your calendar app with a reminder for the trial's end filled in, which you save there yourself. Reread doesn't ask for calendar permission and can't read your calendar.
• Quick Settings tile: Reread can ask Android to add the Reread clipboard tile (on Android 13 and later), or show you how to add it. The tile reads the clipboard only when you tap it.
• Share shortcuts: you can pin up to three reader types to Android's share menu (Direct Share). They're labelled by role only, like Manager or Landlord, never with a name you saved, because share menus can appear in screenshots and screen recordings. Android decides which of them appear. You can change them in People.
• Where did you find Reread? An optional question. Only your answer's code goes to usage statistics, and only while they're on.

2.15Other data kept on your phone

Some data is kept only on your phone to run the app: History (see 2.6); a locked free preview for Home's card (your text, the reader and the parts of the result the preview showed in full), until it unlocks, you clear History or turn it off, or you delete your account; your names, notes, default reader and the reader last picked in each app (see 2.4); your setup answers, your consent choices and your usage-statistics and crash-report switches; the reader you picked while practising in setup and the name you typed for them, if any; a cached copy of your subscription status; the trial reminder's date and price, and whether reminders are on; your theme, colour-blind friendly colours and Reduce motion choices; whether the post-purchase setup was shown, whether the tile is added and which share shortcuts are pinned; your install's campaign fields from Google Play (see 2.11); the Remote Config settings last fetched; and small counters, such as how often you opened Reread from each app (up to 20 apps), so hints aren't shown too often.

Local app data is excluded from Android cloud backup and device transfer. Deleting your account in the app, clearing the app's data or uninstalling Reread removes it.

2.16This website

This website (getreread.app) is served by Firebase Hosting, which processes your IP address and browser details to deliver the pages. It has no analytics, ads, trackers or cookies, and its fonts are served from this website too, so reading it sends nothing to anyone else. If you go to getreread.com, Cloudflare redirects you here and receives your IP address and browser details to do so. If you pick Light or Dark with the theme button, the choice is saved in your own browser (local storage) and never sent to us.

Legal basis: our legitimate interest in providing a working, readable website (Art. 6(1)(f)).

2.17Emails to support

If you email us, we receive your email address, what you write and anything you attach, and use them only to answer you and handle your request (for example a deletion request, see the deletion page). Please don't send us the messages you checked or decoded. Email to support@getreread.app is forwarded by Cloudflare to our inbox.

Legal basis: our legitimate interest in answering you (Art. 6(1)(f)); for requests about your rights under data protection law, our legal obligation to handle them (Art. 6(1)(c)).

3A note about other people's data

Decode works on messages other people wrote to you, a draft you check may mention other people, and a note in People is about someone else. That means Reread processes personal data about people who don't use Reread. Please:

• only share conversations you're allowed to share, and only what you need for the result;
• keep notes in People to what helps the result (for example "new to the team, likes short messages"), since they're sent with checks and decodes for that person;
• think twice before sharing sensitive details about someone else (for example their health, sex life or beliefs), and leave them out if the result doesn't need them; and
• remember that masking can miss things: only the names you saved in Reread are replaced, and other names, details written in unusual ways and details that identify someone in other ways (such as their employer or a place) can be sent as written (see 2.3).

We process the other person's messages, and your notes, in masked form, only to produce your result, and don't store them (except in a report, if you tick the box to include the text). Legal basis: our legitimate interest, and yours, in understanding messages sent to you and replying well (Art. 6(1)(f)). If you believe Reread processed your messages and want to ask about it, contact us. Because we don't store the messages or know who wrote them, we usually can't find them afterwards, but we'll explain what we can do.

4Who we share data with (processors)

We don't sell your personal data and don't share it for advertising. We share data only with the service providers ("processors") that run Reread, under their data-processing terms:

Your calendar app, if you use Add to calendar, isn't a processor: Reread only opens it, and you decide whether to save the reminder. We may also disclose data if the law requires it, to enforce our terms, or to protect the rights, safety or property of our users or others.

5International data transfers

Our database (Firestore) and server functions run in the United States. Gemini requests go through Google's global endpoint, so Google may process them in other countries. Google Analytics, Crashlytics, Performance Monitoring, Remote Config and Google Play, Cloudflare (DNS, email forwarding and the getreread.com redirect) and our email provider may also process data outside the EU/EEA, the UK and Switzerland. These transfers are protected by appropriate safeguards: Google's and Cloudflare's certification under the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework, and the EU Standard Contractual Clauses (with the UK and Swiss additions) in their data-processing terms. You can ask us for more information about these safeguards.

6How long we keep data

Deletion by date happens automatically, usually within a day or two after the date.

What deleting your account doesn't erase: usage statistics already sent to Google Analytics, crash reports and performance data, server logs, the reduced purchase records, the proof of deletion and the free-preview hash of the installation ID stay until the periods above end. Google Play keeps its own order records, which we don't control. History, names and notes exist only on your phone: deleting in the app clears them, but after a deletion by email they stay on the phone until you uninstall Reread or clear its data. If you want your usage statistics erased sooner, email us with your Reread ID before you delete your account, and we'll ask Google Analytics to delete them.

Accounts left behind: if you uninstall Reread or clear its data without deleting your account first, the old anonymous account stays on our servers, because nothing tells us it's no longer used. Email us its Reread ID, or a Google Play order number if you subscribed, and we'll delete it (see the deletion page). Without either, we can't tell which anonymous account was yours. It holds no name, email address or message content.

7Your rights and choices

Under the GDPR and UK GDPR (and similar laws, such as Switzerland's and California's) you have the right to access, correct, delete, restrict or object to the processing of your personal data, the right to data portability, and the right to withdraw consent at any time without affecting processing before you withdrew it. You can do most of this in the app:

• Withdraw AI consent: Settings → Privacy and data → AI processing → Withdraw. Reread then sends no text to its AI until you turn it back on.
• Usage statistics and performance data: turn off Settings → Privacy and data → Share usage stats. Where they rest on your consent, this withdraws it.
• Crash reports: turn off Settings → Privacy and data → Send crash reports.
• History: swipe a result away or tap Clear all in History, or turn off Keep history on this phone at the top of History (Settings → History).
• Names and notes: edit or remove them in Settings → People.
• Delete your account and data: Settings → Privacy and data → Delete account and data, or see the account deletion page.
• Manage or cancel your subscription: tap Manage in Google Play on your plan at the top of Settings, or go to Google Play → Subscriptions.

For any other request, email support@getreread.app with your Reread ID (Settings → Privacy and data → Reread ID), so we can find your data without asking for anything else. We reply within one month; if a request is complex we may need up to two more months, and we'll tell you. History, names and notes are only on your phone, so we can't see, export or delete them for you; use the app.

If you think we haven't handled your data properly, you can complain to a data protection authority: in Norway, Datatilsynet (the authority for Langsæter Labs); in the UK, the Information Commissioner's Office (ICO); in Ireland, the Data Protection Commission; in Switzerland, the Federal Data Protection and Information Commissioner (FDPIC); or the authority where you live.

8Security

Data in transit is encrypted with HTTPS/TLS. Private details in common formats are masked on your phone before anything is sent. Firebase App Check with Google Play Integrity checks that requests come from the real app on a genuine device. Firebase Security Rules stop the app from reading other users' data, and most server data can't be read by the app at all. Data on your phone stays in Reread's private app storage and is left out of backups. On Android 13 and later, the app switcher (Recents) shows a plain card instead of Reread's screens that can show messages, results or notes, and of the app a Reread sheet opened over; screenshots and screen recording still work. Access to our Google Cloud projects is limited to us.

No system is perfectly secure, but we take reasonable technical and organisational measures to protect your data. To report a security problem, see security.txt or email us.

9Children

Reread is not directed to children. It is intended for people aged 18 and over, and we don't knowingly collect personal data from anyone younger. If you believe a child has used Reread, contact us at support@getreread.app and we will delete the data.

10Changes to this policy

We may update this policy from time to time. We'll post changes here and update the date above, and tell you in the app about important changes. If a change affects what is sent to the AI, Reread asks for your consent again.

11Contact us

Last updated: 9 October 2026