Data Retention Schedule

This page lists every class of data AR Logic LLC holds for fixRAgent, the system it lives in, how long it stays there, and the job or the request that removes it. It is the working companion to the Privacy Policy: the policy says what we collect and why, and this schedule says exactly when each thing goes.

Ask us to delete something Read the Privacy Policy
Effective 14 September 2026Last updated 15 October 2026retention-2026-10-09

When you ask us to delete it

How a deletion request reaches every copy of the database.

The live rowgoes firstat once
Server snapshotsage out7 days
The off-site copyages out14 days
Our own encrypted setsonce the last five roll forwardabout 5 weeks

From "How to ask" on this page.

The schedule

Answers and photos

The Triage Profile, the photo behind it, and what happens to each.

a triage card's record (answer, photo hash, versions, role, arm)

how longUntil you ask us to delete it

where it lives
Supabase — our database, under a random diagnosis_id
what removes it
Your request to legal@fixragent.com
privacy policy section
§8

a kept photo (repair-guidance tool, "Keep this photo" ticked)

how long30 days

where it lives
Supabase — a private bucket in the United States, named by the file's hash
what removes it
A daily sweep that deletes the file and clears the pointer, and leaves the consent record standing
privacy policy section
§3

a photo on the triage card path (home page, email, text, Shortcut, API)

how longWith us: until you ask us to delete it. At Google: 55 days

where it lives
Supabase — a private bucket in the United States, named by the profile's random id, kept with its Triage Profile from 6 October 2026; and Google — the Gemini model service
what removes it
Your request to legal@fixragent.com; Google's own 55-day expiry
privacy policy section
§3

repair-guidance results under an account

how longUntil you delete the result or the account

where it lives
Supabase — our database (diagnoses)
what removes it
Deleting it in the app, or your request
privacy policy section
§8

a guest result on our side

how longUntil you ask us to delete it

where it lives
Supabase — our database (diy_guest_scans)
what removes it
Your request, using the details held on your device
privacy policy section
§8

outcome answers

how longKept with the card, and de-identified once the card is deleted

where it lives
Supabase — our database (outcomes), under the card's diagnosis_id
what removes it
Your request, which de-identifies them
privacy policy section
§5

a thumbs-up or thumbs-down on an answer (diagnosis_votes)

how longUntil you ask us to delete it

where it lives
Supabase — our database
what removes it
Your request
privacy policy section
§8

the prompt, the photo and the answer at the model service

how long55 days

where it lives
Google — the Gemini API
what removes it
Google's own expiry
privacy policy section
§6

our permanent archive of consented outcome photos and results

