Privacy Policy

Last updated: November 13, 2026

Food Noise LLC operates the Food Noise app, its in-app community, Marlo, foodnoise.app, and the Food Noise community on Discord. Discord itself is a separate service operated by Discord. This policy explains what we collect, why we use it, who receives it, and the choices you have. Food Noise LLC is responsible for the personal information we handle as described here. Contact us at support@foodnoise.app or 7901 4th St N, Ste 300, St. Petersburg, FL 33702, United States.

Food Noise is a self-help and peer support service. Information about eating, mental health, medication, or recovery can be sensitive health information even though we do not provide medical care.

Information we collect

The information we collect depends on the features you choose.

  • Account and profile: Your name, email, sign-in provider and identifiers, community username, avatar choices, preferences, consent records, and account status. These let us authenticate you, save your settings, and provide the service.
  • Health, goals, and progress: Answers you choose to give about eating patterns, food noise, urges, diagnoses, medication, symptoms, goals, and circumstances; check-ins, journal entries, activity completions, streaks, and progress. We use these for the support and personalization you request. We also collect an optional estimate of food-related spending to personalize savings and related features.
  • Marlo: Your messages, Marlo's replies, conversation history, and the selected profile information used to personalize a reply. If you report a reply, we also collect a separate copy of that reply, your reason, any note, and the related account and technical information described below. These records can contain sensitive information.
  • In-app community and partner chat: Posts, replies, messages, reactions, timestamps, room membership, partner preferences and relationships, blocks, reports, appeals, and moderation outcomes. A relationship or block is part of your account's social connections; it is not an upload of your phone's address book.
  • Optional Discord community: Your account-linked community code, the Discord identity and application information you provide when joining, and content or support requests you share with our Discord community or team. We use this information to confirm Food Noise membership, manage access, moderate our server, and handle support or safety concerns.
  • Purchases and rewards: Subscription status, products, transaction and renewal information, offers, and purchase/refund history. We also keep earned rewards, cosmetic items, and records of activities credited toward rewards. Apple processes payments; we do not receive your full payment card or bank details.
  • Support and feedback: Messages you send us, reports, appeals, and optional feedback, including account-deletion feedback. Please include only information needed to explain the issue.
  • Device and service use: Account and device identifiers, IP address, approximate country or region, operating system and app versions, sign-in activity, notification tokens, app interactions, subscription and paywall events, network timings, errors, and security records. We use these to operate, protect, understand, and improve the service. Attribution information and its choices are described below.
  • Age and integrity: Your age declaration, its source and status, and device-integrity results. These help apply age restrictions and prevent misuse. Version 2.0.14 does not verify your age through Apple's Declared Age Range service.
  • Blocker settings: An encoded copy of your Screen Time selections, blocking schedule, preferences, and pause status. These sync to Supabase linked to your account so we can save and restore your settings; they are not kept only on your device.
  • Legacy phone and audio records: A phone number and voice recording you provided through the retired call setup in an earlier version may remain in your account until removed. Version 2.0.14 retires that setup. Local voice exercises work differently, as described below.

We do not request precise GPS location. Approximate location can come from an IP address, App Store region, or service provider. Free text can reveal more than the fields we ask for; avoid sharing someone else's private information without a lawful reason.

The in-app community

Community forum posts, replies, reactions, and your community profile are visible to the members who can access that area. Messages in a room are visible to people with access to that room. Partner messages are visible to the participants, with limited service and safety access described here. Neither a room nor a partner conversation should be treated as confidential medical care.

You can separately choose to share status items with an accountability partner, such as whether you checked in, your check-in streak, a mood word, your binge-free day count, and your progress in a challenge. These sharing choices start off. When you turn one on, the selected status is sent to our servers so it can be shown to your partner.

Partner chat is not end-to-end encrypted. Our systems and service providers process messages to deliver and moderate them. Authorized staff may access relevant content for a report, appeal, safety concern, age concern, security incident, or legal obligation. Staff access is limited by role and recorded; partner conversations are not provided as a general staff browsing feed. Other members can still copy or take screenshots of content they can see.

Automated checks, reports, and appeals

We use rules and Anthropic's Claude AI to screen in-app community content, including posts, replies, partner messages, edits, usernames, and report notes. Anthropic may receive the submitted text, relevant earlier messages or thread context, and limited safety context, such as the type and recency of a previous crisis flag. We attempt to remove contact details before certain checks, but names, health information, and other identifying details can remain in what you write. These checks are not anonymous processing.

