Delete your Fig account and data

1. How to request deletion

Fig is made by FIRSTBIRD AS. You can request deletion of your Fig account and its data in either of the two ways below — both work whether you originally signed in anonymously, with an email address, or with Google, and neither requires reinstalling or downloading Fig.

Option A — Sign in and delete it yourself

In the Fig app, or in any web browser at cookwithfig.com — sign in, then go to Settings → Account → Delete account. Fig asks you to confirm twice before doing anything, since this can't be undone. Deletion starts when you confirm. We confirm success once your account has been deleted; interrupted cleanup is retried automatically. You're signed out as part of the same process.

Sign in and delete my account

Option B — Email us

Send an email to [email protected] from the email address associated with your Fig account, asking us to delete your account. We verify that the request comes from that address and complete the deletion within 30 days. If your Fig account is anonymous or signed in only with Google (no email/password ever added), mention that in your email and tell us the approximate date you last used Fig — we'll still act on the request; verification just takes a little more care.

2. Data that's deleted

Deleting your Fig account permanently deletes, from Fig's own systems:

• Your Fig account and authentication record (Supabase), including every sign-in method linked to it (anonymous, email/password, Google).
• Every saved recipe: its imported source (the URL, pasted text, or uploaded photo/file you started from — or, for a video import, the video link and its source preview), the structured recipe itself, and anything you organized it into (collections, favorites).
• Video import records (the job records and any raw material still within their short retention window — see the Privacy Policy, §6).
• Notes you wrote, and any photos you attached to a note.
• Recipe links you published stop working when your account is deleted.
• Items in Recently Deleted are included in account deletion without waiting for their normal retention period to end.
• Usage and entitlement records tied to your account: cached subscription status, AI usage counters, and Ask Fig daily usage counters.
• Usage analytics and AI cost records tied to your account — including those from before you signed up, while you used Fig as a guest: optional usage events where you enabled them, account milestones, and the records of what your AI requests and share pictures cost.
• Reports and feedback you sent from the app.
• Your RevenueCat customer record — the account-linked identifier and purchase-history copy that RevenueCat, our subscription processor, holds on our behalf (see §5).

You do not need to delete your account to withdraw optional analytics consent. Turning off Settings → About → Share usage analytics, on any of your devices, stops recording on that device at once. When the withdrawal reaches us, we remove the linked records covered by the consent you withdrew and store no further optional usage events from any of your devices; the others stop collecting when they next connect. Operational records, such as subscription status and AI cost records, are separate; see the Privacy Policy, §6.

Fig does not keep a browsable Ask Fig conversation history on its servers. Each message (and any photo you attach to it) is sent to our AI provider to generate that response. Fig does keep individual AI responses and recipe changes, linked to your account, so an interrupted request can be recovered without running the AI work again. These are deleted along with your account.

3. Data we retain, and for how long

We don't keep a separate copy of your personal data for security, fraud-prevention, or legal/accounting purposes today — Fig is small enough that it doesn't operate a distinct retention system for that. Two things outside our application, and outside our control, are worth stating plainly rather than glossing over:

• No extended backup copy. Fig's database runs on a plan that doesn't provide point-in-time recovery or a guaranteed backup schedule. In practice, that means there is no separate backup-retention window to disclose: once a deletion request is processed, your records are removed from the live database and there is no backup copy of them for us to separately purge later.
• Routine hosting logs. Like any web service, our hosting provider's own request-level logs briefly exist as an operational byproduct of serving traffic (for example, an IP address, as part of standard server operation) and roll off automatically on a short, rolling basis under that provider's own default retention — we don't export or separately archive them. These logs are deliberately minimal by design: recipe content, imported page content, and Ask Fig message text are never written to them.

Report and feedback notifications. When you send a report or feedback, we're notified by email with what you sent. When your account is deleted, we're notified too, and we delete those emails from our inbox within 30 days. The one exception: if a report concerns a serious breach of our rules or a legal claim, we may keep what's needed for as long as that matter requires.

If you've emailed us for support, that correspondence is retained like ordinary email unless you separately ask us to delete it.

4. De-identified data we keep

Fig keeps one shared, de-identified cache: when a recipe is imported from a public URL, the structured result is cached against that URL/content so that if another Fig user later imports the exact same public recipe, we don't need to reprocess it. This cache has no user identifier of any kind — it was never linked to your account and isn't affected by deleting it.

Fig also keeps daily totals without account identifiers (for example, how many people opened a screen on a given day) and counts of visits to shared recipe links by referring site.

5. Your subscription isn't cancelled by this

When we delete your Fig account, we also delete your RevenueCat customer record — RevenueCat's copy of your purchase history and the identifier linking it to your Fig account. That does not reach into Apple's, Google's, or Stripe's own systems: each store keeps its own transaction and billing records independently, for as long as its own tax and accounting obligations require, regardless of what happens to your Fig account.

6. Contact

FIRSTBIRD AS
Norway
[email protected]

See the Privacy Policy for how we handle information more generally, while your account is active.