Privacy Policy

01About this policy

GoMatrix Tech Internet Co., Limited operates Lettura and is responsible for the personal information it processes to provide the service. This notice covers the Lettura application, these website pages, and requests you send to us. Contact support@lettureapp.com for privacy questions.

Personal information means information that identifies you or can reasonably be linked to you, including your account identifier. This notice describes the current service, including its local mood feature and server-based correspondence. It does not govern independent services you visit through someone else's links. Our Service Agreement describes use of Lettura, and our Child Safety Policy describes our standards for protecting children.

Lettura is an account-based letter correspondence service for adults aged 18 or older. Sending originals and replies requires signing in with a supported Google or Apple account, or a phone number verified through Firebase Authentication. Letters, relationships, and safety reports are linked to the relevant Lettura account identifiers. Signing in establishes access to that account; it does not independently verify a person's legal identity or age.

Reading this notice is not blanket consent to processing. We will seek a separate choice where required by law. You can request account deletion even if you no longer have the app installed.

02Information we use and where it comes from

We receive information you enter, information supplied through supported sign-in providers, technical information generated when you use the service, and information other people submit in correspondence or reports involving you.

Account sign-in, birthday, and the information needed to send a letter are required for their respective features. If you do not provide them, those features may be unavailable. Mood check-ins, support messages, and notification permissions are optional.

Phone registration and sign-in

SMS sign-in is an independent way to access Lettura. After Firebase verifies your number, an existing account for that phone sign-in is opened; otherwise, a new account is created and you must complete registration, including the 18+ eligibility and community requirements, before using correspondence. Choosing phone sign-in does not automatically merge a separate Google or Apple account or transfer its letters and collections.

When you request a verification code, your phone number is sent to Google through Firebase Authentication. Google receives and stores it for authentication and to improve spam and abuse prevention across Google services, including Firebase. Verification and device-security services may also process technical information needed to assess the request. Appropriate consent is required before this processing; reading or accepting this policy alone does not replace that consent. See Firebase's phone authentication information.

A verification SMS may be sent, and your mobile operator's standard message or data charges may apply. Availability depends on the country or region, service limits, and security checks. You can choose an available Google or Apple sign-in option instead. A verification code establishes access to the number; it does not independently verify your identity or age.

Feedback and contacting us

In Me → Settings → Feedback, you can choose App issue, Feature idea, Account help, Safety report, or Other and submit a message. Your submission is linked to your signed-in account so we can assess the request and prevent misuse. The form does not require an email address and does not automatically attach your phone number, sign-in email, letters, or device logs to the feedback record. Related records may be consulted when necessary to investigate a concern.

Feedback is private to authorized personnel handling support, safety, or service operation; it is not published to other users. There is currently no in-app reply inbox. If you need a reply, you can email support@lettureapp.com using the contact link at the bottom of the page. Opening that link only opens your email app; you must send the message to contact us. Include only information needed to explain the issue, and do not send passwords, verification codes, or identity-document copies.

Sensitive information in your submissions

Letters, reports, and support messages may contain personal or sensitive information about you supplied by you or another person, such as health, religious, political, or relationship details. We process this content when checking and delivering correspondence or addressing a report or request. Submitted letters and replies are sent to Google's Vertex AI service for the content checks described below, including any personal information you put in the text. Avoid unnecessary sensitive details about yourself or anyone else, and do not include passwords, payment credentials, or identity-document copies in letters.

03Who can see your information

Other users: your display name, bird avatar, country, and account status can be available through relevant profile and correspondence views. A Discover original may reach multiple assigned readers after passing content checks. Replies are intended for the two participants after passing those checks. A stamp attached to a letter is visible to its readers. Your writing stays associated with your account even when you change your display name.

Information kept private from other users: sign-in email, verified phone number and provider identifiers, birthday, detailed location, stamp album and balances, notification settings, feedback submissions, and personal read markers are not part of the public profile. Your phone number is not added to your public profile or shared with correspondents through phone sign-in. Your read state is not shown to a correspondent as a read receipt. Mood history is not added to your letters or public profile. Information you choose to include in a letter can still be read by its recipients.

Service operation and safety: private account records and letters are processed on the infrastructure that operates Lettura and may be accessed for necessary support, security, safety, or legal work. Submitted letter and reply text is also processed by the content-check provider as described below. A reply being private to two participants does not exclude it from these safety checks. Letters are not end-to-end encrypted. We cannot prevent recipients from separately copying what they can read, and we cannot guarantee that information voluntarily shared with them remains confidential.

04Purposes and legal bases