The checks can hold or reject content, apply a warning or temporary restriction, or identify a possible safety issue. Reports and requests for an automated second look can send the relevant content and context for another AI assessment. A report is not an emergency alert, and AI can miss a problem or make a wrong decision. You can contact support@foodnoise.app to request human review. The Terms explain the difference between report follow-up and an automated appeal.

AI moderation is required to participate in the in-app community. Separate permission to send your information to Anthropic is required before that sharing begins; accepting this policy alone does not give that permission. If you do not want this processing, do not join or submit in-app community content. You can leave the community and separately choose whether to delete your content. Blocking a member limits contact and visibility; it does not erase messages or safety records.

We store reports, report notes, block relationships, decisions, and appeals to handle concerns and prevent abuse. Reporting is not an anonymous submission to Food Noise. We do not ordinarily show your identity as a reporter to the reported member, but may disclose information where needed for a fair process, to protect someone, or as required by law.

Optional sharing of a win

Adults may separately permit Food Noise to share one selected community win and its username on Food Noise's social channels. The choice is off by default and applies to the specific version approved. Editing the win requires new permission. It does not cover private journals, Marlo conversations, room messages, or partner chats. You can withdraw permission to stop future use and ask us to remove copies we control. We cannot erase copies independently made by other people. Any sharing must also comply with legal and platform restrictions on using health or fitness information for advertising or promotion; your permission does not override those restrictions.

Optional Community Discord

Joining our Discord community is optional. In Discover, the Community Discord card shows your community code and the joining steps. You can use Food Noise's other available features, including the in-app community, without joining Discord.

Your community code is stored with your Food Noise profile in Supabase and may also be saved on your device. When you copy it from the app and paste it into the Discord joining application, you provide it through Discord to our team. We use the code to match your application to your Food Noise membership and confirm access. This can link your Discord identity to your Food Noise account; the code is not anonymous information. We use the membership and application information to manage access, support, and safety in our server.

Discord receives the information you provide on its platform, including the code you submit, Discord account information, and content you share there. Discord operates under its own Privacy Policy and Terms of Service. Our team and other server members can see content according to the Discord spaces and audiences you choose. Avoid posting sensitive information you do not want that audience to see.

This policy covers Food Noise's handling of membership and server-management information. Discord's own collection, retention, privacy controls, and account-deletion rules are governed by its policy. Deleting your Food Noise account does not automatically delete your Discord account or the content you posted there. Use Discord's controls for that account and content, and contact us about records or content our team controls.

Marlo and Anthropic

Marlo is an optional AI companion powered by Anthropic's Claude. From version 2.0.14, the app asks you to separately agree to the described AI sharing before you use Marlo. General health consent, a subscription purchase, and acceptance of these legal pages do not substitute for that choice. Earlier versions do not have this separate consent screen and can still send messages and context when you use Marlo. Update every device when version 2.0.14 is available, or stop using Marlo if you do not want this sharing.

To generate a reply, we send Anthropic your message and relevant conversation history. Where used for personalization or safety information, we also send selected onboarding or profile answers, such as your main struggle, symptoms, goals, or food-spending estimate, and a country or region. We do not promise that a message is anonymous simply because we omit a name or email field. Anything you type can identify you or another person.

Food Noise stores your conversation history on its servers to maintain context. Authorized Food Noise personnel may review relevant conversations for safety, abuse investigation, and quality improvement, with access limited to those purposes. We may produce aggregated quality summaries that do not identify individual members. If we use another analysis provider, such as OpenAI, it receives only those nonidentifying summaries, not your raw private conversations or account identifiers.

From version 2.0.14, you can turn Marlo off in Settings and clear your chat history. Turning Marlo off blocks new sends from that app installation; it is not a guarantee that an older app version or another device stops sending. Stop using Marlo on other devices too, and contact us if you need help stopping further processing. Clearing history requests removal of the stored conversation. Neither action deletes a separately submitted reply report, recalls an API request already processed, or overrides a provider's lawful safety retention.

If you report a Marlo reply, we save a separate copy of the selected reply, your report reason, and any optional note in Supabase for our team to review and address safety or quality concerns. The report also includes your account identifier, message and conversation identifiers, the reply time, submission time, and app version. The copied reply is limited to 8,000 characters and your note to 500 characters. Submitting a report does not automatically attach the rest of your conversation, but the copied reply or your note can contain personal or health information. This report goes to Food Noise; using this control does not submit feedback to Anthropic.

