Your work remains yours.

If you request an app-launch email, we store your notification preference and the time you changed it with your account. This is optional, separate from signing in, and can be cancelled on your character screen. It does not subscribe you to an ongoing marketing list.

Your player characters

When early registration is enabled, Get started records your profile name, email and acceptance of the displayed notice privately in Supabase. We create an unverified account if needed; an existing account is not changed. This does not sign you in, save a character or subscribe you to marketing. You verify your email when you choose to save your hero.

Unverified registration records expire after 30 days and become eligible for cleanup. This does not automatically delete a shared sign-in account: those accounts are reviewed separately so that existing saved characters and Writer access are protected. Contact us to request deletion.

Character creation uses your profile name, character name, rules choices and any appearance and personality notes you enter. Before you meet the Dungeon Master, choices stay in the open page. Efef does not automatically save character content in browser storage; leaving before the conversation starts can lose those choices.

When you meet the AI-powered Dungeon Master, we store the conversation and character details privately using Supabase so you can return to them in the same browser. We send your profile name, fictional character choices and conversation to OpenAI to create the wizard’s replies. Choosing Bring your character to life also sends your character description and Efef’s style references to OpenAI to generate a portrait. Your email address is not included in these AI requests. Please share fictional character details, not sensitive personal information.

Unclaimed conversation and portrait access expires after seven days. Expired content is eligible for deletion through our cleanup process. A private browser cookie lets you resume that work; the portrait is not available through a public image URL. Provider processing may take place outside Australia and is subject to the provider’s applicable security and retention controls. We do not request that your character content be used for model training.

When you sign in with a verified email and save, we store your character in your private Efef account using Supabase. You can reopen it after signing in on another device, download it, or delete the saved character. Account ownership and revision checks protect it from other users and conflicting saves. This is account-private cloud storage, not end-to-end encryption. It is separate from Writer projects.

Deleting a saved character removes its name, biography and choices from the active character record. We retain an account-linked revision marker to prevent older sessions restoring deleted data. Its conversation and portrait access are revoked, and private image bytes are eligible for cleanup. Account deletion removes that marker. Authentication sessions may be stored in your browser to keep you signed in.

Founding pledges and rewards

When you choose to pledge, Stripe-hosted Checkout collects payment and billing details, including your Australian address to check the supported sales territory. We do not receive or store your full card number. Stripe processes those details under its Privacy Policy.

We store your account-linked order, amount, accepted offer and terms, Stripe references, payment/refund/dispute status and reward delivery records privately in Supabase. Stripe receives opaque order and offer identifiers, not character conversations or private artwork links. We preserve a private copy of the chosen hero name, origins and approved portrait for the rewards you request. Replacing your ordinary hero does not erase that reward snapshot or account recognition.

Financial and delivery records are separate from abandoned registration cleanup and character deletion. We retain the records needed to fulfil rewards, resolve disputes and meet accounting or legal obligations; account deletion does not erase required transaction records. Contact hello@efef.io to request access, correction or deletion. Before using any image, animation or voice provider for a personalised reward, we will identify that provider and explain what is shared. No such provider trial or automatic generation is automatically activated by making a pledge.

Who is responsible

Efef is operated by Maung Zar Ni in Australia. For privacy questions, access or correction requests, or a complaint, email hello@efef.io. Please do not include private manuscript text in email.

What we collect

Why we use personal information

• To create and secure your account, send sign-in links and provide the Writer you ask us to provide. Where relevant, this processing is necessary to perform our agreement with you.
• To prevent abuse, protect accounts, diagnose faults and keep the service reliable. We rely on our legitimate interests in running a safe service, subject to your rights.
• To answer support, privacy and legal requests and to meet obligations that apply to us.

Efef does not use advertising cookies, behavioural advertising, session replay or marketing analytics in the current service. We do not use automated profiling to make advertising, creative or account-eligibility decisions about you. Automated security and bot checks may allow or refuse an account request in order to protect the service.

An email address you control is required to create and return to an account. You do not have to provide one merely to read the public website, but without it we cannot create an account, send a secure sign-in link or provide the authenticated Writer.

Cloud saving and recovery

Typing saves to an account-scoped browser copy and crash-recovery journal first. When online, Efef sends settled changes over HTTPS to Supabase. A completed cloud save means the database has accepted that revision. Sign in to the same account on another device to retrieve it. There is no recovery kit or separate manuscript password.

If the connection fails, changes remain on this device until synchronisation succeeds. Do not clear browser data or discard the device while the status says a save is pending. Efef preserves conflicting edits for you to resolve instead of silently overwriting them. Existing local-only archives must be imported into a cloud-enabled project to join cloud saving.

Cloud history keeps up to 30 earlier restore points, at least five minutes apart during editing. Restoring creates a separate project and leaves current writing untouched. History is bounded, not a permanent record of every keystroke. Complete project exports remain available as an additional independent copy.

