Privacy
This page explains what Shared Memory Backups stores, where it stores it, and what happens on this website. It describes one person's private utility, not a product offered to the public.
Setup status: nothing is running yet
The utility is still being set up. No scheduled backup job is active, no backup has been uploaded as part of a working cycle, and retention is a planned policy rather than an operating one. Wording below such as "is intended to" or "planned" is deliberate. This page must not be read as describing a deployed, functioning backup service.
Who this covers
Shared Memory Backups is a private utility with exactly one user: its owner. It backs up that owner's own database into that owner's own Google Drive account. There is no sign-up, no invitation, no multi-user mode, and no way for anyone else to store data through it. There is no separate customer, tenant, or user base whose data is involved.
What is stored, and where
- On the machine that runs the backups
- The owner's shared-memory database and the encrypted snapshot files produced from it while a backup cycle is in progress.
- In the owner's Google Drive
- Only encrypted backup files. The data is encrypted before it is uploaded, so what the storage provider holds is ciphertext, not a readable database.
- The key that decrypts the backups
- The private decryption identity is kept separately, off the machine that runs the backups, and is not stored in Google Drive or on the backup host. Only the matching public key needs to be present where backups are made. Without the private identity, the encrypted files cannot be turned back into a database.
- Google authorization tokens
- The credential that lets the utility write to the owner's Drive is held privately, in a restricted location on the owner's own machine, and is used only to access the backups. It is not published, shared, sold, or used for anything other than backup access.
Google account access
Which permission is requested
The utility requests the Google Drive drive.file permission
only. That permission is limited to files the utility itself creates, plus
files the owner explicitly opens or shares with it. It is not a
full-Drive permission, and it does not grant access to the rest of the
owner's Google Drive, to Gmail, to Photos, or to any other Google service.
Who handles sign-in
Sign-in is handled entirely by Google's standard OAuth consent flow. The utility never sees, asks for, or stores the Google account password. It receives only the authorization result Google issues for the requested permission.
Questions about the Google permission screen
For anything about the consent screen itself, use the support contact shown on that Google consent screen. No separate contact address is published on this site.
Retention (planned)
The intended retention policy is 14 daily copies and 8 weekly copies. Older copies would be removed as new ones are created, so the practical history is roughly two weeks at daily resolution plus two months at weekly resolution.
This is a plan, not something already being enforced by a running job. Retention is one of the parts of the utility that is still being set up.
The owner's controls, and what each one does
- Revoke the utility's access to the Google account
- Access can be revoked at any time from the Google account's own third-party connections page. Revoking stops the utility from obtaining new authorization.
- Stop the automation
- Turning off or disabling the backup job stops new backups from being made and uploaded. Stopping the automation is separate from deleting what is already stored: existing encrypted copies remain in Drive until they are removed.
- Delete stored backups
- Removing backup files is a deliberate, separate step, done in Google Drive or by an explicit deletion action.
Revoking access does not delete the files. Revocation ends the ability to reach the account; the encrypted backup copies that already exist stay where they are until someone deletes them. Likewise, deleting the files is not the same as revoking access.
What this website does
These pages are plain static HTML and one local stylesheet. They contain no analytics, no tracking pixels, no advertising, no third-party embeds, no external fonts, no external images, and no JavaScript at all. They set no cookies and store nothing in your browser. There is no form to fill in and nothing to submit.
One honest caveat: the pages are served by a third-party static hosting provider, and any provider (including this one) may automatically process standard technical request data — such as IP address, request time, the requested URL, and user-agent string — in order to deliver the pages, keep them available, and protect against abuse. That happens at the hosting layer rather than in the pages themselves, and this site makes no promise about what the hosting provider logs or how long it retains it. Because the pages contain no analytics or tracking code, this site does not receive, read, or use that data itself.
Limitations, stated plainly
- This is a small personal utility, not a commercial backup product. There is no service-level agreement, no support commitment, and no guarantee of availability.
- There is no guarantee that any particular backup succeeds, is complete, or can be restored. A restore has to be tested to be trusted.
- The utility is still in setup, so these properties are statements of design intent, and the code that enforces them is still being finished and verified.
- Encryption protects the contents of a backup file. It does not hide the existence of the file, its name, its size, or the fact that a backup happened, from the storage provider or from anyone who can see the account.
- Anyone who obtains the private decryption identity can read the backups. Keeping it safe is a human responsibility, not a property of this site.
- This page may need to change as the utility is completed. The date below shows when it was last written.