We normally retain Marlo reply reports for 24 months from submission, then remove them through daily cleanup. Clearing chat history or turning Marlo off does not delete the copied reply or report note. Account deletion removes these reports from our active records; separately preserved safety evidence, lawful holds, and backups follow the rules below. You can also contact us about a report or request its deletion.

Anthropic's commercial API does not use customer inputs and outputs to train its general-purpose models by default. Its terms allow different treatment for content deliberately submitted as feedback or through an optional training arrangement. We do not opt your private conversations or community content into those arrangements, or submit identifiable member content as training feedback, without separate permission. Anthropic's commercial data-use explanation.

Under Anthropic's standard commercial API policy, inputs and outputs are normally deleted within 30 days. Content flagged for a possible policy violation may be retained for up to two years, and related safety classification scores for up to seven years. If content is deliberately submitted as feedback, Anthropic applies a separate five-year retention period to the associated data. Legal obligations and policy-enforcement needs can justify longer retention. Anthropic's retention policy.

Age and access

Food Noise accounts, self-help tools, Marlo, and our communities are for people aged 16 and older. Crisis-resource links remain available at any age. In-app partner matching and optional promotional sharing are for adults aged 18 and older. To use Discord, you must also meet Discord's own age requirements.

In version 2.0.14, in-app community access uses your age declaration and reviews of reported age concerns. This version does not verify your age through Apple's Declared Age Range service. These are in-app community access checks, not verification of everyone's age before they can use the app. They are not identity-document checks. Device-integrity checks help establish that a request came from a genuine app or device; they do not prove age.

If we learn that a user is below the permitted age, we may restrict access and remove information, except records needed for a safety or legal obligation. Contact us if you believe someone under 16 has given us personal information.

How we use information and our legal bases

We use information to provide your account and chosen features, personalize support, manage subscriptions and rewards, deliver communications, maintain safety, respond to support requests, improve reliability and usability, and meet legal obligations. Advertising measurement and optional research have separate limits below. We do not use private journal text for advertising, marketing, product analytics, or research.

Where data-protection law requires a legal basis, we rely on performance of our agreement for requested services; legitimate interests for proportionate security, support, service administration, and product improvement; legal obligations for required records and disclosures; and consent where required, including optional marketing, tracking, and sensitive-data uses. For health or other specially protected information, we also need explicit consent or another applicable legal condition. Accepting these Terms or this policy is not, by itself, explicit consent to a sensitive-data use.

Service providers and other disclosures

We give providers the information needed for their role, under applicable contractual protections. Key providers include:

  • Supabase: Account authentication, database, file storage, and live updates, including profiles and community codes, health and journal records, chat, in-app community content, reports and copied Marlo replies, consents, encoded blocker selections and settings, and legacy uploaded recordings.
  • Anthropic: Marlo replies and in-app community moderation, with the content and context explained above.
  • Apple: Sign in with Apple, App Store billing and subscription records, push delivery, and device-integrity services.
  • Google: Optional Google sign-in and its authentication/integrity services. Google processes profile and account information, which can include name, email or phone information, plus device, IP, approximate-location, and sign-in usage data under its own account policies. We receive the information supplied through the sign-in flow. Recorded calls use YouTube's privacy-enhanced video player. Loading or playing a video sends Google network and device information and the requested video; privacy-enhanced playback does not mean no data is sent.
  • Superwall: Paywalls, subscription access, purchases, and related account, device, IP, usage, and performance information. An optional daily-spending estimate can personalize paywall wording. From version 2.0.14, the app does not send that estimate when either your device region or App Store region indicates the European Economic Area, United Kingdom, or Switzerland; sharing elsewhere waits for the regional check. Earlier versions can send daily and yearly spending estimates without this regional restriction. We do not authorize forwarding that estimate or health answers to advertising partners.
  • PostHog: Account-linked product analytics and feature configuration, using permitted interaction, device, and technical information. From version 2.0.14, the app filters diagnosis and medication answers, check-in values, mood and goal answers, and specified binge and crisis events. It does not send journal or message text in its analytics events. It still records account-linked feature use, including when an urge is logged, use of support tools, and community actions. The timing and frequency of these events can reveal health-related behavior. Earlier versions can send more detailed health-related events and values, including binge counts, food-noise scores, streak lengths, moods, and goals. Version 2.0.14 disables automatic rage-click capture and surveys, and does not enable screen recording or automatic crash capture.
  • AppsFlyer: Install and advertising attribution, campaign and conversion measurement, using applicable account/device identifiers, IP-derived region, purchase and interaction events, and advertising information, subject to the choices below.
  • Resend: Email delivery, including recipient addresses, message content, and delivery records. Its abuse-screening subprocessor is described below.
  • Cloudflare: Network delivery, hosting and protection of service endpoints, including the moderation portal. This can involve IP addresses, request metadata, security logs, and content passing through the service.