how longKept, as the record of what each repair turned out to be; a photo reaches it only where you agreed to that use (on a manager's sticker or team page, unless you unticked the box)

where it lives
Hetzner — a content-addressed store on our own server
what removes it
Your request to legal@fixragent.com
privacy policy section
§7

our evaluation exports (a photo, the verdict and the human signal, under file names that are hashes)

how longKept while the engine is being measured

where it lives
Hetzner — a working folder on our own server
what removes it
Your request to legal@fixragent.com
privacy policy section
§7

Your details

Email addresses, consent, accounts, payments, and the people we write to.

your request for an API key

how longUntil you ask us to delete it

where it lives
Supabase — our database (b2b_inbound_leads): the email you gave us, what you told us you were building, your consent version, and a pointer to the key issued — never the key itself
what removes it
Your request, by email to support@fixragent.com
privacy policy section
§2.4

an email address or phone number on a card

how longUntil you unsubscribe or ask us to delete it

where it lives
Supabase — our database, next to the version of the consent line you saw
what removes it
The unsubscribe line in any card email, or your request
privacy policy section
§4

unsubscribe records

how longKept, so that the unsubscribe keeps working

where it lives
Supabase — our database (triage_email_optout)
what removes it
Kept by design
privacy policy section
§4

the record that a follow-up was started for a card

how longKept with the card, so that no follow-up is started twice

where it lives
Supabase — our database (triage_mail_log), holding a hash of the address rather than the address
what removes it
Kept by design
privacy policy section
§4

consent records (which text you saw, when)

how longKept, as the proof that consent was given

where it lives
Supabase — our database, next to the record they belong to
what removes it
Kept by design
privacy policy section
§8

feedback

how longUntil you ask us to delete it

where it lives
Resend — delivered to us as email; Anthropic — read once to categorise it and draft a reply for us
what removes it
Your request
privacy policy section
§8

account, plan and Stripe identifier

how longUntil you delete the account; Stripe keeps its own record of payments

where it lives
Supabase — our database (fixr_users); Stripe — your customer record
what removes it
Deleting the account, or your request
privacy policy section
§8

payment records

how longKept, as the record of what was paid

where it lives
Supabase — our database (payment_logs); Stripe — its own invoice record
what removes it
Kept by design, as financial record-keeping requires
privacy policy section
§8

our outreach and prospect records (section 2.9)

how longUntil the person asks to be removed

where it lives
Supabase — our database
what removes it
Your request
privacy policy section
§8

the contractor list and its send record

how longUntil the contractor asks to be removed

where it lives
Supabase — our database
what removes it
Your request
privacy policy section
§8

email you send to our addresses, and our replies

how longUntil we delete it; Google Workspace keeps mail in the mailbox until it is deleted

where it lives
Google Workspace — our mailboxes
what removes it
Your request, for a message we can find
privacy policy section
§8

Managers and buildings

What a property manager puts in, and what residents send through it.

properties and assets you register

how longUntil you delete them or the account

where it lives
Supabase — our database (properties, assets)
what removes it
Deleting them in the app, or your request
privacy policy section
§8

resident, manager and roof-inspection photos, and the intake records around them (accounts, properties, units, tickets, intake codes and their scan log)

how longUntil the account holder or the contractor deletes them or asks us to; the intake rate-limit record for 24 hours

where it lives
Supabase — private buckets and our database
what removes it
The account holder deleting them, or your request
privacy policy section
§8

a resident's email address on a ticket

how longUntil the account holder deletes the ticket or the resident asks us to

where it lives
Supabase — our database (pm_tickets)
what removes it
Deleting the ticket, or your request
privacy policy section
§8

the QR scan log (qr_scans: time, network address, browser, referring page, city, country, device type)

how longFor as long as the link exists

where it lives
Supabase — our database
what removes it
Retiring the link, or your request for the rows for your address
privacy policy section
§8

identified resident and work-order data in a property-manager pilot

how longAs the signed pilot agreement says

where it lives
Where the signed pilot agreement says
what removes it
The agreement's deletion terms, or the manager's request
privacy policy section
§2.10

Visits and tracking

Page views, analytics, logs, and the outside services a page loads.

product analytics events at Google Analytics, PostHog and Vercel Web Analytics

how longEach tool's own period, set out in the processor rows below

where it lives
Google Analytics, PostHog and Vercel
what removes it
Deleting a person and their events in each tool, on your request
privacy policy section
§8

our own event store (fixr_events: device id, events, city, region, country, browser type)

how longFor as long as we operate the service

where it lives
Supabase — our database
what removes it
Your request for your device's rows, with the fixr_did value from your browser's storage
privacy policy section
§8

error reports and hosting logs

how longEach provider's own period, set out in the processor rows below

where it lives
Sentry — error reports; Vercel — request logs
what removes it
Each provider's own expiry
privacy policy section
§8

page views and interactions

how longUp to 14 months for the data behind explorations; standard aggregated reports are unaffected by that setting

where it lives
Google Analytics
what removes it
Deleting a person's data in the property, on your request
privacy policy section
§6

product analytics events

how long1 year on the free plan and 7 years on a paid plan

where it lives
PostHog
what removes it
Deleting a person together with their events and recordings, on your request
privacy policy section
§6

the request that loads the typeface and the database client library

how longEach host's own request-log period

where it lives
Google Fonts and esm.sh
what removes it
Each host's own expiry
privacy policy section
§6

the request that loads the stylesheet on most site pages

how longIts own request-log period

where it lives
Tailwind Labs (cdn.tailwindcss.com)
what removes it
Its own expiry
privacy policy section
§6

the request that loads script libraries on seven site pages

how longThe period Cloudflare's stated business purposes and legal duties set

where it lives
Cloudflare — cdnjs
what removes it
Cloudflare's own schedule
privacy policy section
§6

the request that loads a library on the QR admin page

how longIts own request-log period

where it lives
unpkg
what removes it
Its own expiry
privacy policy section
§6

a property address, when a roof-size estimate is run

how longGoogle's own schedule; Google anonymises advertising data in server logs by removing part of the address after 9 months

where it lives
Google Maps and Google Solar
what removes it
Google's own expiry
privacy policy section
§6

a video embedded in some repair guidance

how longGoogle's own schedule

where it lives
YouTube
what removes it
Google's own expiry
privacy policy section
§6

your visit, when you follow a link to a parts or trades site

how longWe send them nothing, so we hold nothing to remove; each site keeps its own record of the visit under its own policy

where it lives
Amazon, The Home Depot, Lowe's, Angi and Thumbtack
what removes it
Each site's own schedule
privacy policy section
§6

Companies and backups

The companies that hold data for us, how long each keeps it, and our own backups.

our database, our file storage and sign-in

how longA live row stays until it is deleted here; Supabase's daily backups hold the last 7 days on our plan, and Storage objects sit outside those database backups

where it lives
Supabase — United States (US East)
what removes it
Deleting the row here, then the backup window passing
privacy policy section
§6

our web hosting, server functions and request logs, and the page views and page-load timings its analytics report

how long1 day of runtime logs, and 30 days with the observability add-on

where it lives
Vercel
what removes it
Vercel's own expiry
privacy policy section
§6

email delivery

how long30 days for email and log data, and its backups persist for 7 days

where it lives
Resend
what removes it
Resend's own expiry
privacy policy section
§6

payments and card details

how longFor as long as Stripe provides the service, and afterwards for the periods its legal, tax and fraud-prevention duties set

where it lives
Stripe
what removes it
Stripe's own schedule
privacy policy section
§6

error reports from our servers, and from your browser on the resident-intake pages

how long90 days for errors and 30 days for logs

where it lives
Sentry
what removes it
Sentry's own expiry
privacy policy section
§6

the text of feedback you send us

how longInputs and outputs are deleted within 30 days

where it lives
Anthropic — Claude
what removes it
Anthropic's own expiry
privacy policy section
§6

our own encrypted backups of the database and the code

how longThe last five sets of each kind, which reaches about five weeks

where it lives
Hetzner — our own server; each set is encrypted before it is written
what removes it
A nightly job that prunes to the last five sets
privacy policy section
§8

the off-site copy of that nightly set

how long14 days

where it lives
Cloudflare — R2 object storage in the European Union, encrypted
what removes it
A nightly job that deletes sets older than 14 days
privacy policy section
§8

server snapshots

how long7 daily snapshots

where it lives
Hetzner — rolling images of the whole server
what removes it
A daily job that keeps 7 and removes the rest
privacy policy section
§8

How to ask

Email legal@fixragent.com, or use the feedback form in the app. Write from the address you used, or give us the diagnosis_id printed on the card, so that we can find the right records. We act within 30 days and tell you when it is done, as §9 of the Privacy Policy sets out.

A deletion request reaches every copy of the database within about five weeks: the live row goes at once, the off-site copy ages out after 14 days, the server snapshots after 7 days, and our own encrypted sets once the last five have rolled forward.

Write to legal@fixragent.com Write from the address you used, or include the diagnosis_id. Email legal@fixragent.com Delete my data

Each period above that belongs to another company was read from that company's own published page on the date shown.

Every record listed.
Every way it goes.

Read the Privacy Policy Delete my data