Privacy Policy

The quick read

• Private by design. Beta Farts go to 1–20 accepted friends you select. Groups are private selection shortcuts; the Service does not show recipients the group name or other recipients. FWF does not offer a public Fart Map in the current beta.
• Your journal stays on your device. If you turn on location recording, exact journal coordinates are stored locally and are not sent to FWF, analytics, notifications, crash reports, or map providers. An IP address may still reveal an approximate area when your device uses any online service.
• Camera use is a separate choice. Ordinary Listen does not initialize the camera. A reaction clip is recorded only after you choose Listen + React, grant permission, and consent. You preview it before deciding whether to send it to the original sender.
• No ads or data brokerage. The current beta does not sell personal information, share it for cross-context behavioral advertising, or use it for targeted ads.
• You have controls. You can block or report people, change notification and reaction settings, stop future location recording, and request or initiate account deletion.

1. Scope and who controls the information

William Henry Mayo is the operator responsible for personal information handled by FWF. Contact him about privacy at [email protected]. This policy applies only to the Service. Apple, Google, Supabase, Sentry, and other services have their own privacy notices for information they independently control.

Legal-review requirement: Complete the mailing address (191 Pennsylvania Ave; city, state/province, postal code, and country pending) and confirm the required privacy-responsibility designation and disclosures for the US and Canadian launch.

2. Information we handle

Account and profile information

Email address, authentication-provider identifiers, account and session records, Fart Tag/username, display name, profile image, optional profile details, settings, and the version and time of your legal acknowledgments. If you sign in with Apple or Google, we receive the information that provider makes available under your settings.

Content and communications

Fart audio you record or send, replies, reaction clips, effect choice, delivery metadata, Saved references, Inbox state, and messages you send to support. Content may include another person's voice, face, surroundings, or other personal information. Do not record or upload anyone without the permission required by law.

Friends, safety, and service activity

Friend requests and connections, sender-only group names and membership selections, blocks, reports, send and delivery records, authorized listen events, reaction and reply relationships, notification state, and other records needed to provide and secure the private social loop. An ordinary audio-only listen does not create sender-visible listen evidence. We may derive limited, privacy-safe operational measures, such as whether a send was delivered or a reciprocal exchange occurred; the current beta does not run a general-purpose third-party product-analytics feed.

Camera, microphone, photos, and local files

FWF accesses these only when needed for an action you choose and subject to device permission. Temporary recordings and previews may exist on your device while you create, review, send, or discard content. Selecting an avatar may give FWF access to the photo you choose.

Location

The optional Fart Map in the current beta is a private, account-scoped journal of your own accepted sends. Exact coordinates are captured only after you turn on location recording and grant foreground permission. They remain in the app's local store and are not included in a send. The send flow does not ask for location permission.

Like most online services, our infrastructure may receive an IP address when your device connects. An IP address can indicate an approximate location; we do not use it to populate your private journal.

Device, network, push, and diagnostics

App and operating-system version, device and network characteristics, IP address and request time, security and server logs, push-notification token, delivery status, and error/performance diagnostics. If Sentry is configured, FWF disables its default personal-information setting and applies redaction to error events and breadcrumbs. Performance traces and session information are also enabled in the current configuration. Error-event redaction does not establish what every diagnostic channel sends; release-specific payloads and provider retention must be verified before publication.

Website connections and browser choices

The website and short-link service receive network requests, including IP addresses and technical request information, to deliver pages and resolve links. The current website source does not include advertising trackers. This is separate from the app’s authentication, push and diagnostic services.

Release verification: confirm deployed hosting logs, cookies or similar storage, third-party collection over time and across services, and responses to Do Not Track and applicable opt-out preference signals before finalizing the website disclosures. Do not infer these facts from the absence of advertising in the source.

Information from others

Another user may send you content, invite you, report an interaction, or include information about you in content. Authentication providers, app stores, infrastructure providers, and security services may also send us information needed to complete a request or protect the Service.

3. Why we use information

• create and secure accounts; authenticate sessions; and record required legal acknowledgments;
• deliver private Farts, replies, reaction clips, Inbox items, signed media, Saved items, and requested notifications;
• apply friendship, block, consent, permission, audience, and media-access rules;
• operate support, investigate reports, prevent fraud and abuse, enforce our Terms, and protect users and the Service;
• diagnose failures, maintain reliability, and measure limited beta operations without sending exact journal coordinates;
• comply with law, respond to valid legal process, establish or defend legal claims, and complete a corporate transaction; and
• ask for consent before using information for a materially different purpose when the law requires it.

We seek consent where required and use legal exceptions only where applicable law permits. Optional camera capture, location recording and tone export have separate choices; accepting this policy does not turn them on. The intended launch is limited to the United States and Canada; expansion requires review of local notices, consent and transfer requirements.

4. When information is disclosed

People you choose and people involved in an interaction

Each selected recipient receives the Fart and information needed to understand who sent it. Group names and the other recipients are not included in their delivery information. If the recipient deliberately sends a reaction clip, the original sender can view that private clip during its availability window. Your profile may be visible to you, accepted friends, and other users in the limited ways needed for friend search and requests, subject to block and safety rules.

Optional tone files that leave the app

If the original sender enables Let friends save farts (off by default), an eligible friend may export a received recording as a ringtone or text-tone file of up to 30 seconds through the device share sheet. Authorization checks the sender’s permission, the friendship, and blocks in both directions. Reaction clips are not exportable through this feature.

The recipient chooses the destination outside FWF. That destination may receive the audio and apply its own privacy practices. Turning the setting off, unfriending, blocking, or deleting an account cannot recall a file already exported. FWF attempts to clean up its temporary export files, but cannot delete copies kept by recipients or destination apps.

Service providers