Apple and Google also operate services under their own privacy policies. A provider may have its own obligations to retain billing, security, or legally required information.

We may disclose relevant information to professional advisers, authorities, or others when legally required, to investigate abuse, protect people, or establish or defend legal claims. A business transfer may involve personal information, subject to this policy and applicable law. We do not sell private journals, chats, or health records to data brokers.

Test purchases

Purchases made in Apple's sandbox for testing or App Review do not charge real money. We keep their account identifier, test product and transaction identifiers, access status, expiry, and processing records so Marlo and the in-app community can recognize test access. These server records are kept separately from real subscription and purchase-event records and are excluded from the production purchase counts, revenue reports, and server advertising-conversion queues. Test accounts can still generate the normal app-use, support, and safety records described in this policy.

Advertising measurement and your choices

We use attribution to understand which campaigns lead to installs and subscriptions. When iOS requires tracking permission, we ask through Apple's App Tracking Transparency prompt before the permitted tracking. You can change that choice in iOS Settings. Depending on permission and configuration, attribution can involve an advertising identifier, other app/device or account identifiers, IP address, approximate region, campaign information, and purchase or usage events.

Declining tracking does not necessarily stop every network request or collection of device and IP information needed for permitted attribution, fraud prevention, or service operation. It does not authorize tracking by another method. We do not send private journal text, community or Marlo conversations, health answers, or daily-spending estimates to advertising partners for targeting.

Advertising measurement or website pixel sharing can fall within a local law's definition of a sale or sharing of personal information, even without payment for the information. Where applicable, you may opt out or limit use of sensitive information through the available tracking/cookie choices or by contacting us. Applicable law may also give you the right to exercise an opt-out through a recognized browser signal. Your website cookie choice is separate from your iOS tracking choice.

Email and push notifications

We use email for sign-in, verification, account and security notices, support, and other service messages. If we offer optional engagement or marketing emails, we ask you to opt in and provide unsubscribe or preference controls. Unsubscribing from optional messages does not stop necessary account or safety communications.

Push notifications require your device permission. You can turn them off in iOS Settings and use available in-app preferences. Apple receives a device token and the notification payload. Our in-app community notifications use generic notices rather than the words of your post or partner message; the notice type or the fact that it comes from Food Noise can still reveal sensitive context. In-app community service emails use codes, generic notices, counts, or links rather than member-message excerpts. Information you choose to send in a support email may be more detailed. Notifications sent by Discord follow Discord's settings and policies.

Resend's published standard Free, Pro, and Scale retention is 30 days for email content and logs; Enterprise arrangements can differ. Its backup period is seven days. If Food Noise ends its service account with Resend, Resend may retain remaining customer data for up to 90 days under its termination rules. Resend also uses TypeSafe to screen a sample of outgoing emails for abuse; Resend states that TypeSafe does not retain those contents or train on them. Resend's privacy and retention details.

Apple can hold an undelivered push notification until its configured expiry, up to 30 days. Apple's push-delivery documentation.

On-device features and synced blocker settings

Camera-based expression exercises, the drawn commitment signature, and local voice exercises operate on your device. We do not upload camera images, facial-expression data, the signature image, or a list of your phone contacts through these features. Dictation uses on-device speech recognition; if you then submit the resulting text to Marlo or the community, that text is processed as described above.

Screen Time enforces blocking on your device. When you save blocker settings while signed in, we also sync an encoded copy of your selection to Supabase, linked to your account, together with the blocking schedule, exercise preferences, and pause status. We use this to save and restore your settings. Apple's selection uses opaque tokens representing selected apps, categories, and any selected web domains. These are selection settings, not a record of your browsing or app-use history; encoding them does not make the account-linked record anonymous. Apple's explanation of Screen Time selections.