We process information to provide and secure the service, deliver correspondence, support account and collection features, resolve requests, apply community standards, and comply with law. We do not treat your acceptance of the Service Agreement as consent to every optional use.

Where European or UK data-protection rules apply, the relevant bases include:

• Providing the service: processing necessary account and correspondence information to perform our agreement with you.
• Legitimate interests: proportionate security, abuse prevention, troubleshooting, support, and protection of correspondence history, where those interests are not overridden by your rights. This does not remove your right to object.
• Legal obligations: records and disclosures needed to comply with applicable requirements or valid legal process.
• Consent: optional processing for which the law requires your agreement. You may withdraw it without changing the lawfulness of earlier processing.
• Vital interests: necessary processing to protect someone's life or physical safety where the applicable legal conditions are met.

Different or additional conditions may apply under your local law, particularly to sensitive information. Sending a letter is not a waiver of those protections.

Automated content checks and safety reports

Before a submitted original or reply becomes available to readers, our server sends its text, associated prompt, and content type to a Google Gemini model through Vertex AI to check for violations of our community rules. The request does not add your sign-in credentials, birthday, private location, or local mood history; the writing itself can contain personal information. These checks support our zero-tolerance rules for objectionable content and abusive conduct. Content that fails the checks is withheld from readers, and a failed check may create an account-linked safety event.

Automated checks can make mistakes or fail to complete; they do not guarantee that every harmful item will be detected. You can report a concern from a letter's Report or block menu, choose Safety report in Settings → Feedback, or email support@lettureapp.com. A report made from the letter connects the reason, description, relevant account identifiers, and source correspondence. Feedback instead contains the description you supply, so identify the relevant account or interaction without reproducing abusive material. Concerns are assessed under our Service Agreement and Child Safety Policy. If you believe a safety decision is wrong, contact us using the appeal instructions.

Discover allocation, sending limits, and reward eligibility also use automated service rules. These organize app activity and do not guarantee a particular connection. Reading this notice or accepting the Service Agreement does not replace a separate permission required for third-party AI processing or another data use.

05Local storage, cookies, and device choices

On your device

Mood entries and history are stored locally, separated by account, and do not synchronize between devices through Lettura. You can change or remove today's entry and manage the reminder in the app. Local records may be lost when app data is removed or a device is lost; any operating-system backup or restoration depends on your separate settings.

The app also stores preferences, sign-in-related state, and caches of correspondence and stamp information. A cache is a local copy of information that can also exist on our servers. Deleting an account does not remotely wipe every device. Unsent original-letter and reply text is discarded when the editor closes; there are no saved drafts.

Website and service requests

These policy pages use local fonts and do not set advertising or analytics cookies or run analytics scripts. The website host can receive your IP address, requested page, browser information, and request time to serve and secure the site. Service infrastructure also processes request and error records for operation, troubleshooting, and security. These records are separate from your local mood history.

Independent sign-in providers and websites you follow through links have their own privacy practices.

Notifications and permissions

Manage notification categories in Lettura and system notification permission in your device settings. Push messages use general activity notices rather than letter bodies, but previews may still appear on a locked device. On iOS the app may request App Tracking Transparency permission; declining does not disable core correspondence. The current app has no advertising integration and does not use an advertising identifier for advertising or cross-app tracking.

06Providers and the information they handle

The following providers support the current application. Their notices explain their own processing, including service or security information they handle under their terms.

• Google and Firebase: supported sign-in and authentication, database storage, server processing, push delivery, and App Check security checks. Relevant information includes account and authentication records, phone numbers used for verification, stored app data including feedback submissions, push identifiers, network requests, and device or app attestation information. For phone sign-in and SMS reauthentication, Google receives and stores the supplied number for authentication and spam and abuse prevention across Google services. Device checks or reCAPTCHA may be used to protect the verification process. Google Cloud Vertex AI also receives submitted original-letter and reply text, the associated prompt, and content type to run automated content checks. Information within your text is included in that processing. The feedback form stores submissions in Firestore; it does not send feedback through the letter-content AI review. See Firebase Privacy and Security, Vertex AI data governance, and Google's Privacy Policy.
• Apple: Sign in with Apple, Apple push delivery, and device or app attestation on supported devices. Your provider choices can affect the email or profile information supplied to us. See Apple's Privacy Policy.
• Cloudflare: R2 and related delivery infrastructure serve stamp images and other assets, receiving network and request information needed to deliver them. This asset delivery does not itself require sending your letter body to Cloudflare. See Cloudflare's Privacy Policy.
• ipwho.is / IPWHOIS: our server sends your IP address for an approximate location lookup and may receive a country, region, and city. It does not send your letter body for that lookup. See IPWHOIS's Privacy Policy.

