Skip to main content

Trust center

What we keep, and what deletion removes.

A deletion request for a verified email removes the rows below. Audit entries keep only a hash of who acted.

What we keep, and what deletion removes.
DataWhereRemoved on deletion
account recordConvex, usersYes
breach lookupsNetlify Blobs, auditsYes
account event timelineNetlify Blobs, auditsYes
mobile push tokensNetlify Blobs, auditsYes
monitored identitiesNetlify Blobs, watchlistsYes
billing/subscription recordNetlify Blobs, subscriptionsYes
insurance policy recordsNetlify Blobs, policiesYes
uploaded vault documentsNetlify Blobs, documentsYes
phishing-simulation recordsNetlify Blobs, simulationsYes
concierge chat historyNetlify Blobs, messagesYes
concierge conversation summariesNetlify Blobs, memoriesYes
insurance claimsNetlify Blobs, claimsYes
extension bearer tokensNetlify Blobs, auditsYes
session credential epochNetlify Blobs, auditsYes
password-account email verification challengesConvex, emailVerificationsYes
seat threat-catch ledger (AE29 "ledger")Netlify Blobs, auditsYes
reported-phish records / per-seat reputation cache (AE29 "reputation cache")Convex, orgReportsYes
device check-in recordsConvex, orgSeatsYes
pending and tombstoned invitesConvex, orgInvitesYes
org membership / seat statusConvex, orgMembersHashed or expired
audit trail (AE29 "the audit event holds only the hash")Convex, orgAuditHashed or expired

The browser extension keeps a few counters on your own device: how many threats it detected, what it did about each one, and whether its warning was followed. They never reach SYBA servers, and uninstalling the extension clears them.