We use providers to perform services on our behalf. The expected beta providers include Supabase for authentication, database, Edge functions, and private storage; Firebase Hosting and Cloudflare for website hosting, delivery and protection, Firebase Cloud Messaging and Apple’s push service for notifications; Sentry for error, session, and performance diagnostics when configured; Apple and Google for optional sign-in; and hosting, email, or support providers used for the website and support requests. Depending on their role, providers receive account identifiers, content, push tokens, diagnostics, or network/request data. We remain responsible for our own information practices; a provider’s separate policy does not replace this notice. The final release must verify the provider inventory, contractual restrictions, and processing locations.

Legal, safety, and corporate events

We may preserve or disclose information if we reasonably believe it is necessary to comply with law or valid legal process; protect a person from harm; investigate fraud, abuse, or a security incident; enforce our agreements; or protect rights and property. We may disclose information in a merger, financing, reorganization, bankruptcy, or sale of all or part of the business, subject to appropriate confidentiality and notice where required.

No sale or targeted advertising

The current beta does not sell personal information, share it for cross-context behavioral advertising, or use personal information for targeted advertising. If that changes, we will update this policy and provide any notice and choice required by law before the change applies.

5. How long information is kept

Legal-review requirement: Validate these periods against the production provider configuration and adopt an internal retention schedule before approval. A policy cannot substitute for working deletion jobs.

6. Your choices and privacy rights

• Account and profile: review or update available profile details in the app.
• Camera, microphone, photos, location, and notifications: use in-app controls and iOS Settings. Withdrawing permission may disable the related feature but does not undo content already sent.
• Reaction clips: use ordinary Listen without a camera, discard a preview, change your default or per-friend reaction preference, or revoke consent for future capture.
• Tone export permission: turn off Let friends save farts to prevent new authorized exports of your recordings. This does not remove files already exported.
• People and safety: block, unblock, unfriend, or report through available controls.
• Location journal: turn off recording to stop new coordinates. Existing entries remain until account/session cleanup or removal of app data. FWF cannot export exact journal coordinates from its servers because the coordinates are not sent there.
• Account deletion: start deletion in the app. The app attempts to delete server account data and clear local session, queue, media, cache, and journal state. If it cannot confirm completion, contact [email protected].
• Access, correction, deletion, portability, restriction, objection, or appeal: email [email protected]. Rights vary by location and may be subject to identity verification and legal exceptions. We will not discriminate against you for exercising an applicable privacy right.

Request an export of your data in a portable format by emailing [email protected]. The export will not contain exact journal coordinates because those coordinates stay on your device.

Canadian users: you may request access to and correction of your personal information, information about its use or disclosure, and a portable copy of eligible information where applicable law provides that right. You may withdraw consent subject to lawful restrictions and reasonable notice; we will explain the effect on features that need that information. You may raise concerns with us or with the Office of the Privacy Commissioner of Canada or the provincial privacy regulator with jurisdiction. Acknowledging this policy does not replace separate, meaningful consent when it is required.

We may deny or limit a request when permitted by law—for example, if we cannot verify the requester, the request would expose another person's information, or retention is required for security or legal obligations. We will explain a denial where required and respond within the time required by applicable law. You may appeal by replying with “Privacy Appeal” in the subject line, and may complain to the privacy regulator or attorney general with authority where you live. Where applicable law permits, an authorized agent may submit a request, subject to verification of their authority. Do not email a password or unnecessary identity documents.

7. Security and the limits of privacy

FWF uses measures designed to reduce risk, including authenticated access, database row-level rules, private storage, short-lived signed media links, account-scoped client state, consent checks, and diagnostic redaction. The Service does not provide end-to-end encrypted messaging: authorized infrastructure processes content for delivery and the purposes described in this policy. No service is perfectly secure. A recipient can play content aloud, record it with another device, or misuse what you send. Send only to someone you trust, and report suspected unauthorized account access promptly.

8. Children and teens

The Service is not directed to children under 13 and is not available to anyone below the higher minimum age required where they live. FWF does not provide a separate child experience. If you have not reached the age of majority where you live, use the Service only with permission from a parent or legal guardian, and ask them to review the Terms and this policy with you.

If you believe a child used the Service contrary to this rule, email [email protected]. We may request information reasonably needed to investigate. If we learn that we collected personal information from a child below the applicable minimum age without legally required authorization, we will take steps to delete it as required by law. The proposed 13+ minimum is pending owner confirmation. For Québec users under 14, the required parent/guardian consent must be obtained before collecting personal information, or those users must remain ineligible until that process exists. Teen consent information must suit the user’s maturity. Terms alone do not establish compliance with children’s privacy law.

9. U.S. and Canadian users; processing across borders

The intended launch covers the United States and Canada. Providers may process information outside your state, province, or country, including in the United States. Information processed abroad may be accessible to courts, law enforcement or other authorities under local law. Contact [email protected] for information about providers, processing locations and safeguards.

Required before approval: verify the actual countries and provider agreements, designate the person responsible for privacy, and complete applicable Québec privacy impact assessments, cross-border assessments, and provincial notices. The policy must reflect actual operations; this draft does not establish Canadian data residency or a completed transfer assessment.

10. Changes to this policy

We may update this policy to reflect changes in the Service, law, or our practices. We will change the date above and provide additional notice when required. If a change materially affects how we handle information already collected, we will seek consent when law requires it. The app's legal-release process may require you to review the exact approved policy before account use continues.

11. Contact us

Privacy questions or requests: [email protected]
General support: [email protected]

Operator: William Henry Mayo. Mailing address: 191 Pennsylvania Ave (remaining address details pending). The operator confirms these email addresses are monitored. Complete the postal address and document request-verification, response and escalation procedures before approval.