Service providers

We disclose only the information needed for these providers to perform their role:

• Vercel hosts and delivers the website and may process ordinary request and short-lived runtime-log data.
• Supabase provides authentication and the account-private project storage when enabled. The primary Efef project is hosted in the Sydney AWS region. Supabase processes account records, project content, earlier restore points and synchronization metadata to provide the service.
• Cloudflare Turnstile processes browser and security signals only when an account form needs a bot check. It does not receive form entries or manuscript content.
• Resend sends transactional account emails and receives the destination address, sign-in message and delivery events. Sign-in emails contain no manuscript content and email data is retained for up to 30 days under Resend's published service policy.
• Zoho Mail receives the information you choose to include when you email Efef support.

Efef does not send readable manuscript content to OpenAI, Stripe, Resend, Cloudflare, Zoho or an analytics provider. Connected story understanding and payment processing are not active in the Free Writer. When enabled, account-private cloud saving uses Supabase as described above.

If you deliberately turn on Connected story understanding for a project, Efef sends the saved passages needed for that update through its server to the disclosed model provider. Turning it off blocks new work and rejects results that arrive too late, but it cannot recall text from a provider request that has already started. The consent screen identifies the active provider and its separate retention terms before anything is sent.

International processing

Account and cloud project data are primarily stored in Sydney, Australia. Limited account, email, security or network information may also be processed in Japan, the United States, the United Kingdom, countries in the European Economic Area and other locations listed by the providers in their current subprocessor notices. Those countries may have different privacy laws. We choose providers that publish privacy, security and subprocessor commitments, limit each provider to its stated role and review those arrangements as the service changes. You may ask us where your account information is processed.

How long information is kept

• Your local copy remains in a browser until you delete it, delete your account and local copies, or clear browser storage. Cloud projects remain while your account is open, unless you delete them. The oldest recovery points expire when the per-project limit is reached.
• Your active account information is kept while your account is open. Self-service deletion removes the active authentication record, cloud projects, restore points and this browser's account-scoped Writer copy. A copy already present on another device must be cleared on that device. Project deletion retains a content-free marker while your account remains open so an offline device cannot silently recreate that project. Already-issued sign-in tokens can remain valid until their short expiry, but do not restore deleted account data.
• Transactional email data is retained by Resend for up to 30 days. Vercel makes runtime logs available to us for a limited operational period under the active plan; that viewing window is not a promise that every provider backup is erased at the same time. Scheduled daily provider backups are not currently enabled. Local recovery and cloud history do not cover loss of the entire cloud database. Any future disaster-recovery backups will be access-restricted and follow the configured provider retention, separately from active project deletion. Restoring a backup requires reapplying deletion requests. Backups reduce loss risk but do not guarantee that every most-recent offline or unsynchronised edit can be recovered.
• When Connected story understanding is enabled, temporary staged findings and their supporting passages become eligible for deletion no later than 30 days after they are created and are removed by bounded hourly cleanup, including for inactive accounts. Cleanup normally completes within 24 hours after expiry, but an operational incident or unusually large backlog may delay final removal. Validated findings and source passages copied into your project remain part of that project until you remove them or delete the project or account. Content-free job, security and cost records may be retained longer to prevent duplicate processing, enforce limits and investigate service failures. A model provider's retention is separate and is shown in the consent disclosure.
• Support email is kept only while it is needed to answer the request, protect the service or meet a legal obligation. A closed conversation may be deleted when it is no longer needed for one of those purposes.

Your choices and rights

You can export a manuscript or complete Efef project, delete a project and delete your Efef account from Settings. You may ask us to confirm whether we hold personal information about you, provide access, correct inaccurate information, delete information where applicable, restrict or object to processing, or provide portable account information. Some rights depend on the law that applies where you live. We verify account ownership before acting on a request.

Email hello@efef.io to make a request or complaint. We will acknowledge it and aim to respond within 30 days. If you are not satisfied, you may contact the Office of the Australian Information Commissioner or the privacy regulator where you live.

Security and data breaches

We use local recovery, account isolation, transport encryption and bot protection. Cloud-enabled projects use owner-only database rules, revision guards and restricted write commands. Authorised operational access is limited to providing, securing and recovering the service. These measures do not protect readable text while it is open on an unlocked device, from a hostile browser extension or from compromised Efef code delivered to that browser. No internet service can promise absolute security. If a breach is likely to cause serious harm, we will notify affected people and the relevant regulator where the law requires it.

Age and changes to this Notice

Efef accounts are for people aged 18 or older. We do not knowingly collect account information from children. We may update this Notice as the service changes. We will post the new date here and give reasonable notice before a material change takes effect. Any future AI feature will explain what content leaves the Writer and require your choice before processing. We will not silently turn cloud saving into model training.