The country choice used to display crisis resources stays on your device. Marlo may separately receive an approximate country or region as part of the context described above.

Version 2.0.14 retires the telephone-call and voice-note setup. A phone number and recording reference saved through an earlier version can still remain with your blocker settings and sync to your account until removed. A previously uploaded recording can also be downloaded to your device. Contact us to remove retained phone-number and recording records from your account. Removing a local copy or disabling the feature does not by itself erase cloud copies. This retention does not mean a telephone-call service remains available. Device backups you manage with Apple may separately contain local app data.

How long we keep information

We keep account information, published in-app community content, and saved chats for the purposes described here until you remove them, delete your account, or the information is no longer needed. We keep Food Noise's Discord membership and server-management records as needed to manage access and handle support, safety, or legal matters. Discord's retention of information on its platform follows its own policy. The following more specific schedules apply to our in-app community and related app records; unresolved reviews, safety cases, and legal obligations can require longer retention.

  • Superseded community versions, unpublished held or screened content, and temporary moderation-review copies: Removed through scheduled deletion after 30 days.
  • Text removed through moderation: Normally removed after 90 days from removal.
  • Community report notes: Normally removed after 90 days from the latest relevant note or handling/review event, once the related review queues are closed. An unresolved review or appeal can delay removal.
  • Marlo reply reports, including the copied reply, optional note, reason, and associated identifiers and times: Normally kept for 24 months from submission, then removed through daily cleanup; removed earlier with account deletion. Clearing chat history or turning Marlo off does not delete these separate reports.
  • Community notifications, delivery records, and partner-status signals: 90 days. Revoked push tokens are removed after 30 days.
  • Verification and duplicate-request records: Expired community email codes are removed after seven days; request identifiers used to prevent duplicate actions are kept for seven days.
  • Community action records and staff access logs: Action audit records: 12 months. Staff portal access and sign-in logs: 400 days.
  • Optional account-deletion feedback: Up to 24 months. We remove the account identifier, but free text can still identify you; do not include sensitive information you want erased.
  • Android waitlist: Deleted within 30 days after the launch email, or earlier on request.

Safety evidence

For a child-safety concern, we may preserve a separate case record containing relevant messages, revisions and surrounding context, reports, and necessary account/contact/age information. It can also include recent sign-in IP addresses, device information, and times. This is separate from ordinary account records and can remain after a message, partnership, or account is deleted.

An open case is kept while it remains unresolved. If a report is filed with the appropriate authority, the normal evidence hold runs for one year after the report. If a case is closed without a report, the normal hold runs for one year from opening the case. Longer retention may be necessary for a legal obligation or lawful preservation request. Access is limited to safety and legal purposes. We may share necessary evidence with the National Center for Missing and Exploited Children or other appropriate authorities when required or legally justified; an automated flag does not itself mean a report has been filed.

Providers, backups, and deletion requests

Provider retention is separate from our app schedules. Anthropic, Resend, and Apple's push service have the specific rules described above. AppsFlyer's published end-user retention is generally no more than 24 months, subject to customer instructions and legal exceptions; partner-specific raw-data limits and aggregated reports can differ. AppsFlyer's services policy.

Backup retention depends on the applicable plan and recovery configuration. Deleted information may remain in protected backup copies until they rotate out, restricted to recovery, security, and legal purposes. We take steps to preserve deletion choices if recovery restores older records. Supabase's backup documentation.

We retain records handled by PostHog, Superwall, and Cloudflare only as needed for their stated purposes, applicable security or legal requirements, and the relevant service settings and contracts. We coordinate applicable deletion requests with them. Some hosted analytics deletions are processed in batches rather than immediately. PostHog storage and deletion, Superwall's data-processing terms, and Cloudflare's privacy policy.

Your controls and account deletion

You can edit available profile details and change notification and tracking choices. From version 2.0.14, Settings lets you turn Marlo off, delete your chats with Marlo, withdraw an existing research permission, and request account deletion. The community has separate controls for your content and sharing choices. There is no general health-permission switch in this version. For health-data withdrawal or deletion without deleting your whole account, email support@foodnoise.app. We may need to verify that the account is yours before releasing or deleting information.

