Privacy
Last updated October 7, 2026.
This notice describes stringdtheory at stringdtheory.com. Contact the operator at punchingelm@gmail.com about privacy or account data.
Browser drafts and account saves
Your local workspace, notebook and attached media are saved in this browser's storage. They are not sent to an account merely because you select a file, sign in or import a backup. Clearing browser data can remove those drafts. A workspace export contains the local notes and attached media you include.
When you choose account Save or an account archive action, the selected content and referenced media are sent to the server. The server stores account ownership, saved content, revisions, file metadata and records needed to safely retry a Save. Uploaded media is scanned and normalized on the application's host before it is accepted. Private account content is accessible through account authorization; it is not automatically a public share.
Sign-in and email
Password accounts use an email address and a password hash. The server also records the account's display name, creation information and email-verification status. Verification and password-recovery messages use the account address when email delivery is enabled.
Google sign-in requests sign-in identity and email permissions. It uses Google's account identifier and an available verified email address to identify your stringdtheory account.
X sign-in requests read permissions needed to retrieve the signed-in account's identity and available email address. X's response also provides basic profile information such as a name. stringdtheory uses the identifier, available email and display name for sign-in; it does not retrieve posts, direct messages or contacts, and does not request permission to post.
Provider authorization tokens are used during sign-in and are not retained in the account database. Provider identity links are retained so you can sign in again. An email address supplied by a provider does not automatically merge separate stringdtheory accounts.
Sessions and service security
The account service uses a session cookie and server records to keep you signed in and protect requests. Browser storage also keeps local drafts and interrupted Save information. The server processes network addresses to enforce abuse limits and stores keyed identifiers for those limits. Service diagnostics may record errors. The application does not include advertising or third-party analytics trackers.
Sharing and other services
Publishing a share is an explicit action. Anyone with the share link or code can access the published board snapshot and its included media while that share is available. Recipients can retain their own copies; revoking a link does not remove those copies.
A share code copies one saved version of one board. Later edits never change that shared snapshot.
The hosted application and operational backups use OVHcloud infrastructure. The operator can access server data to maintain the service and handle support. If account email delivery is enabled, its delivery service receives the destination address and message. Google and X handle their own sign-in pages under their own policies. Choosing to play a YouTube source loads a YouTube player, which can send information about that request to YouTube. External links take you to the linked service.
Optional board translation
Changing the interface language uses translations bundled with the application and does not send board content for translation. If you sign in and explicitly choose to send board text to Google Cloud Translation, the server sends the board title, notes, captions and contact-card text for that request. Images, audio, video, URLs, filenames, Trash, dossiers and the workspace notebook are excluded. Review the preview and confirm before applying it; account Save and public sharing are separate actions.
Translation results may be cached in server memory for five minutes for your account. Character-use counters are retained for a 24-hour allowance window. Translation can be unavailable or limited; it does not run automatically when you switch language.
Retention and your choices
Account records and saved content remain until you remove content, delete the account, or the operator removes them. Deleting your account immediately disables its sessions, saved boards, disks, files and share links. Live account data is retained for 30 days so you can recover it.
During those 30 days, sign in with the account's password or an already linked provider and choose Restore account. Signing in alone does not restore the account or allow access to saved content. Restoration keeps the same account and saved work; unrevoked, unexpired share links become available again. At the recovery deadline, restoration ends and server cleanup permanently removes live account data.
Account deletion does not erase drafts on your devices, workspace exports or copies other people have already imported. Operational backups may retain earlier copies until removed under the operator's backup retention policy; the 30-day recovery period does not promise erasure of every backup.
You can export your local workspace, delete saved boards through available controls, revoke your shares, and manage linked sign-in methods while keeping another available sign-in method. You can also revoke provider access in your Google or X account. Revoking that access does not itself delete your stringdtheory account or local drafts.
Use Delete account in the account window for self-service deletion. For an account data or export request, contact punchingelm@gmail.com. The operator may need to verify account ownership. Do not send your password or a verification or recovery link.