Latelight - Privacy Policy

Last updated: November 1, 2026

This policy describes how the Latelight iOS app handles your data. Latelight is published by ByteVoid SAS ("we", "our", "us"). The bytevoid.io website has a separate privacy policy at /legal/privacy.

Latelight is a self-reflection tool. It is not therapy, not a medical service, and not a substitute for professional support.

What we collect

On your device (stays on your device)

  • Your relationship content. The people you add, the messages you write, the conversations Latelight has with you, and the Portraits it generates. All of this is stored on your device in encrypted form. We do not have access to it. We cannot read it.
  • Encryption keys. A master key is generated on your device on first launch and stored in the iOS Keychain. It never leaves your device.
  • App preferences. Your settings, onboarding state, and acknowledgment of the medical disclaimer. Stored locally.

Sent off your device (only when you use AI features)

  • Message content for AI processing. When you send a message, the app sends the message and its context to our proxy. For the chat reply, the context has six parts. First, the name you gave in the "Your name" field, if you gave one. Second, the name and relationship of the person. Third, facts the app saved about them. Fourth, their Portrait. Fifth, summaries of your last two sessions. Sixth, up to 19 earlier messages. The proxy forwards the chat context to OpenAI. It forwards message text to Google for two tasks. The tasks are noting facts and writing session summaries. This text can include health or sex-life details if you write them. The proxy does not store it. Each provider keeps data under its own rules (see Who receives your data below).
  • A device authentication token. The first time you use an AI feature, your device generates a random identifier and registers it with our auth server. The server returns a token that authorizes AI requests. The server keeps a device record with the device identifier and the times of your first and last requests. We do not link the record to your name or your email address. A record made before we stopped storing the IP address may still hold it. That record ends at most 44 days after the last request from that device.

Subscription and payment

  • Apple handles all payment processing. When you subscribe, Apple processes the transaction. The app reads your subscription status (active or expired) from Apple through StoreKit, on your device. Our servers do not receive it. We never see your payment details. We do not see your credit card, billing address, or Apple ID.

What we do NOT collect

  • We do not collect analytics on your in-app content (no tracking of what you write, who you add, or what the AI says).
  • We do not have a server-side database of your relationship data.
  • We do not sell, rent, or share your data with advertisers, data brokers, or third parties for marketing.
  • The app does not contain Meta Pixel, Google Analytics, or any third-party analytics SDKs that track user content.

Anonymous usage counters

Latelight sends ten anonymous counters to a server we run. The counters count the first app open after an install. They count the end of onboarding and your first message that the AI answers. They count each time you open the app after a fresh start or after more than 30 minutes away. They count each time the subscription screen is shown, and each purchase. They count each time the app shows a card that offers crisis resources. That counter records that a card was shown. It never records what you wrote. The crisis protocol page says what ByteVoid counts and publishes the yearly number.

Three more counters work like this. One counts how many people open the app on a day (at most one counter a day). One counts how many open it in a week (at most one a week). One counts how many send a message in a week (at most one a week).

Each counter carries only six things. They are its name, the app version, the build number and the platform. The other two are how the app was installed and a short label. The label names the part of the app that opened the subscription screen. It can also say that the app opened from its icon, or that you sent a message. Those three also carry the number of days since the app was first opened on this iPhone (0 to 30, or 31 for longer), so we can see if people come back. The number is -1 when the app cannot tell when you first opened it.

Nothing in a counter identifies you. A counter holds no install ID, no name, no message text and no timestamp. Our server files each counter under the calendar day in Paris time. It keeps no time of day. Like every request, a counter reaches our server with your IP address. Our host, Railway, can keep it in its server logs for 30 days. We store the counters on a server that we run on Railway Corp. (USA). We keep the counts. They identify no one.

How we use what we collect

The encrypted on-device data lets the app function. The AI proxy routes your messages to generate responses. The auth token lets us validate requests came from a registered device, preventing abuse. The subscription status tells the app whether you have access to premium features.

