What we keep, and why.

Your account

We store your email address, a password hash and hashed session tokens to provide your account and sign-in. Your password is not stored as readable text.

Optional Google sign-in

When Google sign-in is connected and you choose it, Google provides an account identifier, verified email address and profile name. We keep the identifier with your Foyer account to recognize future sign-ins. We do not request access to your Gmail, Drive, contacts or calendar, and do not store Google access or refresh tokens.

Account email

When email delivery is connected, you can request password-reset and email-verification messages. The configured email provider receives the destination address and message, including its one-use confirmation link. Foyer stores a hash of that link token with an expiry time. Verification links are tied to the email address on your account.

Your drafts and published page

Page content stays in your private draft until you explicitly publish it. Editing a published page creates draft changes; visitors continue to see the published version until you publish again. Anyone can view content on a published page.

The editor also keeps a recovery copy of unsaved edits in the current browser tab. You can restore or discard it; recovering edits does not save or publish them automatically.

Optional writing assistant

When the writing assistant is connected and you request a suggestion, your request and selected page text are sent to OpenAI. We do not automatically include your audience contacts, account email, destination URLs or uploaded images. Anything you include in your own request is also sent, so include only information you want the assistant to use.

We keep the proposed changes and their previous values so you can review, apply or undo them. Applying a suggestion changes only your private draft; publication remains a separate action. The assistant can make mistakes, so review its suggestions before using them.

Images you upload

Uploaded images are available to you while they are only used in your draft. An image becomes publicly accessible when it is included in a published page. Taking the page offline or removing the image from the published version withdraws that access, although a previously loaded image can remain briefly in a browser cache.

Email signups

If a visitor explicitly opts in to a page's email signup, we store their email address and consent record for that page owner. The owner can view, export and delete those records. Foyer does not currently send marketing emails on the owner's behalf. Page owners are responsible for how they use the information visitors share with them.

Page activity

We record page views and link clicks, the referring website's host when available, and source and campaign labels supplied in the page address. We do not store the full referring address, build IP-based visitor profiles or fingerprint devices. The owner preview does not collect page activity.

Abuse prevention

Some requests are limited to reduce abuse. We store hashed identifiers and expiring counters for these limits; they are separate from page activity and are not visitor profiles.

Cookies and other sites

A session cookie keeps you signed in to the editor. Foyer's page activity does not use advertising or analytics cookies. Following an external link or loading third-party media can share information with that service under its own policies.

Deleting your data

Deleting your account removes your page, links, activity records, collected contacts, uploaded assets, connected sign-in records, account-link tokens and saved AI suggestions from the service. Previously loaded public images may remain in browser caches for up to five minutes. We cannot remove copies that other people have already downloaded or exported.

About this draft

This notice describes the current beta implementation. The operator's legal identity, a verified privacy contact and the final production policy still need to be established before public launch. Account and page deletion are available in Settings.