Only the country is used as your public profile location. A country inferred from an IP address can be inaccurate; contact us if it needs correction. The current registration lookup does not request device GPS location.

07Other disclosures and international processing

In addition to the recipients and providers described above, relevant information may be disclosed when necessary to investigate misuse, protect a person, establish or defend a legal claim, or comply with a valid legal requirement. Information disclosed for these purposes should be limited to what is needed. A report may include information about both the person reporting and the account being reported.

If ownership or operation of Lettura changes, necessary data may be transferred as part of that transaction, subject to applicable law and confidentiality protections. A business transfer does not remove your rights or authorize an unrelated use merely because the data changed hands.

Recipients may be in other countries, and our infrastructure providers may process information outside your country of residence. Protections and government-access rules can differ. Where applicable law requires a transfer safeguard, it must be in place; merely using the app is not consent to bypass those requirements. Contact support@lettureapp.com to request the relevant processing locations and information about safeguards, including any applicable contractual protections.

08Request account or data deletion

How to submit your request

• In the app: open Me → Settings → Delete account, enter the requested confirmation, and complete any sign-in verification. For a phone account, this may require a fresh SMS code for the number used to sign in. If you have not completed registration and cannot reach Settings, use the email route below; you do not have to finish registration to request deletion.
• By email: identify the account and what you want deleted. Provide the account email, sign-in provider, or phone number including its country code if known. If you cannot access the original email or phone number, or use an Apple private relay address, explain this in the message.

Opening the email link does not send a request or delete the account; send the message to submit it. If no email app opens, write to the address above using your usual email service. A suggested subject is optional. Never send passwords, verification codes, or identity documents with an initial request.

Scope and verification

An account deletion request covers the account and its associated personal information. You do not need to list every record or apply twice. We may request only the information needed to verify the account or an authorized representative. You can also ask to delete particular information while keeping the account, although a feature may stop working if it needs that information.

What happens next

Deletion removes sign-in access and starts cleanup of birthday, detailed private location, push-device registrations, your stamp album, and your private account records such as delivery, read, notification, blocking, and collection activity. Account balances are reset. The cleanup also deletes your original-letter records, pending content-check jobs, in-app reports involving your account, feedback you submitted, and associated feedback rate-limit records, while making your previous Discover allocations unavailable. The app attempts to clear mood history and relevant caches on the device used for deletion. Some server cleanup continues in the background.

Deleting the account also deletes its Firebase Authentication identity, including the phone number on a phone account, from active account access. It does not delete your Google or Apple account or cancel your mobile service. Providers may retain backups or security records under their applicable terms and lawful retention requirements; deletion is not a promise that every provider copy is erased immediately.

Using the same phone number after deletion: once the old authentication account has been deleted, a successful new phone registration creates a new account identifier. You must complete registration again. The new account does not restore the old letters, relationships, flowers, stamp album, or feedback, even if cleanup of the old account is still running. Re-registration does not permit evasion of a block, suspension, or safety restriction.

Other records can remain after automatic cleanup. The next section explains what can remain and why retention needs a lawful basis. We must arrange any additional deletion required or explain an applicable exception. See Your privacy rights for response periods and complaints.

Signing out, disabling notifications, or uninstalling alone does not delete your server account.

09How long information is kept

Retention depends on the purpose, whether an account is active, what is needed for correspondence, and any specific safety, dispute, or legal requirement. Submitted content and content-check results are stored on our infrastructure while needed for processing and the applicable operational lifecycle. Account deletion starts the cleanup described above; it does not erase all copies of previously delivered correspondence. The following information can remain:

• Delivered correspondence and historical account profile: copies of original letters and replies already stored in a conversation, account identifiers, historical display names and avatars, and profile information recorded in that conversation can remain for the other participant. Copies of an original already assigned through Discover, or retained in another user's blocked history, may also remain even when delivery or interaction is unavailable. The current profile is marked as deleted and its country is cleared. Blocking history maintained by another user can also retain relevant profile information and message previews. These records remain within the scope of a personal-data deletion or restriction request.
• Deletion markers: a limited record of the account identifier, deleted status, and relevant timestamps remains to recognize the closed account and prevent its old application records from being treated as active. It no longer contains your birthday or detailed private location.
• Support, security, or legal records: email correspondence, infrastructure security records, or information separately preserved for a specific safety, dispute, or legal purpose may need to remain. The current automatic cleanup deletes in-app reports involving the deleted account; it does not guarantee preservation of every report or piece of safety evidence.