We do not train AI models on your content or use your data for anything beyond running the app.

Legal basis

We process your messages and their context to run the AI features you ask for (our contract with you). Because what you write can reveal health or sex-life details, we ask for your explicit consent on the first screen. We keep the device record on the basis of our legitimate interest in protecting the service from abuse. We keep the anonymous counters on the basis of our legitimate interest in counting app use.

Who receives your data

  • Apple Inc. (USA). App distribution, payment processing, StoreKit subscriptions, iCloud backup of encrypted device data if you have iCloud backup enabled. Apple acts under its own terms and privacy policy.
  • OpenAI Ireland Ltd (Ireland) and OpenAI OpCo, LLC (USA). Large language model provider through our proxy. It processes your message and its context to write the AI chat replies. The context includes up to two earlier session summaries. Google writes those summaries. OpenAI's API terms apply. OpenAI keeps API requests for up to 30 days to detect abuse. It does not use them to train its models.
  • Google Cloud France (France) and Google LLC (USA). Large language model provider through our proxy. It processes your message text for two tasks. It notes facts about the person. It writes short summaries of your sessions. It receives each message for the facts. It receives the last 40 messages of a session for the summary. Google's API terms apply. Google processes this data under its data processing addendum. Google keeps prompts and replies for up to 55 days to detect abuse. We use Google's paid service, so Google does not use them to improve its products.
  • Railway Corp. (USA). Hosts our authentication proxy and AI relay in the Netherlands. For each device, it keeps the device identifier, the time of registration and the time of your last request. A counter holds your AI use over the last 24 hours. A second counter counts registrations from each IP address for 1 hour. See How long we keep data below.
  • Fastmail Pty Ltd (Australia). Hosts our email, including [email protected], where you write to us.
  • Cloudflare, Inc. (USA). Carries the traffic of our website, including this page. The app does not call Cloudflare.

We do not use Resend or Meta Pixel inside the Latelight iOS app. Those are used only on the bytevoid.io website.

International data transfers

ByteVoid SAS is established in France. Some of our providers are outside the European Economic Area and the United Kingdom. For each of them, we use the safeguard in this list. For the EEA, that is the European Commission's Standard Contractual Clauses or the EU-US Data Privacy Framework. For the UK, that is the UK Addendum to those clauses or the UK extension to the Data Privacy Framework.

For the EEA, each transfer follows Chapter V of the GDPR. For the UK, each transfer follows Article 44A of the UK GDPR and meets the UK data protection test. Under that test, the protection after the transfer must not be materially lower than UK protection.

  • OpenAI (Ireland and USA). EEA: OpenAI Ireland Ltd is our contracting company. Onward transfers rely on Standard Contractual Clauses or an adequacy decision. UK: Standard Contractual Clauses with the UK Addendum, with OpenAI OpCo, LLC.
  • Railway Corp. (USA; our servers run in the Netherlands). EEA: Standard Contractual Clauses. UK: clause 9.4 of Railway's data processing terms. It uses the Data Privacy Framework if the recipient is certified, or the UK Addendum to the Standard Contractual Clauses.
  • Google Cloud France and Google LLC (France and USA). Google Cloud France is our contracting company. EEA: the EU-US Data Privacy Framework covers transfers to Google's certified US entities. The Standard Contractual Clauses apply if the Framework does not. UK: the UK extension to the Data Privacy Framework.
  • Cloudflare, Inc. (USA). EEA: Standard Contractual Clauses, or the EU-US Data Privacy Framework. UK: the UK Addendum.
  • Fastmail Pty Ltd (Australia). EEA: Standard Contractual Clauses. UK: Fastmail names no safeguard yet.
  • Apple Inc. (USA). This is not a ByteVoid transfer. StoreKit runs on your device. iCloud Backup is your own. Apple acts under its own terms.

Encryption details