Deleting your in-app community content removes the text and associated ordinary copies we control; a deleted-item marker may remain to preserve another person's reply or the conversation structure. Other members' independently authored messages are their records. Leaving a community or ending a partnership does not itself erase stored content. Ending an in-app partnership removes the participants' normal access to that chat; request deletion separately. Discord account and content controls are explained in the Optional Community Discord section. Safety evidence and legal holds remain subject to the rules above.

To withdraw health and personalization permission or remove health records without deleting your account, email support@foodnoise.app. Tell us whether your request includes profile answers, check-ins, journals, urges, streaks, activity history, Marlo, community content, and any existing research permission. We handle this request through support and explain which records can be removed and which must be retained. This is not an automatic in-app erase.

Removing server records alone does not clear copies on your devices. A signed-in app can upload locally saved records again when you use it. We may ask you to sign out on every device and stop using the affected features while we complete your request, and will give you instructions for clearing local copies. Do not assume that turning off Marlo or changing research permission also erases other health records.

A request concerning health and personalization does not by itself cancel your subscription or delete your whole account. Community content, Marlo conversations and reply reports, separate safety records, and independently authorized research records have their own controls and retention rules. If a separate existing research permission remains active, eligible onboarding, check-in, and care-demand answers can remain for that purpose; withdraw research permission separately if you also want that use to stop.

We retain earned rewards and a limited account-linked ledger to preserve your balance and prevent duplicate credit. It records which activity category earned credit, when it was completed and accepted, the local day and time-zone details, and the type, amount, and date of the reward. It does not keep the journal text or check-in answer for this purpose. This ledger is removed with account deletion, subject to a lawful hold.

We complete account deletion from active Food Noise systems within 30 days of a verified request, except information we must retain for the limited safety, legal, financial, or dispute purposes described here. We also coordinate applicable provider deletion requests. Backup expiry and independent provider safety/legal records can take longer. We will explain a material delay or an applicable retention exception. Deleting the app, signing out, or deleting your Food Noise account does not cancel an Apple subscription; manage that separately through your Apple account.

Research choices

Accepting this policy does not enroll you in research. If you previously gave separate research permission, eligible records can include onboarding and outcome answers, activity history, country, subscription and acquisition information, and identifiers needed to connect those records. Such records can initially remain linked to your account.

You can withdraw existing research permission in Settings or by contacting us. This stops future research use of your linked records; health information still needed for features you separately choose may remain. We can also consider a deletion request. Work already completed with genuinely anonymous information cannot necessarily be undone. Any new research enrollment requires separate information and consent; private journal text is not included through general acceptance of this policy.

Website cookies and the Android waitlist

Our main website uses Meta, TikTok, and Reddit measurement pixels where enabled by your choices. These can receive page and referral information, IP/device details, and actions such as tapping a download link. In Europe, optional pixels require prior consent; elsewhere, the site's cookie controls let you decline them. We do not load these pixels on the legal or waitlist pages or for visitors identified as using Android. Measurement cookies can last up to 13 months. Use the website's cookie controls to change your choice; browser controls can also block or remove cookies.

The Android waitlist uses Google Forms. It asks for email, country, confirmation that you are at least 16, and optional information such as first name, how you found us, or requested features. We use this for launch notification and planning, not unrelated marketing. You can leave the list by emailing us. The retention period is in the table above.

Security and international processing

We use safeguards such as encrypted network connections, access controls, and restricted staff permissions. No service can guarantee absolute security. Information may be processed in the United States and other countries where we or our providers operate. Where required, we use appropriate transfer safeguards, such as standard contractual clauses and the applicable UK transfer mechanism. You can request information about those safeguards from us. Accepting this policy does not waive your data-protection rights.

Privacy rights and contact

Depending on where you live, you may have rights to access, correct, delete, or receive a portable copy of your personal information; restrict or object to processing; withdraw consent; opt out of a sale, sharing, or targeted advertising; and limit certain sensitive-information uses. Withdrawing consent does not make earlier lawful processing unlawful. Some choices affect features that need the information.

Send requests to support@foodnoise.app. We will respond within the period required by applicable law, explain any applicable exception, and tell you how to appeal a denied request. You may use an authorized agent where allowed. We verify identity proportionately and do not ask for unrelated sensitive documents as a routine step. We do not discriminate against you for exercising privacy rights. You can also complain to your local data-protection authority.

If we materially change our practices, we will update this policy and give any notice or request any new permission the law requires. The date above identifies this version.