Footprintreduction

Backend memory + remove cascade

How Footprint is designed to work

Honest product shape — a ledger, a cascade, and a receipt. No magic wand.

• 1 · Register a loginWhen you sign into a service through SILOCK (or mark an account yourself), the system records service, handle, scopes, and the official delete path — only with your consent.
• 2 · Local login ledgerA private map on your machine: what you use, what data categories it may hold, and how to leave. Not a cloud dossier of everyone you ever visited.
• 3 · Ask to removeOne intent: remove this account. SILOCK confirms control, then runs the provider’s official deletion or data-erasure path where one exists.
• 4 · Purge our sideTokens, vault entries, caches, and exports SILOCK stored for that account are deleted or sealed per policy — so “leave the site” also means leave our store.
• 5 · ReceiptYou get a step log: what was requested, what completed, and what residual public copies may still exist outside SILOCK’s reach.
• 6 · Legal railsSelf and proven identity only. Official APIs and documented portals. No unauthorized access, no “scrub the web of someone else.”

Coming soon package

What we will not claim

Footprint cannot force every mirror, search index, or third-party archive to forget you. It can make your account graph legible, drive official leave flows, and zero out what the private OS still holds.

• In scope Accounts you control · SILOCK-held data · consent ledger
• Out of scope Third-party scrub without rights · credential abuse · doxxing
• Status Pipeline design · not general availability

Founding access