Sensitive content (messages, person details, Portraits, conversation history) is encrypted on your device before being written to storage. The encryption key lives in the iOS Keychain. Plaintext copies are cleared from memory once encryption completes. If your device is locked, the data is protected by iOS Data Protection. If you delete the app, iOS deletes the data on your iPhone. If iCloud Backup is on, your iCloud Backup holds an encrypted copy of that data and of the key. The key in a backup works only on the same iPhone. A backup on a new iPhone brings the data but not the key. Without the key, nobody can read the data, including us and Apple.

How long we keep data

Data stored on your device stays there until you delete it. It remains for as long as the app is installed and is removed when you delete the relevant item in the app, use "Delete Account and Data" in Settings, or delete the app. We keep no copy of your data on our servers, so we cannot recover data that you delete. A backup that you made earlier, with iCloud or a Mac, can still hold a copy.

On our servers we hold a device record. We use it to authenticate requests and prevent abuse. We delete the device record 44 days after the last request from that device. The record holds the device identifier. It also holds the time of registration and the time of your last request. A record made before we stopped storing the IP address may still hold it. That record ends at most 44 days after the last request from that device. A separate counter holds your AI use over the last 24 hours. Our host, Railway, also keeps server logs. They can hold the device identifier and your IP address. Railway keeps them for 30 days. Your message content passes through our proxy only for the length of each request and is not stored on our servers.

Your rights

You can email [email protected] at any time to:

  • Ask what information we hold about you. In practice, this is a device record with your device identifier and the times of its first and last requests. A record made before we stopped storing the IP address may also hold your IP address. We do not hold your conversation content or your subscription status.
  • Ask us to delete data. "Delete Account and Data" in Settings deletes the device identifier on your phone and asks our server to delete your device record. If our server cannot be reached, the record ends by itself within 44 days. To ask by email, quote the device identifier shown in Settings.
  • Withdraw consent for AI processing in Settings. The app then sends nothing to the AI providers until you agree again. You can also email us, or delete the app.

European Economic Area and United Kingdom (GDPR / UK GDPR). You can complain to us about how we handle your data. Write to [email protected]. We acknowledge each complaint within 30 days. You have the rights above plus the right to data portability, the right to object to processing, and the right to lodge a complaint with your supervisory authority. In France, that is the CNIL. In the United Kingdom, it is the Information Commission (ICO).

California (CCPA / CPRA). You have the right to know what personal information we collect, request deletion, and opt out of "sale" or "sharing" of personal information. We do not sell personal information.

Canada (PIPEDA + provincial laws). You have the rights above. In Quebec, Law 25 grants specific rights regarding automated processing.

Australia (Privacy Act 1988 + APPs). You have the rights above. You can also lodge a complaint with the OAIC.

Children

Latelight is for users 18 years of age and older. We do not knowingly collect data from anyone under 18. If you believe a minor has used Latelight, please contact us and we will delete the associated device records.

Information about other people you mention

When you write about another person in Latelight, what you write stays on your device, encrypted. We do not see it. Because the AI processes your messages, our third-party AI providers (OpenAI and Google) may process descriptions of others as part of generating a response. The providers keep them only as stated in Who receives your data.

You are responsible for being thoughtful about what you write about others. Do not share information about another person (medical, financial, sexual, immigration status, or other sensitive categories) without their informed consent.

Data controller

The data controller is ByteVoid SAS, 9 rue des Colonnes, 75002 Paris, France. Contact: [email protected].

Data breaches

If a personal data breach affects data we hold, we will notify the CNIL, our lead supervisory authority in France, within 72 hours of becoming aware of it, as required by the GDPR. If a breach affects people in the United Kingdom, we will also tell the Information Commission (ICO) within 72 hours. Where a breach is likely to result in a high risk to your rights and freedoms, we will also inform affected users without undue delay. Because your relationship content is encrypted on your device and is never stored on our servers, a breach of our systems would expose only your device identifier and IP address, not your conversations or the people you write about.

Changes to this policy

We may update this policy. The "last updated" date at the top reflects any changes. Material changes will be surfaced in the app on next launch.

Contact

For questions about this policy, email [email protected].