Feedback: submissions are kept while needed to handle the request and relevant support or safety follow-up. They do not currently expire automatically when a request is handled. You can request deletion of particular feedback through the privacy contact below, and account cleanup removes feedback submitted under the deleted account and its submission-limit records. Email exchanges or evidence separately retained for a lawful safety or legal purpose are handled under the criteria above.

For information we retain, we must assess whether the purpose requires identifiable information, explain the applicable reason and period or criteria on request, and delete it or remove its link to a person when the basis ends. Replacing a display name with an account identifier alone does not remove that link. Incomplete automatic cleanup is not a retention reason.

Temporary notification delivery jobs and other operational records have their own purposes and lifecycles. A notification expiring does not delete its underlying letter, and a local cache being removed does not erase the server copy.

Account deletion does not recall delivered letters. We cannot remotely erase screenshots, independent recipient copies, or device backups outside our control. Where applicable law requires us to notify providers or other recipients of an erasure or restriction, we must do so, subject to any lawful exception. For local data on another device, use that device's app-data controls.

10Security and sensitive correspondence

We use authenticated access, separation of public and private records, and infrastructure security controls to reduce unauthorized access. Access needed for support, safety, or legal handling should be limited to the relevant purpose. No storage or transmission system can guarantee absolute security.

Letters are stored on service infrastructure and may be cached on devices; they are not end-to-end encrypted. Protect your device and sign-in account. If you believe your account or information has been compromised, contact support@lettureapp.com. Where a security incident requires notification to affected people or an authority, we must follow the applicable legal requirements.

11Your privacy rights and how to use them

Available rights

Depending on applicable law, you may request access, correction, a copy or portable version of your information, deletion, restriction, or an explanation of disclosures. You may be able to object to processing based on legitimate interests, withdraw consent for optional processing, or authorize a representative to act for you. Withdrawal does not affect earlier lawful processing.

Make a request

Email support@lettureapp.com with what you want us to do and the account email, sign-in provider, or phone number including its country code, if known. No special wording or subject line is required. If you cannot access the original email or phone number, explain this. Opening the link only opens your email app; you still need to send the message.

We may ask for the information needed to verify the account or your representative's authority. Do not send passwords, verification codes, or identity documents with your initial request. If another person supplied inaccurate information about you, you can raise that here. We will protect other people's information when supplying correspondence or report records.

Responses and complaints

We will respond within the period required by applicable law. Where EU or UK rules apply, the ordinary response period is one month; any permitted extension and its reasons must be communicated as the law requires. This is a response period, not a promise that every retained record will be erased within one month. We will explain a refusal or limitation and available complaint options.

Requests are generally free; an exceptional charge or refusal must have a lawful basis. We will not retaliate against you for exercising a right. You may complain to the appropriate privacy authority or seek an available legal remedy without first contacting us where the law permits.

If local law gives you a sale, sharing, targeted-advertising, or sensitive-data choice relevant to our processing, you can use the same contact route. The current app has no targeted-advertising feature.

12Adults only and underage information

You must be 18 or older to create an account, send a letter, reply, or use correspondence features. Registration checks the birthday you submit against that requirement on the app and server. It is a declared-age check, not independent identity verification. Do not provide a false birthday or use another person's account to bypass the rule. Parental permission does not make an underage account eligible.

We do not intend to collect information from people under 18 for participation in Lettura. If we learn that an account belongs to someone under 18, our policy is to restrict access and arrange deletion of their personal information, retaining only information necessary for a lawful safety or legal purpose. Previously delivered correspondence and third-party copies need the separate handling described in How long information is kept; an underage account is not an exception to applicable deletion duties.

Anyone, including a young person, parent, guardian, or other concerned person, may read these policies and contact support@lettureapp.com without creating an account. Provide enough information to locate the account or content and explain the concern; do not send passwords, verification codes, identity documents, or abusive material with an initial report. We use the information in that request to assess the concern, handle the privacy or safety request, and meet applicable duties. See the Child Safety Policy reporting instructions.

13Updates and contact

We will update this notice when practices change and identify revisions by their date. Material changes will receive appropriate notice, and additional consent will be obtained where required. A new notice does not retroactively authorize an unrelated use of previously collected information.

Data controller and operator: GoMatrix Tech Internet Co., Limited.
Privacy, deletion, support, and safety contact: support@lettureapp.com. Use the same address for an underage-data concern or inappropriate activity; an account is not required to contact us.

Signed-in users with completed registration can also use Me → Settings → Feedback for an account question or safety concern. Use email if you need a reply or cannot access the app. A feedback submission does not itself delete an account; use the deletion controls or email deletion instructions for that request.