Privacy notice

FYInbox is the notification system for people and agents. Project notifications belong in a central FYInbox inbox, outside conversation threads and email. This notice describes the processing used to create and operate a personal account.

FYInbox determines how account administration, authentication, security and support data is used. You choose the content submitted by your projects and authorized producers. Avoid personal data that is unnecessary for a project notification; contact us before using FYInbox for processing that requires a separate data processing agreement.

The service handles only the data needed to operate the account, receive project notifications, secure access and provide optional delivery features.

• Account data: email address, display name, password hash, sessions and preferences.
• Project data: projects, source credentials stored as digests, notification titles and bodies, tags, metadata, actions, severity and timestamps supplied by the account holder or a producer they authorize.
• When authentication email is enabled, Resend processes the email address, verification or recovery message content and delivery metadata.
• MCP and OAuth connections: client registration details, approved projects and scopes, consent records, credential digests, expiry and revocation records. An authorized agent can access only the operations and projects allowed by its grant.
• Support: your email address and the minimum information you choose to include in a help or privacy request. Support messages may pass through Cloudflare Email Routing and the support mailbox.
• Optional Web Push: browser push endpoint, cryptographic material, device preferences and delivery status.
• Security and operations: request identifiers, redacted errors, authentication events and aggregate ingestion measurements.
• Audience measurement: public paths, referrer origin, campaign parameters and allowlisted product events in self-hosted Umami; account-linked events use an HMAC pseudonym rather than an account identifier.

We use account and authentication data to provide the service you request, handle support and privacy requests, and protect accounts against abuse. Security and minimal operational records support our interest in keeping the service reliable and secure. We also handle data when required to meet applicable legal obligations.

Optional Web Push requires your browser permission and subscription and can be disabled. Authorizing an MCP connection gives the selected client access within the projects and scopes you approve; you can revoke that connection. We do not use authentication email as a mandatory marketing subscription.

FYInbox uses the following technical recipients only where their function is active. Audience measurement uses self-hosted Umami when enabled; it is not a separate analytics SaaS recipient.

• The VPS hosting provider stores the application, PostgreSQL data, operational logs and backups. This notice does not identify a verified contracting entity or contractual processing location for that provider; contact us for information before submitting data with specific hosting requirements.
• Cloudflare provides DNS, proxy and support email routing services and handles network metadata and incoming support email. Its public DPA describes processor terms and international-transfer safeguards, including EU standard contractual clauses where applicable.
• When authentication email is enabled, Resend, operated by Plus Five Five, Inc., processes authentication email addresses, message content and delivery metadata. Its public DPA describes processing locations and international-transfer safeguards; those published terms do not by themselves establish the configuration or agreement of a particular account.
• Apple, Google, Mozilla or Microsoft Web Push infrastructure may carry an optional push notification, depending on the browser and device selected by the user.

Active account data is kept while the account is in use. Notifications remain until account deletion or an applicable retention rule removes them. There is currently no individual notification deletion control. The source storage limits still apply. This is not a promise of unlimited history or storage.

Sessions expire after 30 days. Authentication links expire or become unusable when consumed, superseded or invalidated by a password change. MCP access tokens last at most one hour and grants at most 30 days; revocation can end access earlier. Expiry or revocation prevents use of a credential and does not by itself erase its stored record.

Operational logs and recovery copies rotate according to configured size and backup-count limits rather than a guaranteed number of days. Account deletion removes active account data; recovery copies can retain it until rotation, and deletion must be reapplied after a restore. For self-hosted analytics, retention depends on the deployment configuration; no fixed deletion period is promised here. Support messages are handled to resolve requests; no fixed automatic deletion period is represented here. Contact us about deletion or retention requirements before sharing sensitive information.

Resend's public DPA describes processing while its agreement is active and deletion of customer data within 90 days after the Resend account ends. That criterion is separate from deleting your FYInbox account or the validity period of an authentication link.

Authenticated account controls provide a personal NDJSON export and account deletion. Depending on applicable law, a person may also request access, correction, deletion, restriction, portability or objection, and may complain to the relevant supervisory authority. Requests are verified with the minimum data needed and never require a password, session token or API key.

For a privacy request, email the verified contact below. Account controls do not shorten the expiry of isolated recovery copies or a provider's independently applicable retention requirement.

[email protected]

The authenticated application uses an HTTP-only session cookie. The browser also stores interface preferences such as theme. Public audience measurement uses self-hosted Umami; the FYInbox integration does not set an analytics cookie. Network requests still expose IP address and user-agent metadata to the infrastructure, and account-linked events use a pseudonym rather than being anonymous.

Public paths, referral origins and campaign parameters help us understand how people discover the service. Selected product events help us understand whether core workflows work. Measurement does not include private notification content or credentials. A cookie-free implementation does not by itself establish an exemption from consent requirements.