Imprint & privacy policy
Imprint
Sebastian Wiese-Wagner
Albert-Einstein-Straße 47
c/o Autorenglück #75241
02977 Hoyerswerda
Contact
Phone: +491753644013
E-Mail: seb@center.for.cybernetic.beauty
ATMOSYNTH is built with other people's work; their licenses and notices are reproduced in full.
Privacy policy
This Privacy Policy explains how Atmosynth ("we", "us", or "our") collects, uses, and shares information in connection with the Atmosynth service. If you have any questions, contact us at seb@center.for.cybernetic.beauty.
About Atmosynth
Atmosynth is a platform for creating, publishing and playing synth patches in the browser, built on top of the AT Protocol (ATProto), the same protocol used by Bluesky. ATProto is designed so that your data lives on your own Personal Data Server (PDS). Patches, modules and the samples they use are records and blobs in your own account, not ours — but some things are necessarily kept on our servers, and this policy says which.
Information We Collect
- A cookie for authentication: we set one cookie, named “atmo_session”, and only after you begin signing in. It holds an opaque session identifier and nothing else, and exists strictly to keep you signed in. We set no cookie before you start a session, and we use no cookies for advertising, analytics or cross-site tracking. Separately, the player remembers three settings — volume, mute and the latency choice — in your own browser's storage. Those never reach our servers, and nothing about what you played or opened is written there.
- Your session: while you are signed in we store, on our servers, your account's identifier (DID) and handle, your display name and the address of your avatar, the access and refresh tokens that let us write to your account on your behalf, and the times the session was created and last used. Tokens stay on our servers and are never given to your browser. Signing out deletes that browser's session. A sign-in you begin and never finish leaves a short-lived record that expires after fifteen minutes.
- Drafts you have not published: work in the editor is autosaved to our servers, not to your PDS. A draft is private to you, has no public address and appears in no listing, and it is the one thing here that is not yet in your own account: it will not travel with you if you move your account until you publish it. We keep drafts until you publish or discard them. Audio you add to a draft is different — a sample is uploaded straight into your own account when you add it, and we keep no copy.
- Public ATProto data: we index and may cache data that is already public on ATProto — the names, descriptions, tags and timestamps of published patches and modules, who published them, and which patches fork or use which modules — so that pages and search results can be listed without reading every account. We also cache the handle that belongs to an account identifier, and the fact that we have looked one up. All of this is derived from public records and can be rebuilt from them. We do not collect or store private ATProto data.
- Reports: if you report a patch we store what was reported, the handle of the account that published it, the reason you give, and the time. We do not store anything identifying the reporter — unless you put something identifying in the reason itself, which is a free-text field in your own words and is stored as you wrote it. To stop the report form being flooded we briefly note the coarsened network your request came from — the first half of the address, never the address itself — and discard it within a day.
- Moderation decisions: where we withhold a patch, a module or an account from this site, we keep a record of what was withheld, the reason, and when it was decided or lifted.
How We Use Information
We use the session cookie and the session it names to keep you signed in and to publish, edit and delete records in your account when you ask us to. We use drafts to give you back the work you left unfinished. We use the index of public data to render listings, search and creator pages. We use reports and moderation records to run the service. We do not profile you, sell anything about you, or share any of it with third parties for their own purposes.
Third Parties
We run no analytics and embed no third-party scripts or fonts. Two things do reach beyond this site: signing in sends you to your own PDS to authorise it, and an avatar is served by redirecting your browser to wherever that account publishes its picture, so that host — often a Bluesky CDN — sees the request. Audio samples are streamed through our servers rather than linked, so playing a patch tells no one else that you did.
Data Storage and Retention
Your published content lives on your PDS. On our servers: drafts are kept until you publish or discard them; a session is deleted when you sign out, and in any case ninety days after it was last used; unfinished sign-ins expire within fifteen minutes; cached handle lookups are dropped after a week; and the index of public data is kept as long as the record it describes is published.
Server Logs
The server writes a log line for every request: the method, the address requested, the response status and how long it took. Because the address is recorded in full, those lines show which pages, patches and samples were requested, and — since a search term travels in the address — what was searched for. They do not include request headers, so no cookie, no session identifier and no browser identification is written, and Atmosynth itself writes no IP address to them.
The log goes to the server's standard output. Atmosynth keeps no log file of its own and applies no retention to it, so how long those lines survive is a property of how this deployment is hosted rather than of the software. Any reverse proxy or hosting provider in front of Atmosynth keeps its own logs, and those ordinarily do record IP addresses.
Your Choices and Deletion
Because your published data lives on your PDS, you can remove your content at the source using Atmosynth or any other ATProto client, and it stops being listed here. You can discard any draft from the editor, and sign out to delete a session. If you would like us to delete anything else we hold on our servers, write to seb@center.for.cybernetic.beauty.
Children’s Privacy
Atmosynth is not directed to children under 13, and we do not knowingly collect personal information from children.
Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date below. Your continued use of Atmosynth after an update means you accept the changes.
Last updated: 2026-08-31