Privacy policy

Last updated: 17 November 2026This translation is for information only. The German version is legally binding.

In short: we do not track you and we show no advertising. On your device we only store your settings, and we only process data that is necessary to run the website or that you send to us yourself.

01Controller

The party responsible for data processing on this website is Elias Alexander Friedrich, c/o Online-Impressum #6682, Europaring 90, 53757 St. Augustin, info@synapselabs.studio. You can find the full details in the Legal notice.

02Overview

This privacy policy applies to the website synapselabs.studio and to the services of Synapse Labs. Section 1 names the controller. What applies to all services is in sections 3 to 6 (hosting and server log files, cookies and local storage, bot protection, security and backups). The Synapse Labs account is described in sections 7 to 10 (account, Synapse+ and contracts, AlphaCloud in the account, data export and deletion). After that there is one section each for Axon (11), glia (12), lust.bio (13), the Minecraft server Cortex SMP (14), Synapse Support (15) and Synapse Ideas and Synapse Bugs (16). The services of the website are in section 17 (contact forms, newsletter and dev updates, live player counts, fonts, links, short links) and section 18 (status page). For our team, section 19 (hub, mailboxes, chat) and section 20 (confidentiality agreement) apply. Section 21 says where the retention periods are, and section 22 names your rights.

03Hosting, Cloudflare and server log files

This website runs on our own server in a data centre of Hetzner Online GmbH in Germany. Requests reach the server via the network of Cloudflare, Inc. (USA), which encrypts the connection, caches content and fends off attacks. Cloudflare is certified under the EU-US Data Privacy Framework.

When you open a page, technically necessary data transmitted by your browser is processed: IP address, date and time, the page requested, referrer URL, and browser and operating system. We use this data to run the website securely and reliably. The legal basis is our legitimate interest under Art. 6(1)(f) GDPR. Our server does not keep access logs with IP addresses. Technical logs of our services, for example error messages and the delivery logs of our mail server with the sender and recipient of a mail, are deleted after 14 days. We delete sign in logs of our team services that contain IP addresses after 7 days.

04Cookies and local storage

On your first visit we ask you in a cookie banner what we may store on your device. There are two categories, on synapselabs.studio two more for statistics and marketing (see below). “Necessary” is always active because the site does not work without these entries; the legal basis is § 25 Abs. 2 Nr. 2 TDDDG, and for the processing Art. 6(1)(f) GDPR. “Preferences” is optional and only active after your consent (§ 25 Abs. 1 TDDDG, Art. 6(1)(a) GDPR). Without consent, a chosen setting only applies while the page is open, and we delete any preferences already stored. We store your choice in the cookie “sl-consent” for the domain synapselabs.studio (the time and which categories you allowed or declined, 12 months, a cookie without HttpOnly so that the banner can read it) and as a copy in the Local Storage of the respective site. It applies to all Synapse Labs sites: synapselabs.studio, acc.synapselabs.studio, support.synapselabs.studio, ideas.synapselabs.studio and bugs.synapselabs.studio. Each of these sites only asks about the categories it uses and that you have not decided yet (for example “Statistics” on synapselabs.studio if you chose in the account first). Support and Synapse Ideas and Bugs use no optional category: they show no banner and store only what is necessary (including the draft of a form, see sections 15 and 16); “Cookie settings” in the footer there shows what is stored and lets you change the shared choice for the other sites. Axon, glia and lust.bio each have their own banner and do not read this cookie. You can change or withdraw your choice at any time via “Cookie settings” in the footer of any of these sites, just as easily as you gave it; a withdrawal then applies on all five sites. The cookie is sent along with every request to these sites, but we do not evaluate it on the server and do not store it; the Local Storage stays on your device. The language is derived from the address of the page and is not stored.

On synapselabs.studio the following are necessary: “sl_pass” (cookie, only for our team during the preview before launch, 12 hours), “sl_team_login” (cookie, protects the team sign-in process, 10 minutes), “sl-consent” (cookie with your choice in the banner for all Synapse Labs sites, 12 months, plus a copy in Local Storage) and Cloudflare Turnstile (bot protection, only in the contact forms and when submitting on ideas.synapselabs.studio and bugs.synapselabs.studio, see section 5). Under “Preferences” falls “sl-prefs” (Local Storage, your light or dark theme, until you change it). Under “Statistics” fall “_ga” and “_ga_E17SEBV645” (Google Analytics cookies, 2 months each). “Marketing” sets no cookies of its own on our site; Google stores what it needs on its side.

Statistics (only on synapselabs.studio): with your consent in the category “Statistics” we use Google Analytics 4, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (“Google”). Only after your consent does your browser load the script from googletagmanager.com and set the cookies “_ga” and “_ga_E17SEBV645” (2 months each). Google Analytics then records which pages you open, for how long and in which order, where you come from (referring page and an approximate region derived from your IP address), device, browser, screen size and language, as well as scrolling, clicks on links to other sites and downloads. Google Analytics 4 does not store full IP addresses. With “Statistics” alone, Google signals and personalised advertising are off (see Marketing); the data is kept for 2 months. The purpose is to understand which content is used so that we can improve the website. The legal basis is your consent (§ 25 Abs. 1 TDDDG, Art. 6(1)(a) GDPR).

Google processes this data as our processor. Data may be transferred to Google LLC in the USA; Google LLC is certified under the EU-US Data Privacy Framework, for which an adequacy decision of the EU Commission exists (Art. 45 GDPR). You can withdraw your consent at any time via “Cookie settings” in the footer: we then stop measuring at once and delete the Google Analytics cookies on your device. More on how Google handles data: policies.google.com/privacy.

Marketing (only on synapselabs.studio, builds on “Statistics”): if you also allow “Marketing”, we switch on Google signals, personalised advertising and the collection of data you provide yourself in Google Analytics. Google then links your visits with the information about your Google account if you are signed in and have allowed personalised ads in your Google account. This information can include your location, your history in Google Search and on YouTube and data from websites of Google partners. This creates cross-device reports and information about age, gender and interests, and audiences from our visitor data can be used for personalised advertising through Google. In addition, Google Analytics can automatically detect email addresses and phone numbers you type into forms on our pages (for example the newsletter or contact form) and send them to Google as a hash to match visits. Without your consent to “Marketing” all of this is off: Google signals, personalised advertising and sending such data are then explicitly forbidden in the Google tag.

Google itself is responsible for the data from your Google account and for personalised advertising. You can see and delete what Google has stored about you at myactivity.google.com (“My Activity”), and turn off personalised ads at myadcenter.google.com. The legal basis is your consent (§ 25 Abs. 1 TDDDG, Art. 6(1)(a) GDPR), which you can withdraw at any time via “Cookie settings” in the footer. For the transfer to the USA, what is said above about statistics applies.

We do not use external media on any of our pages. If we were to introduce anything of that kind, we would first ask for your consent in a separate category.

05Bot protection with Cloudflare Turnstile

To protect against spam we use Cloudflare Turnstile (Cloudflare, Inc., USA) on the contact page. Turnstile uses technical data from your browser and your IP address to check whether a human is submitting the form; for this, a connection to Cloudflare is established when you open the contact page. The same check runs on ideas.synapselabs.studio and bugs.synapselabs.studio before a new idea, a new bug report, a comment, a vote or a report is sent; there we establish the connection to Cloudflare only when you start one of these actions, and our server sends the result of the check together with your IP address to Cloudflare for confirmation. We store none of this. The legal basis is our legitimate interest in a contact form and in contributions on these sites free from abuse (Art. 6(1)(f) GDPR). Cloudflare is certified under the EU-US Data Privacy Framework. We also limit the number of messages per IP address; the address is only held briefly in working memory for this purpose.

06Security and backups

Security and backups: We store access keys, secrets, contact details from reports and contracts, and the contract documents encrypted (AES-256-GCM), access keys for the owner API, sessions and the one-time keys from account emails only as irreversible check values, and passwords only as hash values. Once a day we back up the databases of the account and of our projects (Axon, glia, lust.bio, Support, Ideas and Bugs, status page, the website’s mail lists) as well as our internal team database and the mailboxes of our mail server. The backups are encrypted on our server with a key that only we have and then stored at Cloudflare R2 (Cloudflare, Inc., storage location Western Europe); Cloudflare cannot read the content. For Cloudflare, what is said in section 3 applies. We delete backups after 30 days, so deleted data stays in them for up to 30 days. If we restore a backup, we delete again everything that was deleted after it was made before the service goes live: for this we keep a deletion list that contains only identifiers and the time of the deletion (see “Data export and deletion”, section 10). After a restore we first delete again every account that had been deleted in the meantime before the service serves users again. Axon also asks the account every day about all its members and deletes those it no longer knows. The legal basis is Art. 6(1)(f) GDPR in conjunction with Art. 32 GDPR.

07Synapse Labs account

At acc.synapselabs.studio you manage your Synapse Labs account, which is currently used by Axon, glia, lust.bio, Synapse Support and Synapse Ideas and Bugs (for glia see section 12, for lust.bio section 13, for support section 15, for Ideas and Bugs section 16); for AlphaCloud the account has its own tab (below, “AlphaCloud in the account”, section 9). The controller named in section 1 is responsible. Both run on our own server at Hetzner in Germany, in two separate databases on that server, one for the account and one for Axon. The legal basis is Art. 6(1)(b) GDPR. The pages are delivered via Cloudflare as described in section 3; what is said there applies to the server log files.

Account: You create your account at acc.synapselabs.studio with an email address, password and display name. We store the email address encrypted (AES-256-GCM) and additionally as an irreversible check value (HMAC), so that we can find your account at sign-in and each address is only used once. We store the password only as a hash value (scrypt with a random salt), so we do not know it. At registration we also store when you accepted the terms of use of Synapse Labs and confirmed your minimum age, and which version applied. You only agree to the terms and policies of Axon on Axon itself, before your first action there (for example a vote); for this, Axon stores the version and the time of your agreement for as long as you use Axon. After that we send you an email with a confirmation link; an account that is not confirmed within 7 days is deleted with all its data. The legal basis is performance of the user contract (Art. 6(1)(b) GDPR). We store the data until you delete your account. If you do not use your account for 24 months (no sign in and no use in our projects) and nothing paid or open hangs on it (for example a running Synapse+ subscription, an open cancellation or withdrawal, or an NDA of work that has not ended), we write to your confirmed email address and delete the account 30 days later, like a deletion by you, unless you sign in until then. For this we store when you last used your account (updated at most every 10 minutes) and whether and when we warned you; both are in your data export. We do not delete an account without a confirmed email address this way. The legal basis for this is Art. 6(1)(f) GDPR (data minimisation, Art. 5(1)(e) GDPR).

Account emails: We send the confirmation of your email address, links for resetting the password, and notices after a change of password, email address, second factor or passkeys and after linking or unlinking a login (for a new address, the notice goes to the old one) from noreply@synapselabs.studio via our own mail server at Hetzner. The links in them contain a random one-time key, of which we store only an irreversible check value. It is valid for 24 hours (confirmation) or one hour (password reset) and is deleted at the latest one day after use or expiry. The legal basis is Art. 6(1)(b) GDPR, and for the notices after changes additionally our legitimate interest in the security of your account (Art. 6(1)(f) GDPR).

Linked logins: You can voluntarily link Discord, Roblox, Google and GitHub to your account and then also sign in through them; a new account cannot be created through them. Before you link a login, we ask for your password. After that, a random one-time key is valid for 10 minutes only for your account and that provider; of it we store only an irreversible check value. After linking and after unlinking a login we send you a notice by email (see “Account emails”). From Discord, with the permissions “identify” and “guilds”, we receive your Discord ID, your username, display name and profile picture, as well as the list of your servers with your rights there; we use the server list only to check whether you own a server you want to list, for selecting the server for AlphaCloud Premium, and for selecting the affected server in support (section 15). With the same confirmation at Discord you also add our Discord app “Synapse Labs” to your Discord account (permission “applications.commands”). This allows the app to send you direct messages; it only does so if you expressly switch this on in support or at Synapse Ideas and Synapse Bugs. We store which permissions Discord confirmed. You can remove the app again at any time in Discord under Settings, Authorized Apps. If you unlink a login, reset your password by email or delete your account, we also revoke the access at Discord, Roblox and Google and delete the stored keys; a key the provider no longer accepts is deleted at once. From Roblox, with “openid” and “profile”, we receive your Roblox ID, your name, display name and profile picture. From Google (Google Ireland Limited, Ireland), with “openid”, “email” and “profile”, we receive your Google account ID, your email address at Google, your name and your profile picture; we show the address only to you in the account, so that you can see which Google account is linked. When signing in via Google you enter your credentials directly at Google, where Google’s privacy policy applies; Google may transfer data to the USA in the process (Google LLC is certified under the EU-US Data Privacy Framework, Art. 45 GDPR). From GitHub (GitHub, Inc., USA), without any further permission, we receive only your public profile: GitHub ID, username, name and profile picture, no email address and no access to repositories; GitHub is likewise certified under the EU-US Data Privacy Framework (Art. 45 GDPR), and at sign-in GitHub’s privacy policy applies. We do not store the access key from GitHub; those from Discord, Roblox and Google we store encrypted. The legal basis is performance of the user contract (Art. 6(1)(b) GDPR), because you link the login yourself. We delete a link when you unlink it or delete your account.

Account ID: Every Synapse Labs account receives a random account ID (for example SL-7K3Q-9XMP). It reveals nothing about you, does not count upwards, and serves to identify your account unambiguously, for example when you write to support or no email address is stored. You see it at acc.synapselabs.studio, our team sees it in the internal hub. It is deleted with the account. The legal basis is Art. 6(1)(b) GDPR.

Profile picture and name: You can voluntarily upload a profile picture and change your display name at acc.synapselabs.studio. Your browser crops the picture to a square and scales it down to 256 pixels before it reaches us; embedded information such as location or camera is removed in the process. We store only this scaled-down picture in our database at Hetzner in Germany and show it to you, when you are signed in, in the account and on Axon. On Axon we show it to others next to your public reviews and on the owner card of a listing. We delete the picture when you remove or replace it or delete your account. The legal basis is Art. 6(1)(b) GDPR.

Sessions: For each sign-in we store when it started, when it was last used, what you signed in with (for example password and authenticator app) and a rough device description from browser and operating system (for example “Firefox on Windows”), so that you can see and sign out your signed-in devices at acc.synapselabs.studio, Security. We do not store IP addresses for this. Each session has two random keys, of which we store only irreversible check values: one for signing in to our projects (“sl_session”, handed over for lust.bio, section 13) and one that applies only to the account itself (“__Host-sl_acc”, see “Cookies and local storage”). A session ends 60 days after you signed in, then you sign in again; we delete it when you sign out or when it ends. If you reset your password via the link by email, we end all sessions and remove your passkeys, the authenticator app with its recovery codes and all linked logins, because the link only shows that you have access to the mailbox; we record what was removed in the security log (see “Two-factor and passkeys”) and name it in the email about the password change. The legal basis is Art. 6(1)(b) and (f) GDPR (security of your account).

Two-factor and passkeys: You can voluntarily protect your account with an authenticator app or with passkeys. For the authenticator app we store secret key material encrypted (AES-256-GCM), the date of setup and the most recently used time step, so that a code cannot be valid twice. The QR code is generated on our server; no third-party service is involved. Of recovery codes we store only irreversible check values (HMAC) and when they were used. For a passkey we store the passkey’s identifier, its public key, a counter, the transport methods (for example USB or internal), whether it is synced, the name you gave it, and when it was created and last used. We never receive the private key, your fingerprint, your face or your device PIN: they stay on your device or with your password manager, where the device itself verifies you. We therefore do not process biometric data. During a sign-in with a second factor and when setting up or using a passkey, we set technically necessary cookies (“__Host-sl_mfa”, “__Host-sl_wa”) for at most 5 minutes with a random one-time key, of which we store only a check value; the intermediate step for a passkey (challenge) is deleted after 5 minutes. Changes to the security of your account (second factor on or off, passkey added or removed, recovery code used or newly generated, reset by our team) we log with type and time, so that you and we can detect abuse. We keep this log for 12 months; it is part of your data export. If you no longer have access to your factors, an owner of our team can reset the second factor after we have verified that the account belongs to you; in doing so we record in the same log who did it, when and with what justification, and we inform you by email. The legal basis is Art. 6(1)(b) GDPR and our legitimate interest in the security of accounts (Art. 6(1)(f), Art. 32 GDPR). We store the remaining data until you remove the factor or delete your account; the log is deleted with the account as well.

Projects in the account: At acc.synapselabs.studio, Projects, we show you for each Synapse Labs project whether your account can be used there, and in the case of a ban its duration and reasons, together with the decisions and reports of that project. For this we collect no further data; we only assign the data named above to its project. If your name, your profile picture or your logins change, we tell the projects that use your account through a queue; we delete its entries 30 days after delivery. If you delete your account, we delete the changes of your name, picture and logins that were not delivered yet at once; the message about the deletion itself stays until every project has confirmed it and is deleted 30 days after that. AlphaCloud has its own tab there (see “AlphaCloud in the account”, section 9).

Notifications in the account: At acc.synapselabs.studio, Notifications, you decide per service (Synapse Support, Synapse Ideas, Synapse Bugs) whether you get emails and Discord direct messages, and for Synapse Ideas also for which kinds (team answers and status changes, replies to your comments, new comments on your ideas). For this we store your choice per account and service and the time of the last change; without a stored choice the defaults apply (email on, direct message off, new comments on your ideas off). The services ask the account before they send you an email or direct message: the account sends an email only if you have not switched it off, and releases your Discord ID for a direct message only if you have switched direct messages on for that service. The service learns only whether a notice was delivered or switched off. Confirmations and closing notices (that a request, an idea or a report has arrived and how it ended) and bans in support are part of the service and always arrive by email, even if you switched emails off for the service; direct messages for them follow your setting. The legal basis is performance of the contract for using the services (Art. 6(1)(b) GDPR), for direct messages your consent (Art. 6(1)(a) GDPR), which you withdraw by switching them off. We delete your choice with your account; it is part of the data export.

Cookies and local storage: Axon and the account area ask you in the cookie banner like this website (section 4, the same two categories, withdrawal via “Cookie settings” in the footer of the respective page). The account area shares your choice with the other Synapse Labs sites (cookie “sl-consent”, section 4); Axon has its own banner and its choice only applies on Axon. The following are necessary: “sl_session” keeps you signed in to our projects and applies to axon.synapselabs.studio, acc.synapselabs.studio, glia.synapselabs.studio, support.synapselabs.studio, ideas.synapselabs.studio and bugs.synapselabs.studio (domain synapselabs.studio, 60 days from signing in; on lust.bio “sl_session” applies to lust.bio only instead, see section 13); “__Host-sl_acc” keeps you signed in to the account itself and applies only to acc.synapselabs.studio (60 days, ends with the same session); “sl_pass” is received only by our team for the preview before launch (12 hours, with an irreversible check value of the IP address so that the access cannot be passed on); “ax_team_login” protects the team sign-in process on Axon (10 minutes); on acc.synapselabs.studio “__Host-ax_oauth” secures sign-in via Discord, Roblox, Google or GitHub (10 minutes), “__Host-sl_mfa” holds the intermediate step of a sign-in with a second factor (5 minutes) and “__Host-sl_wa” the check value when signing in or setting up a passkey (5 minutes); “__Host-sl_handoff” remembers the project and the state value for the way back (10 minutes) if you first have to sign in on the way from lust.bio; “__Host-sl_ndapass” opens, for someone invited to the team NDA, only the pages for signing, signing in and linking (24 hours, with an irreversible check value of the IP address); the prefix “__Host-” means that only acc.synapselabs.studio itself can set these cookies and no other site under synapselabs.studio; plus “sl-consent” with your choice (on acc.synapselabs.studio the shared cookie from section 4, on Axon an entry in Local Storage that only applies to Axon) and Cloudflare Turnstile as bot protection when voting on Axon, on acc when registering and signing in and for a cancellation or withdrawal without signing in, and on ideas.synapselabs.studio and bugs.synapselabs.studio when submitting ideas, bug reports, comments, votes and reports. Under “Preferences”, only with your consent: “ax-theme” (your colour scheme, on Axon and acc), and on Axon also “axon-proto-v2” (your language in the app, whether you see the list or tiles, and your recent searches) and “ax-terms-notice-…” (that you have closed a notice about changed terms). This data stays on your device. The legal basis for necessary items is § 25 Abs. 2 Nr. 2 TDDDG, for “Preferences” your consent under § 25 Abs. 1 TDDDG and Art. 6(1)(a) GDPR, and for the processing otherwise Art. 6(1)(b) and (f) GDPR. We do not set advertising or analytics cookies.

Team NDA: Anyone who works in the team of one of our projects signs the confidentiality agreement in the account at acc.synapselabs.studio. What we process for it is described in section 20.

08Synapse+, payments and contracts

Synapse+ and contracts: As soon as the Synapse+ subscription can be booked, the payment service Stripe (Stripe Payments Europe, Ltd., Ireland) handles the payment. You enter your payment details directly at Stripe. For payment processing Stripe processes the data on our behalf; a data processing agreement under Art. 28 GDPR is in place with Stripe as part of Stripe's terms of service. For its own purposes, such as fraud prevention and legal obligations, Stripe is itself the controller (stripe.com/privacy). We delete your customer object at Stripe (name, address, stored payment methods) 18 months after the end of your last contract, 3 years after a dispute about a payment; while a subscription runs it stays. Stripe also keeps its own records under its own rules, which we cannot shorten. Where data goes to Stripe, Inc. in the USA, this is based on the EU-US Data Privacy Framework or the standard contractual clauses of the European Commission. We ourselves pass Stripe the confirmed email address of your account and an internal identifier of your account, so that invoices and receipts reach you and the payment is assigned to your account; the address is therefore preset at checkout. You enter your name and your billing address there as required details for the invoice. You can change your name and billing address yourself at acc.synapselabs.studio, Synapse+; the page loads them only when you reveal them, reads them from Stripe for this and writes changes back there, they are stored only at Stripe and in the invoice documents. You change your payment method there on a page of Stripe; you enter the new payment details there directly at Stripe, we neither receive nor store them. From Stripe we receive your name, your email address, your country, the payment status and the invoice data. Because we only sell Synapse+ to certain countries (Synapse Labs Terms of Use, section 10 paragraph 14), before every purchase we check the country you state as your residence and the country of your connection, which Cloudflare derives from your IP address. We do not store the country of the connection; the stated country goes to Stripe with the purchase. After the payment we compare the country of your payment method (card or account, from your bank through Stripe) and the country of your billing address with the list. If we refuse a purchase for this reason, we store for 12 months (24 months at the latest) your account, the stated and the checked countries, plan and amount, the identifiers of the subscription and the payment at Stripe and, encrypted, the email address we inform you at. The legal bases are our legal obligation to determine the place of supply for VAT (Art. 6(1)(c) GDPR, Art. 24b of Implementing Regulation (EU) No 282/2011) and the performance of the contract (Art. 6(1)(b) GDPR). For this we store your subscription (plan, term, status) and your email address encrypted. When you conclude a contract, we store your confirmations (terms and immediate start) with version, language and time as evidence. We delete these confirmations three years after the end of the year in which your contract ends, because claims from a withdrawal can rely on them until then (§§ 195, 199 BGB); those of a checkout that did not lead to a purchase after 30 days. If you delete your account we separate them from it but keep the link to your contract so that the period is right. We send contract confirmations, cancellation and withdrawal confirmations and notices about your subscription from billing@synapselabs.studio via our own mail server at Hetzner in Germany. We create invoices, invoice corrections, contract confirmations, withdrawal confirmations, confirmations of the end of the contract and notices about your subscription (for example about the switch of the yearly plan, a change of plan, a price change or a failed payment) as PDFs on our own server and send them to you as attachments to these emails. They show your name, your email address, your billing address, your account ID as customer number, the contract number, plan, period, amount and payment method. We store each file together with its data encrypted (AES-256-GCM), exactly as we sent it; you can download your invoices and invoice corrections at acc.synapselabs.studio, Synapse+. The legal basis is performance of the contract (Art. 6(1)(b) GDPR) and our statutory obligation to confirm (§§ 312f, 312k, 356a BGB; Art. 6(1)(c) GDPR). We keep invoices, invoice corrections and accounting records for 8 years (§ 147 AO, § 14b UStG), contract confirmations and other business correspondence for 6 years (§ 147 AO), in each case from the end of the calendar year (Art. 6(1)(c) GDPR). When the period ends, our server deletes them automatically. Your subscription itself (plan, term, status, amount) stays linked to your account, your email address and its identifiers at Stripe until its invoices no longer have to be kept either (8 years from the end of the calendar year in which it ended); then we remove this information, and only figures without any link to you remain. We delete unfinished checkouts, documents of our team's test subscriptions and of test purchases without a real payment after 90 days. If you delete your account, the link to the account goes at once; the email address stays only for the invoices, and these documents remain stored until their period ends. If you change your plan or agree to or decline a price change (at acc.synapselabs.studio, Synapse+, or via the link in the email, which works without signing in), we store as evidence what you chose, the plan and prices, from when it applies, the time and whether the answer came from the account or via the link. We delete this information three years after the end of the year in which your subscription ends, because until then claims under the contract may rely on it (§§ 195, 199 BGB; Art. 6(1)(b) and (f) GDPR). Until launch, Synapse+ only runs in test mode without payment.

One Stripe account for all projects: payments for all our projects run through the same Stripe account of Synapse Labs, including purchases of AlphaCloud Premium. A payment therefore starts with “SYNAPSE” on your bank statement, for example “SYNAPSE PLUS” for Synapse+ or “SYNAPSE* ALPHACLOUD” for AlphaCloud. Each project marks what it creates at Stripe (customer, checkout, subscription and payment) with its project and only processes payment events of its own project; its server discards events of other projects without storing their content. A Synapse+ subscription and a purchase at AlphaCloud are therefore not linked, even if you use the same email address. How AlphaCloud processes its purchases is set out in the AlphaCloud privacy policy (alphacloud.bot/privacy). The legal basis is the performance of the respective contract (Art. 6(1)(b) GDPR).

Cancelling and withdrawing: Via “Cancel contracts here” (acc.synapselabs.studio/kuendigen, also without signing in) and “Withdraw from contract” (acc.synapselabs.studio/widerrufen) we ask for the information required by law: type of cancellation, name, email address, details of the contract, desired date and, for an extraordinary cancellation, the reason. We store name, email address, contract details and reason encrypted, and the email address additionally as an irreversible check value to find your contract. We use the information to carry out the declaration and to confirm receipt to you with date and time. If you withdraw from your own subscription while signed in and within the 14 days, we end and refund it automatically at once; if you already withdrew automatically in the 90 days before, a person decides on the refund instead. For this we compare with your earlier withdrawals (account and check value of the email address) to prevent abuse (Art. 6(1)(f) GDPR). If you send a form without signing in, Cloudflare Turnstile may first check whether a human is acting (see “Protection against abuse”, section 11); if the check does not load, you can also send your declaration by email to support@synapselabs.studio. The legal basis is Art. 6(1)(c) GDPR in conjunction with §§ 312k and 356a BGB. As received business correspondence, we keep the declarations for 6 years from the end of the calendar year (§ 147 Abs. 1 Nr. 2 and Abs. 3 AO); we delete the free text in them (reason and note) already 3 years after the end of the calendar year, because it is no longer needed to settle a dispute about a deadline (§§ 195, 199 BGB). If you delete your account we remove the link to it, name and email address stay in the letter until the 6 years end.

Invite friends: If you take part in the “Invite friends” programme (Synapse Labs terms of use, section 12), we store your personal invite code. If someone creates an account through your link, we store that this account came through your link and when, whether it got a gift and when it redeemed it, whether a purchase was counted and with which subscription or why not (for example withdrawn, refunded or the same person), as well as your rewards and gift codes (when created, valid until when, whether and by which account redeemed) and the gifted Synapse+ time (start, end and origin). Of the gift code itself we only store an irreversible check value. So that everyone gets the gift only once and nobody invites themselves, we compare the linked logins of the accounts involved; for this we store irreversible check values (HMAC) formed with a secret key of the logins of the inviting account and of the Discord accounts with which a gift was redeemed, never the IDs themselves. We read the age of a Discord account from its ID. To check whether a friend pays with the same payment method as you, we ask Stripe for the check values (fingerprints) of the payment methods stored for both subscriptions and compare them without storing them. Who sees what: You only see numbers (how many accounts were created through your link and how many purchases count), never who signed up or bought something. Anyone who comes through a link learns nothing about the inviting account from us, not in the data export either. We do not send invitation emails. We inform you about a reward by email to your confirmed address via our own mail server. The legal basis is the performance of the conditions of participation (Art. 6(1)(b) GDPR); the comparison of logins and payment methods is based on our legitimate interest in protecting the programme against misuse (Art. 6(1)(f) GDPR). We delete invitations that did not count 90 days after the decision, counted purchases and rewards 3 years after the reward, gift codes 3 years after they were redeemed or expired and the check values of Discord accounts that redeemed a gift 3 years after the redemption, because claims can rely on them until then (§§ 195, 199 BGB). If you delete your account, we delete your invite code, the check values of your logins and your gifted Synapse+ time right away; invitations and rewards stay stored without a connection to your account until the end of their period.

09AlphaCloud and the account

AlphaCloud Premium with Synapse+: If you choose a Discord server for AlphaCloud Premium with Synapse+ in the AlphaCloud tab, we read the list of your servers with your Discord sign-in and ask AlphaCloud on which of them the AlphaCloud bot is present. For the chosen server we transmit to AlphaCloud the ID of the server, your Discord ID, the end of the Premium period and an internal identifier of your account, by which AlphaCloud assigns the Premium to your subscription. On our side we store the ID and the name of the chosen server and until when the Premium runs, until it ends or you delete your account. The requests run over a private connection between our servers. We operate AlphaCloud ourselves as the same controller; the privacy policy of AlphaCloud applies there (alphacloud.bot/datenschutz). The legal basis is performance of the contract (Art. 6(1)(b) GDPR).

AlphaCloud in the account: At acc.synapselabs.studio, Projects, AlphaCloud, you see and change your AlphaCloud settings. AlphaCloud knows you by your Discord ID. The account therefore asks AlphaCloud only with the Discord ID of your linked Discord login (linking requires your password and signing in at Discord), never with your account ID, your name or your email address. AlphaCloud answers with the settings for this Discord ID: your name and profile picture from Discord, since when you have used AlphaCloud, whether a ban exists, your servers with their Premium (term and where it comes from), your Premium subscriptions and withdrawals, whether you have subscribed to the AlphaCloud newsletter, whether your Discord account uses two-factor authentication, and your referral program (code, points, redeemed servers). There you can subscribe to or unsubscribe from the newsletter, create a referral code, redeem points for Premium on a server, have your AlphaCloud data sent as a file to your confirmed email address and delete your AlphaCloud data; to delete, we ask for your password, and your Synapse Labs account remains. AlphaCloud never hands out email addresses, payment details, access keys or IP addresses in the process, not even in the data export. The account does not store this information, it only displays it; the requests run over a private connection between our servers. If you open the tab from the AlphaCloud panel, the link contains your Discord ID there; we only compare it with your linked Discord login to warn you if they are two different Discord accounts. You do not need a Synapse Labs account for AlphaCloud: all settings, including data export and deletion, are also available in the AlphaCloud panel with your Discord login. For the data at AlphaCloud, its privacy policy applies (alphacloud.bot/privacy). The legal basis is Art. 6(1)(b) GDPR.

10Data export and deletion of the account

Data export and deletion: At acc.synapselabs.studio, Data, you can at any time have a copy of all data about your account sent to your confirmed email address: a PDF for reading with the information of Art. 15(1) GDPR (purposes, legal bases, recipients, storage periods, sources) and every stored value, plus the same data as a JSON file (Art. 15 and 20 GDPR; an account without a confirmed address downloads the JSON file directly), and delete your account. We only send the copy to the account's address, so that nobody who gets hold of someone else's sign in can simply take the data; we do not store the email. Our server handles the requests one after the other in the background, usually within a minute, and asks the projects and AlphaCloud for it; for this we store when you made the request, which part it covers and whether it was sent, and delete these details after 30 days. To delete, we ask for your password. In doing so we immediately delete your listings, votes, reviews, sessions, your email address, your password and your linked logins (we revoke the access at Discord, Roblox and Google there). Data that we must retain under the periods stated above (invoices and contract documents of Synapse+, the records of the purchase such as consents at checkout and plan and price changes, cancellations and withdrawals, purchases refused for their country, the records of “Invite friends” and an effective NDA) is separated from your account, kept only until its period expires and then deleted. Decisions about your account and your content on Axon are deleted with the account. After the deletion we send you an email with the list of what is deleted and what stays until when; the delete window shows the same list. Deleted data stays in our backups for up to 30 days and is used for nothing else. So that restoring a backup does not bring you back, we store only your account ID and the time of the deletion (no name, no address) for 3 years and 30 days in a deletion list and delete your account again after every restore before the service starts. A server you chose for AlphaCloud Premium with Synapse+ loses this Premium; if we cannot reach AlphaCloud at once we keep trying for up to 30 days. Your AlphaCloud data belongs to your Discord ID and remains; you delete it in the AlphaCloud tab (see “AlphaCloud in the account”, section 9).

11Axon

At axon.synapselabs.studio we operate Axon, a platform for discovering, voting on and reviewing Discord bots, Discord servers, Roblox games and groups, and FiveM, Minecraft and Steam servers. From the account, Axon receives over an internal connection only what it needs for use: your display name, your profile picture, your account ID, your language, the end of a Synapse+ subscription, the names of your linked logins, and check values (hashes) of your logins and of your email address, so that a ban on Axon cannot be circumvented with a new account. Axon never receives your password, your email address or the access keys of Discord, Roblox, Google and GitHub; the account queries your Discord server list when needed and gives Axon only the result. The rules of use are set out in the terms and policies of Axon (axon.synapselabs.studio/de/agb and /de/richtlinien).

Listings and reviews: What owners write in a listing (also separately in German and English) and what users review is publicly visible, for reviews together with the name and profile picture of the account and, if available, the number of its votes for the listing. If you edit a review, we store the previous version (stars, text, date); it remains publicly visible under “Previous versions”, so that it is traceable how a review has changed. We delete the previous versions together with the review, that is, when you delete your account or we remove the review. A review we removed stays stored, not public, for 12 more months for a possible objection and is then deleted. If someone reports a review, we store with the report the version that was reported. If you delete your account, we delete that copy. If you mark a review as helpful, we store your account and the review so that you can mark it only once; only the number is publicly visible. We delete the mark together with the review or when you delete your account. Ownership codes for listings (FiveM, Minecraft, Steam, bots) are valid for 24 hours and are deleted 8 days after they expire at the latest, otherwise with the listing or your account. Owners can embed images via an address; your browser loads these images directly from the server on which they are hosted. That server learns your IP address in the process; we have no influence on this. Live figures such as members or players online we query ourselves from Discord, Roblox, Cfx.re (FiveM) and from the listed Minecraft and Steam servers; no data about you is transmitted in the process. Logos and banners of listed Discord bots, Discord servers, Roblox games and Roblox groups are fetched by our server from Discord or Roblox and stored at Axon; visitors load them from Axon and load nothing from Discord or Roblox for this. We refresh them at most once a day and delete them with the listing. Owners can also upload their own banner and an image for the page background for their listing: we check the file, convert it to WebP and remove metadata such as camera or location information, store the image on our server and show it publicly on the listing page and in the link preview. An image that was uploaded when creating a listing but not submitted is deleted by us after 24 hours; otherwise it remains until the owner removes it, deletes the listing or we remove it after a report. The legal basis is performance of the user contract (Art. 6(1)(b) GDPR). If an owner sets a listing to private, we show it to nobody except them; the data of the listing remains stored.

Companies: On Axon you can create up to three companies (for example a studio or team) and assign your listings to one of them. For this we store the name, the short description, the text, the website, the logo, your account as owner and the review status. Once a company is approved, this information is publicly visible on its page, but not which account created it. We check and store the logo in the same way as own images for listings. We delete everything when you delete the company or your account. Listings and companies we rejected or removed and that nobody changed since, we delete 12 months after the decision, unless an objection is running. The legal basis is Art. 6(1)(b) GDPR.

Automated checks: Our server checks new and changed listings and companies with fixed rules, without artificial intelligence, for signs of fraud, suspicious links, certain words, contact details and duplicate names; for bots, we query the bot’s public information at Discord for this (no data about you is transmitted in the process). We store the result with the listing or company; only our team sees it during review. In the case of a serious indication on a public listing, the check creates a report without a reporting person, on which a human decides; the periods applying to reports apply to it. The check does not make a decision within the meaning of Art. 22 GDPR. The legal basis is our legitimate interest in protecting Axon from fraud and unlawful content (Art. 6(1)(f) GDPR). Where Axon uses AI, this is explained at axon.synapselabs.studio/de/ki-transparenz.

Statistics for owners: Owners see views, visitors, clicks on links and votes per day for their listings. For this, our server counts the view when a listing page is opened and the click when a link of the listing is clicked. To avoid counting visitors twice, the server forms an irreversible check value from a randomly generated value that changes daily, your IP address and the browser identifier. It exists only in working memory, is never stored and is lost at the change of day; the database contains only daily numbers with no link to you. For listings of Synapse+ customers we additionally store only the domain of the page you came from (for example “google.com”), never the full address. We store nothing on your device for this. We delete the daily numbers after 13 months. The legal basis is our legitimate interest in showing owners how their listing is found, without tracking visitors (Art. 6(1)(f) GDPR).

Votes: For each vote we store your account, the listing and the time, so that each account can vote only every 12 hours and the ranking is correct. We delete individual votes after 13 months. If you boost a listing, we store your account, the listing and the time shown and delete this 13 months after the boost ended. Votes we removed as manipulated stay with the decision, so that a successful objection can restore them, and are deleted with it; if you delete your account, we delete them immediately. If the owner has set up a vote webhook, we send them for each vote the listing, the platform, your Axon user ID (not your Discord or Roblox ID), the time and whether it is a weekend, so that they can give you a reward. The owner is responsible for the processing at the owner’s end. We delete deliveries and their log after 14 days, and deliveries carrying your Axon user ID also immediately when you delete your account. What has already reached the owner we cannot take back. The legal basis is performance of the user contract (Art. 6(1)(b) GDPR).

Owner API: Owners of Discord bots can report figures about their bot using their own access key. Of the key we store only an irreversible check value. The secret with which we sign vote webhooks we store encrypted.

Protection against abuse: To prevent spam and manipulation, we count actions such as votes, reviews and reports per account and per IP address; these counters exist only in working memory and expire after one hour at the latest. We count failed sign-ins per IP address in working memory and, for an existing account, on the account itself (number, start, locked until) until you next sign in successfully; for addresses without an account only as a check value in working memory. After too many failed attempts you have to wait 15 minutes. Only at registration, at sign-in, in the voting dialog, when reviewing, when reporting without an account, when submitting an idea, a bug report, a comment, a vote or a report on ideas.synapselabs.studio and bugs.synapselabs.studio, and for a cancellation or withdrawal without signing in can Cloudflare Turnstile check whether a human is acting; we load the Cloudflare script only when you open one of these pages or dialogs or start one of these actions, and what is said in section 5 applies. If we suspend an account on Axon, we keep check values (hashes) of the e-mail address and the linked Discord, Roblox and Google IDs for the duration of the suspension, so that it cannot be bypassed with a new account. We review every suspension that lasts longer than a year once a year and confirm it only with a written reason. Without a confirmation it ends three years after it began at the latest. When it ends or is lifted, including through a successful appeal, we delete the check values immediately. The legal basis is our legitimate interest in a fair and safe platform (Art. 6(1)(f) GDPR).

Reports and moderation: Anyone can report content. Without an account we ask for your name, your email address and a reason, and store name and email address encrypted; with an account we link the report to your account. We use the information to review the report, to tell you the decision (at acc.synapselabs.studio, Notices, or by email from legal@synapselabs.studio via our own mail server) and to be able to handle an objection. We pass the name of the reporting person on to the owner only if this is absolutely necessary for the decision. Anyone affected by a measure (including the removal of manipulated votes) receives the reasons under Notices. The legal basis is our obligations under the Digital Services Act (Art. 16, 17 DSA; Art. 6(1)(c) GDPR) and our legitimate interest in a lawful platform (Art. 6(1)(f) GDPR). We delete reports, decisions and appeals 12 months after the decision. We delete the name and e-mail address of a person who reports without an account 90 days after the decision, and likewise for a report that is still undecided after 12 months. Reports you sent with your account stay without any link to you until that period after an account deletion; if someone reported a review of yours, we delete the copy of its text together with your account. We delete all measures that concern you together with your account. We never refuse the deletion of content on the ground of a legitimate interest, particularly not for content you posted as a child or teenager. If a reported listing or company is deleted, we delete the reports about it with it. In the case of indications of a criminal offence that threatens the life or safety of people, we inform the police (Art. 18 DSA).

12glia

At glia.synapselabs.studio we operate glia, a service with which you create a public status page for your project. The status pages are located at glia-status.synapselabs.studio. The controller named in section 1 is responsible. glia runs on our own server at Hetzner in Germany, with its own database on that server. You sign in with your Synapse Labs account (section 7). From the account, glia receives over an internal connection only your display name, your profile picture, your account ID, your language, the time at which you created your account, and the end of a Synapse+ subscription. glia also stores when you last used glia. glia uses the end of Synapse+ only for the limits of your status pages (number of pages, services and team members, glia terms section 2). glia never receives your password, your email address or the access keys of your linked logins. If, as owner, you want to delete or transfer a status page, the account sends a six-digit confirmation code to your confirmed email address; glia generates the code, stores only an irreversible check value of it for 10 minutes and does not learn your address in the process. The legal basis is Art. 6(1)(b) GDPR. The pages are delivered via Cloudflare as described in section 3; what is said there applies to the server log files. The rules of use are set out in the terms of glia (glia.synapselabs.studio/de/agb).

Status pages and teams: For each status page we store its name, its address, its description, the listed services with their state, incidents and maintenance with all steps and times, as well as the owner and the team with its roles. Name, description, services, incidents and maintenance are publicly visible. Who is on the team and who wrote a report is not public; the members of a team see each other’s names, profile pictures and roles. We store invitation links only as an irreversible check value (SHA-256), together with the role, the person who created them, the expiry after 7 days and whether and by whom they were accepted. When you create a status page or accept an invitation, we store which version of the glia terms you agreed to and when, until you delete your account. We delete accepted, revoked and expired invitations after 30 days. What happens on a status page (for example new incidents, monitors or who joined the team) we show the team in a feed with the name of the person who caused it; we delete these entries after 400 days. The legal basis is Art. 6(1)(b) GDPR.

Monitors and notifications: If a team sets up a monitor, our server calls the specified address at fixed intervals (HTTP or TCP) and stores the time, result, response time and, where applicable, an error code; we delete individual checks after 30 days, and the daily values for uptime and bars after 400 days. If a team removes a service, we delete its address, keyword and single checks at once; only its name stays in the history. With a heartbeat, the team’s service calls a secret address at ours; in doing so we see, as with every request, the IP address of the calling server (section 3), and we store only the time of the last call. If a team stores a webhook address, we store it encrypted (AES-256-GCM) and send to it the name of the status page, the names of the services, their state and incident reports; for the processing at the provider of the webhook, for example Discord or Slack, the team that set it up is responsible. The legal basis is Art. 6(1)(b) GDPR.

Dependencies: If a team lists providers as dependencies, our server retrieves their public status page (for example that of Cloudflare or Discord) every 3 minutes and displays the state. No visitor data is transmitted in the process.

Visitors to status pages: The status pages at glia-status.synapselabs.studio set no cookies, store nothing on your device and load no content from third parties. The team is responsible for the content of a status page, and we are responsible for its operation. The logo and custom CSS of a status page are located on our server; glia removes references to external servers from the CSS so that nothing is loaded from third parties when the page is opened. The team of a status page can embed its state on their own websites as a badge (image), as a widget (small card in an iframe) or as a file in JSON format. These also set no cookies and load no script. If you open an external website that embeds such an element, your browser retrieves it from our server; in doing so we receive, as with every request, the information from section 3 (including the IP address and, depending on the browser, the address of the embedding page) and treat it as described there. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is the delivery and protection of the status pages.

Subscribing to status pages: If a team offers this, you can subscribe to the updates of a status page by email, Discord webhook or RSS. We store your email address or webhook address encrypted (AES-256-GCM) together with a check value (SHA-256) against duplicate entries, your selection of services, whether you want to receive maintenance in advance, your language and when you confirmed. We use email addresses only after you have opened and confirmed the link in the confirmation email; we delete unconfirmed entries after 7 days. We send the messages ourselves via our own mail server; the team of the status page sees only the number of subscribers and how many messages were sent, never your address. An email waits in the outbox of our server with an encrypted address only until it is sent and is then deleted at once, an undeliverable one after 7 days. You can unsubscribe in every message with one click; we then delete your address at once. As proof of your consent and its withdrawal, for e-mail subscriptions we keep only a check value of your address (SHA-256, separate per status page), the time you confirmed and the time you unsubscribed, until 31 December of the third year after the unsubscribe (legal basis Art. 6(1)(f) and Art. 7(1) GDPR, legitimate interest: proving consent and defending claims); then we delete it. The proof also stays if the status page is deleted; it then also holds the page’s short name (slug) so it can be assigned to a page. For a webhook we only remember for 31 days that one was removed, with no link to you. Confirmed subscriptions stay until you unsubscribe or the status page is deleted. Counters about messages sent (time, kind, title of the message, number) are deleted after 400 days. Subscribing by e-mail is meant for people aged 16 and over. A webhook to which three messages in a row cannot be delivered is deleted. The legal basis for the subscription is your consent under Art. 6(1)(a) GDPR, which you can withdraw at any time by unsubscribing.

Minors and moderation: We always grant a request by a minor to delete their data at glia. glia shows no ads and builds no profiles. If we restrict a status page because of a breach of the terms or a report, the report, the decision and the statement of reasons are handled through support (section 15); the retention periods of support apply there. glia itself stores nothing about it.

Cookies: glia itself sets only necessary cookies: it reads “sl_session” (section 7) to recognise you, “sl_pass” is received only by our team for the preview before launch (section 7), and “gl_team_login” protects the team sign-in process (10 minutes). In addition there is “sl-consent” with your choice in glia’s own cookie banner (Local Storage, until you change it; glia does not read the shared cookie of the other sites). glia does not store preferences, advertising or analytics on your device; the banner therefore shows the category “Preferences” empty, so that you can see what glia stores, and you can reopen it via “Cookie settings” in the footer. The legal basis is § 25 Abs. 2 Nr. 2 TDDDG, and for the processing otherwise Art. 6(1)(b) GDPR.

Deletion: If the owner deletes a status page, we delete it with all services, incidents, invitations and the team. If you delete your account, we delete the copy of your name and profile picture at glia at once and you leave all teams; status pages you own go to the team member with the Admin role who has been there longest, or are deleted if there is no admin. We replace the titles and texts of incident messages you wrote with the placeholder “[deleted]”, because the team and subscribers built on the message; the message itself, with its times and affected services, stays as part of the page’s history. We remove your name and the titles of your messages from the team’s feed. If a message written by someone else mentions you, you can ask the team or us to remove it. We back up glia's database once a day like the account's, encrypted with a key that only we have, at Cloudflare R2 (location Western Europe, section 6, security and backups); we delete backups after 30 days, so deleted data stays in them for up to 30 days. At acc.synapselabs.studio, Data, you can have all data that glia stores about you sent as a file to your confirmed email address (Art. 15 and 20 GDPR, as described in section 10).

13lust.bio

At lust.bio we operate lust.bio, a service with which you create and design a public page at lust.bio/yourname, with links, music, widgets from other platforms and, if you wish, your Discord live status. The controller named in section 1 is responsible. lust.bio runs on our own server at Hetzner in Germany, with its own database and its own file storage on that server. The pages are delivered through Cloudflare as described in section 3; what is said there applies to the server log files. The addresses www.lust.bio and bio.synapselabs.space forward to lust.bio. You sign in with your Synapse Labs account (section 7). The rules for using it are in the lust.bio terms (lust.bio/terms).

Sign-in: lust.bio has no sign-in of its own. The account’s “sl_session” cookie (domain synapselabs.studio) does not reach lust.bio, so the account hands the sign-in over to it like this: when you click “Sign in” or “Register” on lust.bio, lust.bio forwards you to acc.synapselabs.studio with a random state value; lust.bio remembers the value and the page you want to return to for 10 minutes in the cookie “lust_auth”. If you are signed in to the account (or sign in there), the account creates a random one-time code, of which it stores only an irreversible check value (SHA-256), and sends you back to lust.bio with it. The code is in the address, is valid for 60 seconds and only once, and the redirect passes on no information about the previous page. If you first have to sign in on the account, the account keeps the value for up to 10 minutes in the cookie “__Host-sl_handoff”. lust.bio checks the state value and exchanges the code, over an internal connection to the account, for a session key of its own for lust.bio; this key never opens the account itself. Your browser stores it in the cookie “sl_session”, which applies to lust.bio only (60 days from sign-in). On every request lust.bio asks the account who you are using only an irreversible check value of this key, and remembers the answer for at most 30 seconds in memory. The account lists the session like any other in your list of signed-in devices at acc.synapselabs.studio, Security, labelled “lust.bio” with browser and operating system; you can end it there. Signing out on lust.bio ends only this session; “Sign out everywhere”, resetting your password and deleting the account end it as well. The legal basis is Art. 6(1)(b) GDPR.

Data from the account: over the internal connection lust.bio receives from the account only your account ID, your display name, your profile picture, your language, the time you created your account, the end of a Synapse+ subscription, irreversible check values (SHA-256) of your logins and of your email address, and which logins are linked. In a table of its own it stores: account ID, display name, profile picture, language, end of Synapse+, time of account creation, the check values and the time your account was last used on lust.bio. lust.bio uses the end of Synapse+ only for the limits of your page (lust.bio terms, section 5), and the check values only so that a permanent ban on lust.bio cannot be circumvented with a new account. If you have linked a Discord login to the account, lust.bio asks the account for its Discord ID the first time you sign in, to find a page that already exists and to assign the Discord features below. If your name, profile picture or logins change, the account reports this to lust.bio through a queue (section 7). lust.bio never receives your password, your email address or the access keys of your logins. The legal basis is Art. 6(1)(b) GDPR; for the check values it is our legitimate interest in a fair and safe platform (Art. 6(1)(f) GDPR).

Your page: for your page we store the username, which is also its address, your display name, bio and location (only if you fill them in), profile picture, banner and background, links, music tracks, widgets, badges, your design, your settings and, if you enter one, your own domain. What you show on a public page is publicly visible; this can include badges, active pacts, the number of hearts and your rank on the leaderboard. You can hide bio and location individually, hide the page or take it off the leaderboard. You upload images, videos, music and cursors to us; we store file name, type, size and address and keep the file in the file storage on our own server. Anyone who knows its address can retrieve it. If someone embeds an image or music file from an address elsewhere, the visitor’s browser loads it directly from the server where it is stored; that server then learns the visitor’s IP address, which we cannot influence. The same applies to images in the live status (for example the profile picture, a game icon or the cover of a song), which the visitor’s browser loads from Discord or the respective service. With image hosting unlocked (ShareX) you upload images using a personal access key, of which we store only an irreversible check value (SHA-256); each image gets an address at lust.bio/i/…, and if you enter a webhook we send it every upload. We delete everything when you remove it or delete your account. The legal basis is performance of the contract of use (Art. 6(1)(b) GDPR).

Widgets, lyrics and downloads: if you show widgets from other platforms (for example Twitch, YouTube, GitHub, Steam, Roblox, Last.fm, Instagram, TikTok or X), our server retrieves the public information about the name you entered from the platform concerned and keeps the result for at most 7 days in our database (usually only minutes in memory) so that not every visit to your page triggers a new request. No data about visitors is transmitted to the platform; images from it, for example profile pictures, can be loaded by a visitor’s browser directly from the platform (see above). If your music player plays a track with lyrics, our server asks LRCLIB (lrclib.net) for the lyrics using title and artist and keeps the answer in memory for at most 6 hours; LRCLIB learns nothing about visitors in this case either. With the downloader you can download a video or an audio track from a public address as MP4 or MP3: our server retrieves the address through a filter of its own that allows only public addresses, converts the file and keeps it ready for 24 hours. For this we store the address, format, title, size and status of the job; we delete the file and the entry after 24 hours, jobs without a result (error, cancelled) as well. The legal basis is Art. 6(1)(b) GDPR.

Statistics and leaderboard: when a public page is opened our server counts the view, and when a link is clicked, the click. We do not count your own views or views by search engines and other programs. So that visitors are not counted twice, the server forms an irreversible check value from a secret value, the current day and your IP address, which is different every day; this means nobody can be recognised across several days, and we never store the IP address itself. For a view we also store roughly where you came from (only the domain, for example of a platform, not the full address), the type of device (phone, tablet or computer), browser and operating system as a rough group (for example “Firefox”, “Windows”, not the browser identifier itself) and the country as a two-letter code, which Cloudflare derives from the IP address. The owner of the page sees only numbers from this; the rank on the leaderboard follows from the number of visitors. We store nothing on your device for this. We keep single views and clicks for 400 days with the check value and the details about origin, device, browser, operating system and country; after that we remove all of it and keep only a count per month without any link to a person. The totals stay until the page is deleted; we delete the rank history after 400 days. A heartbeat from the same kind of check value shows the team how many people are currently on the start page, on pages and in the dashboard; its entries only matter for minutes and are deleted after one day at the latest. The legal basis is our legitimate interest in showing owners how their page is used and in running a leaderboard without tracking visitors (Art. 6(1)(f) GDPR).

Hearts, comments, pacts and visits: if you give a page a heart (at most one per page and day, never your own), we store the day, the page and a key for the giver: your account, your Discord ID if you give a heart in Discord, or, for visitors without an account, a check value that changes daily as with the statistics. Only the number is public. We remove the giver key after 90 days; after that a heart is only a number without any link to you. If you delete your account we do this at once for every heart you gave, including those from Discord; the number on the other page stays. You can write comments only with a page of your own; they are publicly visible with your name on the page commented on, its owner can hide or delete them or switch comments off, and we delete them with your account. Pacts (at most three per page) connect two pages; we store the two pages, the status, the streak and the best streak, and active pacts appear on both pages. If you offer someone a pact, our bot sends that person a direct message with the offer, at most one per pair in 6 hours. If the owner of a page switches on the visitor wall, the page shows signed-in visitors of the last 24 hours as small profile pictures; for this, when you visit such a page signed in, we remember your account and the page once a day and delete the entry after 30 days. There are also the duel of the week (we store your Discord ID and your choice, anonymised when you delete your account) and finding secrets on pages (account, page, time, deleted with your account). Pacts, duels and found secrets last as long as the accounts of those involved. Confessions: visitors can leave an anonymous confession on a page, which only appears once the owner approves it. We store the text and a check value that changes every day, against spam. We delete the check value after 2 days and confessions that were not approved after 30 days; approved ones belong to the page and disappear with it. The legal basis is Art. 6(1)(b) GDPR; for the check value for hearts without an account it is our legitimate interest in a fair count (Art. 6(1)(f) GDPR).

Discord bot and server: lust.bio has a Discord app of its own (its own bot) and its own Discord server for the community; this is independent of the account’s Discord app “Synapse Labs”, through which you sign in with Discord. Live status: if you switch it on in your dashboard and are on the lust.bio Discord server, the bot reads your online status for your Discord account and, in “Extended” mode, your activities (for example a game or Spotify with title and album cover) and stores them as long as live status is switched on; if you leave the server we delete them. The page shows them publicly. If you do not switch it on, we store none of it. The legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time by switching it off. Commands and tickets: if you use commands of the bot (for example the daily card “/desire”, pacts or the duel), we store your Discord ID and what belongs to the function, such as the card drawn per day. If you open a ticket, the bot creates a private channel; we store the number, channel, your Discord ID, topic, status, who handled it and, if you give them, the stars and comment of the rating (public in the rating channel). On closing, the bot sends the history as a text file to a channel of the team and deletes the channel. If you create a public page and have a Discord ID on file, the bot announces it once with name, address and profile picture in the channel for new pages, without notifying anyone. We delete daily cards after 12 months, at once when you leave the server and have no account, and with your account. We delete closed tickets (number, topic, status, rating) at the end of the third year after they were closed; when you delete your account we remove your Discord ID and your comment from them. The history of a ticket exists only as the text file in the team’s channel on Discord (see above). On Discord the privacy policy of Discord Inc. (USA) applies. The legal basis is Art. 6(1)(b) GDPR.

Ideas, bugs, applications and invitations: if you submit an idea, a bug report or an application to the team, we store the text with your account. Ideas are public and can be rated; bug reports and applications are seen only by the team. We delete finished or declined ideas and bug reports 12 months later, rejected applications 6 months after the decision. If you delete your account we delete your ideas; if others voted on one, the idea stays only without title, text and name. If you invite someone with your invitation link or redeem a code, we store the connection and the days granted; the invitation code is kept in the cookie “syn_ref” for 30 days until you sign in. During the closed beta we store the Discord ID and the name for the waiting list and delete them after 365 days. When you first create content we store which version of the lust.bio terms you agreed to and when. The legal basis is Art. 6(1)(b) GDPR; for the proof of consent it is our legitimate interest (Art. 6(1)(f) GDPR).

Reports and moderation: anyone can report any page, even without an account; you can report a comment only when signed in. We store the reason from a list, a note, the page or comment reported and the person reporting: your account or, if you report without an account and give them voluntarily, name and email address. We use name and email address only to tell you the decision on your report by email from our own mail server (Art. 16(5) DSA). We do not store your IP address in doing so. If a comment is reported several times, we hide it automatically for the time being until a human from the team has decided; we delete reports of comments (reporting account, short explanation) after 365 days. The team decides in the internal hub of Synapse Labs. Anyone affected by a measure (page or comment removed, suspension) receives the reasons in the dashboard under notices and can appeal once within 6 months, even during a suspension. We keep decisions, reasons and appeals until the end of the third year after the decision (after the decision on an appeal, if there was one), as long as no suspension rests on them and no appeal is open; if you delete your account we remove your name, the target ID and the text of your appeal from them. We delete decided reports after 365 days, reports that were never decided after 18 months, and the name and email address of reporters without an account 90 days after the decision (183 days after the report at the latest). If you delete your account we empty the note and the account IDs of the reports that concern you or come from you at once. We delete the log of team actions (name of the team member, action, target, reason) after 730 days. Suspensions apply only to lust.bio, never to the account. For a permanent suspension we store the check values of your account so that it cannot be circumvented with a new account. We review the suspension every year; unless we confirm it with a written reason we lift it and delete the check values, at the latest at the end of the third year after the suspension or the last confirmation. The check values stay until then even if you delete your account. The legal basis is our obligations under the Digital Services Act (Art. 16, 17 DSA; Art. 6(1)(c) GDPR) and our legitimate interest in a lawful and safe platform (Art. 6(1)(f) GDPR).

Protection against abuse and error log: we count requests per IP address and per account only in memory; the counters expire after 6 hours at the latest. Errors of the server (error text, without intended personal data) are written to an error log for the team and deleted after 14 days. Certain actions (for example changes made by the team) are recorded in a history with the person’s name; when your account is deleted we remove your name, the target and the additional details from it; we delete the history after 730 days, as we do the log of team actions in the hub. We delete the activity log of the team (who carried out which action) at the end of the third year after the entry. The legal basis is our legitimate interest in safe and stable operation (Art. 6(1)(f) GDPR).

Cookies and local storage: lust.bio asks you in the cookie banner like this website (section 4, the same two categories, withdrawal via “Cookie settings” in the footer), but with its own banner: the choice only applies on lust.bio and is not shared with the Synapse Labs sites. All cookies of lust.bio apply only to lust.bio, not to synapselabs.studio. Necessary are: “sl_session” (sign-in, see above, 60 days from sign-in); “lust_auth” (protects the way to the account and back, 10 minutes); “sl_pass” is received only by our team for the preview before launch (12 hours, with an irreversible check value of the network so that access cannot be passed on); “lust_team_login” protects the team sign-in flow (10 minutes); “syn_ref” (invitation code until sign-in, 30 days); “syn_lang” (your chosen language, until you close the browser); and “sl-consent” in your browser’s storage with your choice. Under “Settings”, lust.bio stores on your device only with your consent: your colour scheme, a power-saving mode for slow devices, the volume of the music player, the snap grid in the design editor, notices already seen, a counter for a Christmas surprise, whether you already opened a hidden secret in this session (session storage, until you close the tab), and your language for a year instead of until the browser is closed. Without consent such a setting applies only to the open page. This data stays on your device. The legal basis for what is necessary is section 25(2) no. 2 TDDDG, for “Settings” your consent under section 25(1) TDDDG and Art. 6(1)(a) GDPR, and for processing otherwise Art. 6(1)(b) and (f) GDPR. We set no advertising or analytics cookies.

Data export and deletion: at acc.synapselabs.studio, Data, you can have all the data lust.bio stores about you sent as a file to your confirmed email address (Art. 15 and 20 GDPR, as described in section 10). If you delete your account, lust.bio immediately deletes your page with design, links, music, widgets, uploads, downloads, comments (including your comments on other pages), pacts and all other data that belongs only to you, and removes your files from file storage; this also applies if you delete your account in the settings of lust.bio. If a file cannot be deleted at once because of a problem with the storage, we retry automatically until it is gone. Anonymised because others need them are the hearts you gave, duel votes and tickets; ideas that others voted on stay without title, text and name. Until the end of their legal period the reason, type and time of decisions and reports remain without name, target ID, free text and appeal text, as do the check values of a permanent suspension (see “Reports and moderation”). We keep a log of every deletion with only an ID and the time, which we delete after 3 years; it exists to repeat the deletion if we have to restore a backup. Deleted data stays in our encrypted backups for 30 days at most and is never restored for other purposes. If we shut lust.bio down, we delete all data within 30 days of the announcement. We always grant deletion requests of minors; the minimum age is set by the Synapse Labs terms of use.

14Minecraft server Cortex SMP

We operate the public Minecraft server Cortex SMP (Java Edition and Bedrock Edition) and present it at play.synapselabs.studio. The controller named in section 1 is responsible. The server runs on our own server at Hetzner in Germany, and the page is delivered via Cloudflare as described in section 3. The page sets no cookies, loads fonts and all other files from our server and keeps no access log. Our server itself queries whether the server is online and how many players are there; no data about you is transmitted in the process. If you download mods via a link on the page or open our modpack in the Modrinth App, your device loads the files directly from Modrinth (Rinth, Inc., USA); its privacy provisions apply there.

Connection via playit.gg: Our server has no public address of its own. Connections to the game and to voice chat therefore run through the tunnel service playit.gg of Developed Methods LLC (Nevada, USA). playit.gg receives your IP address in the process and forwards the connection to our server; our server itself does not see your IP address. The USA does not have a level of data protection comparable to the EU, to our knowledge Developed Methods LLC is not certified under the EU-US Data Privacy Framework, and we have no standard contractual clauses with the company. Authorities in the USA could access the data, and your rights may be harder to enforce there. The transfer only takes place when you connect to the server, because it is technically necessary for this (Art. 49(1)(b) GDPR). If you do not want this, do not connect to the server. For the processing at playit.gg, its privacy policy applies (playit.gg/privacy-policy).

Sign-in: With the Java Edition, our server checks with Mojang (Microsoft Corporation, USA) whether your Minecraft account is genuine; in doing so it transmits your player name and a check value of your session. Microsoft is certified under the EU-US Data Privacy Framework. Chat messages of the Java Edition are signed by your game; other players can report them to Microsoft, for which Microsoft itself is responsible. With the Bedrock Edition, the software Geyser and Floodgate on our server translates the connection. In doing so we receive your Xbox gamertag and your Xbox user ID (XUID); you appear in the game with a dot before your name. So that Java Edition players can see your skin, Floodgate sends your skin image together with your XUID to the service of the open-source project GeyserMC, which converts the skin via the service MineSkin; these servers may be located outside the EU. We do not query a link between your Bedrock account and a Java account via the GeyserMC service. The legal basis is providing the game that you wish to use (Art. 6(1)(b) GDPR).

Game state: For each player, the server stores the player name, the Minecraft ID (UUID, derived from the XUID for Bedrock), your rank, your game state (inventory, position, health, achievements) and statistics such as play time, deaths and blocks mined. If you die, a grave with your items is created until someone empties it. We store this data for as long as the world exists. We create backups of the world every 12 hours and delete them after 3 days. On request we delete your game state. The legal basis is Art. 6(1)(b) GDPR.

Logbook against griefing: The server logs every change to blocks and containers as well as the picking up and dropping of items (who, what, where, when), so that we can detect and reverse destruction and theft. We delete these entries after 90 days. The legal basis is our legitimate interest in a fair game world (Art. 6(1)(f) GDPR).

Server logs: The server writes a log of joining and leaving, chat messages, commands and death messages, without IP addresses. We use it to review rule violations and to find errors, and delete it after 14 days at the latest. The legal basis is Art. 6(1)(f) GDPR.

Voice chat: If you use voice chat (Simple Voice Chat), the server transmits your voice live to players near you or in your group. We record nothing and store nothing; we have disabled recording in the game on the server. The legal basis is Art. 6(1)(b) GDPR.

Visible to others: Other players see your player name, your rank, your chat messages and your skin. In an internal administration page, our team also sees who is online and the players’ statistics; for this, our server loads the skins from Mojang. We issue bans by player name.

15Synapse Support

At support.synapselabs.studio we operate support for all our projects (AlphaCloud, Axon, glia, lust.bio, Cortex SMP and the Synapse Labs account). The controller named in section 1 is responsible. Support runs on our own server at Hetzner in Germany, with its own database on that server. You sign in with your Synapse Labs account (section 7). From the account, support receives over an internal connection only your display name, your profile picture, your account ID, your language, the time at which you created your account, and the names of your linked logins. For requests about AlphaCloud, support queries the account for your Discord ID and the list of your Discord servers so that you can select the affected server; only the ID, name and picture of the selected server are stored. Support never receives your password, your email address or the access keys of your linked logins. The legal basis is Art. 6(1)(b) GDPR. The pages are delivered via Cloudflare as described in section 3; what is said there applies to the server log files. Support does not use AI: requests are read and answered by people from our team.

Requests: For each request we store a number (SUP-…), the product, the topic, the priority, the status, the times, which team member is handling it, your notification settings and, if you give one, a rating from 1 to 5 stars. We store the subject, your answers to the form’s questions, the selected references (for example a Discord server), all messages and images encrypted (AES-256-GCM); only what the team sorts and filters by is stored in plain text. We check images on upload and store them anew as WebP, in which embedded information such as location and camera (EXIF) is removed; up to 5 images per message are allowed. Images that you upload but do not send are deleted by us after 24 hours. The team can send you a form inside a request (a close request, a request for details such as a server, an error number, a link or images, a request for consent); we store your answers like messages, encrypted, with the time of your answer, and delete them with the request. If you do not answer a close request for 7 days, the request counts as resolved. The legal basis is Art. 6(1)(b) GDPR.

Team and log: Only members of our team who are enabled for the respective product see your requests. They work in our internal tool, which is only reachable after signing in with a passkey (section 19). To help you, they can retrieve further information live about the references of a request, for example for AlphaCloud the state of the selected server (active modules, Premium, error messages of the last 14 days with their error number), for lust.bio your page (name and whether it is public, private or hidden), whether Synapse+ is active, the number of your links and comments, a running suspension and the team's latest decisions about you, and about your account, since when it has existed, whether a second factor is set up, which logins are linked and whether a Synapse+ subscription is running. This information is only displayed, not stored in support. The team never sees email addresses, IP addresses, passwords and payment data there. You do not see the team’s internal notes on a request; however, they are part of your data and included in the access response (below). We record every action of the team (opening a request, retrieving information, reply, note, change of status or priority, sanction) in a log with person and time, which is only appended to and not changed. It serves to prevent misuse by the team and to make decisions traceable. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is a secure and traceable handling of your data.

Email notifications: After you submit a request you receive an acknowledgement with its number. If the team replies to you, we ask you for feedback or your request is resolved, the account sends an email to your confirmed address; support does not learn this address. The email contains only the product, the number, the subject of your request, the number of new replies and a link, never the text of a message. We bundle the notifications: at most one email per request in 30 minutes and none while you have the request open. Emails are sent via our own mail server. You set which emails and direct messages you get from support centrally in your Synapse Labs account (section 7); you can also switch off notifications for single requests in the request. We always send the acknowledgement, the message that a request is resolved or closed, and notices about bans by email, because they are part of the service. The link in every email leads to the settings in the account. The legal basis is Art. 6(1)(b) GDPR.

Discord notifications: On request, our Discord app “Synapse Labs” additionally writes you a direct message. You add the app to your Discord account when you connect Discord in your Synapse Labs account (section 7); it only sends direct messages once you switch them on, in the settings in the account or in a request in support. In support we then store only that direct messages are allowed; we fetch your Discord ID anew from the account for every message, and the account releases it only if direct messages are switched on for support. The direct message contains the product, the number, the subject of your request, the first name of the team member who replied, and a link, never the text of a message. For delivery we transmit this information to Discord Inc. (San Francisco, USA). Discord states that it is certified under the EU-US Data Privacy Framework (Art. 45 GDPR); for the processing at Discord, its privacy policy applies. If Discord cannot deliver a message because you block direct messages or have removed the app, we switch off direct messages for you. You can switch them off at any time in the settings in the account, in the request or via the button in every direct message (it leads to the settings). The legal basis is your consent (Art. 6(1)(a) GDPR), which you withdraw by switching them off.

Sanctions: If someone misuses support, for example through insults, spam, attempted fraud, repeated false statements or threats, the lead of a product can record a warning or block support for 1, 7 or 30 days; only the owner can block permanently or for all products. Every block requires a reason from this list, a written justification and the affected requests as evidence. For this we store the reason, the encrypted justification, the evidence, the duration and who decided. We inform you of a block, its lifting and the outcome of an appeal by email via the account, with the justification as the team wrote it. You can appeal a block once; a different team member from the one who imposed the block decides on it. During a block you can continue to read and answer ongoing requests, but not open new ones. The owner reviews a permanent ban every year; if he confirms it, the period of 3 years starts again, and without confirmation and without a new sanction against you it is lifted by itself after 3 years. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is support that works for everyone.

Cookies and local storage: Support stores only what is necessary on your device and therefore shows no cookie banner. Necessary are: “sl_session” (section 7, so that it recognises you), “sl_pass” (received only by our team for the preview before launch, section 7), “sp_team_login” (protects the team sign-in process, 10 minutes) and “sl-consent” (cookie with your shared choice for the other Synapse Labs sites, 12 months, plus a copy in Local Storage, section 4). Also necessary is your draft of a request: the entry “sp-draft-…” per product in Local Storage holds the fields of the form and the time of the last change so that the draft is not lost when the page is reloaded. It stays on your device only and is never sent to us before you submit the request. We delete it after sending and otherwise automatically once it is older than 7 days; you can also delete it in your browser at any time. Because you explicitly use the form and the draft is needed for it, we do not need your consent: the legal basis is § 25 Abs. 2 Nr. 2 TDDDG (strictly necessary for a service you explicitly requested) and, for the processing, Art. 6(1)(b) GDPR. Withdrawing the shared choice does not delete the draft either. Under “Cookie settings” in the footer you can see all entries and change the shared choice for the other sites. There is no advertising or analytics in support.

Retention and deletion: We close a resolved request after 14 days if you no longer reply. We also close an open request in which neither you nor the team has written for 90 days; the usual periods apply from then on. We delete images 90 days after closing, and the request with all messages 12 months after closing (that is how long you can come back to an answer, and how long we can defend ourselves against claims about a request). We delete the team’s log after 24 months, and sanctions 24 months after they end. The owner reviews a permanent ban at least every 12 months; it ends by itself at the latest 3 years after the last confirmation or after the last new sanction against you, and you get an email. We delete the entry of your profile in support (name and profile picture, a copy of your account) when you have not signed in for 24 months and there is no request and no sanction about you. If you delete your account, we immediately delete all your requests, images and sanctions; the one exception is a ban in force at that moment: only a note remains with your account number, the scope, the reason category and the dates (no explanation, no evidence, no appeal), until the ban or its next review ends, at most 12 months (Art. 17(3)(e) GDPR, we must be able to show that the ban existed). In the log, only entries without the content of your requests remain until the end of their period. We always delete the data of children and young people on request, also after they have come of age. If the deletion of your account does not reach support, we catch it up weekly. At acc.synapselabs.studio, Data, you can have all data that support stores about you sent as a file to your confirmed email address (Art. 15 and 20 GDPR, as described in section 10); the names of team members are not included in it.

16Synapse Ideas and Synapse Bugs

At ideas.synapselabs.studio we operate Synapse Ideas, a public ideas board where you submit wishes for our projects, which others can vote on and you can comment on, and at bugs.synapselabs.studio Synapse Bugs, where you report errors that only you and our team can see. Both sites are one shared application for the Synapse Labs account, Axon, glia, lust.bio, Synapse Support and Cortex SMP. For AlphaCloud, its own sites ideas.alphacloud.bot and bugs.alphacloud.bot apply for now, with AlphaCloud’s privacy policy; if they move here, we will name it in this policy. The controller named in section 1 is responsible. The application runs on our own server at Hetzner in Germany, with its own database on that server. You can read the ideas board without an account. To submit, vote, comment, report and for bug reports you sign in with your Synapse Labs account (section 7). Over an internal connection the application receives from the account only your display name, your profile picture, your account ID, your language, the time you created your account and the names of your linked logins. It never receives your password, your email address or the access keys of your linked logins. The legal basis is Art. 6(1)(b) GDPR. The pages are delivered via Cloudflare as described in section 3; what is said there applies to the server log files. We use no AI on these sites: a person on our team reads and handles posts, bug reports and reports, and nothing is rated or summarised automatically.

Ideas and comments (public): For each idea we store a number (IDEA-…), the project, the title, the description, up to 5 images, the status, the times, for an idea that has been implemented the link to the changelog, the team’s answer and your account ID as the author, and for each comment the text, the time and your account ID. Ideas and comments are public: anyone can read them without an account, and they show your display name. We therefore store them in plain text, not encrypted. Do not put private information in them; report an error that involves private information in Synapse Bugs. The team’s answer appears as “Synapse Labs Team”; we record internally which person answered. The team merges duplicate ideas; the votes then move to the remaining idea. We check images when they are uploaded and store them anew as WebP, which removes embedded details such as location and camera (EXIF); we do not accept SVG. The legal basis is Art. 6(1)(b) GDPR, and for the public display of your display name our legitimate interest in an open ideas board (Art. 6(1)(f) GDPR).

Votes and follows: There is one vote per account and idea, which you can take back at any time. We store that your account voted for an idea; we show nobody who voted, neither other users nor the team, and only the number is public. If you follow an idea, we store that. Your notification settings (email, Discord, which kinds) live centrally in your Synapse Labs account (section 7), no longer at Synapse Ideas and Bugs; we moved earlier choices there and deleted them here. The legal basis is Art. 6(1)(b) GDPR.

Bug reports (private): For each bug report we store a number (BUG-…), the project, the area, the status, the severity, which team member is handling it, the times, your account ID and your details: summary, steps to reproduce, expected and actual behaviour, error number, how often the error occurs, since when and your device (for example browser and operating system; the form pre-fills it from your browser and you can change it before sending). We store steps, behaviour, all messages and your answers to questions encrypted (AES-256-GCM); only what the team sorts and filters by is in plain text, plus the summary shown in the lists. Therefore do not put private information in the summary. We treat images as with ideas (stored anew as WebP, without EXIF, up to 5 per post); we delete images you upload but do not send after 24 hours. Only you and members of our team who are enabled for the project see a bug report. It is never public, and we ask search engines not to include it. The team can reply to you in a bug report (you see the reply), add an internal note (you do not see it) and send you a form with questions; we store your answers to it encrypted like messages. Internal notes are part of your data and included in the copy of your data (below). After closing, you can reopen the report for 14 days. The legal basis is Art. 6(1)(b) GDPR.

Team and log: Only members of our team who are enabled for the respective project see your bug reports, and only in our internal tool, which is only reachable after signing in with a passkey (section 19). They see your display name and the details of the report, never your email address, IP address, password or payment data. We record every action of the team (opening, reply, note, question, change of status, severity or assignee, merging, hiding a comment or an idea) in a log with the person and the time, which is only appended to and never changed and contains no content of messages. It serves to prevent misuse by the team and to make decisions traceable. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is secure and traceable handling of your data.

Reports and moderation: Ideas and comments are content from users. Anyone who is signed in can report them (notice under Art. 16 DSA), with a reason from a list and a note; without an account one cannot report. We store the report with the reported idea or comment, the reason, the time and the account ID of the reporting person, and the note encrypted. A person on our team reviews every report; they can hide a comment or an idea, merge an idea or change its status. When we hide a post, the team writes a reason, which we store with that post. Whoever’s post we hide, we inform: the reason is shown under “My ideas” on ideas.synapselabs.studio, and we send you an email that points to it, even if you otherwise switched emails off, and depending on your setting in the account a direct message (the reason itself is never in the email). Section 4 of the Synapse Labs terms of use applies to the statement of reasons and to objections. Whoever wrote a post does not learn who reported it. The rules for content are in the Synapse Labs terms of use (section 13). The legal basis is Art. 6(1)(c) GDPR in conjunction with the Digital Services Act and our legitimate interest in an ideas board without unlawful content (Art. 6(1)(f) GDPR).

Email notifications: If the team changes the status of your idea or bug report, replies, asks for details, hides a post of yours or someone replies to your comment, the account sends you an email to your confirmed address, unless you have switched this off in your settings in the account; the application does not learn this address. Independently of that we always send you an email when your idea or bug report has arrived and when it is concluded (idea done, not planned or merged; bug report fixed, not a bug, closed or merged), because that is part of the service. The email contains only the project, the number, the title (for a bug report the summary), the new status and a link, never the text of a reply or message. We bundle notifications so that you do not get an email for every small thing. If we could not deliver a notification within 48 hours (for example because the mail server was unreachable), we discard it. Sending is done through our own mail server. In your settings you choose whether and for which kinds (team answers and status changes, replies to your comments, new comments on your idea) you get emails; the note in the email leads to these settings. The legal basis is Art. 6(1)(b) GDPR.

Discord notifications: On request, our Discord app “Synapse Labs” additionally writes you a direct message. You add the app to your Discord account when you connect Discord in your Synapse Labs account (section 7); it only sends direct messages once you switch them on in your settings in the account (Notifications). We store only that choice there; we fetch your Discord ID anew from the account for every message, and the account releases it only if direct messages are switched on for the service. The direct message contains the project, the number, the title and a link, never the text of a reply or message. For delivery we transmit this information to Discord Inc. (San Francisco, USA). Discord states that it is certified under the EU-US Data Privacy Framework (Art. 45 GDPR); Discord’s privacy policy applies to processing at Discord. If Discord cannot deliver a message because you block direct messages or removed the app, we switch direct messages off for you. You can switch them off at any time in the settings in the account, also via the button in every direct message. The legal basis is your consent (Art. 6(1)(a) GDPR), which you withdraw by switching them off.

Bot protection: When you submit a new idea, a new bug report, a comment or a reply, a vote (only when giving it, not when taking it back) or a report, Cloudflare Turnstile (Cloudflare, Inc., USA) checks whether a human is acting. This works only when signed in; messages in a bug report, answers to requests for information, editing, following, closing, reopening and reading are not checked. We load the Cloudflare script only when you start one of the checked actions, not when you open the page. Cloudflare receives technical data of your browser and your IP address; our server sends the result of the check with your IP address to Cloudflare for confirmation and stores none of it. The legal basis is our legitimate interest in sites free from abuse (Art. 6(1)(f) GDPR); Cloudflare is certified under the EU-US Data Privacy Framework (see section 5).

Who is writing: When you write a comment, a reply or a message in a bug report while signed in, we store for a few seconds only your public display name, whether you or the team is writing, the internal identifier of the sender and the time, never the text. Under an idea, signed in visitors see this (“Name is writing”); when the team writes the answer, only “The team is writing” appears, never which member. In a bug report, only you as the reporting person and the team see it (“Team member is writing”); an internal note by the team never sends such a display. Entries older than one minute are deleted by a regular run, and we delete your entries immediately with your account. The legal basis is Art. 6(1)(b) and (f) GDPR (a conversation in which both sides see that a reply is being written).

Cookies and local storage: Synapse Ideas and Bugs store only what is necessary on your device and therefore show no cookie banner. Necessary are: “sl_session” (section 7, so that they recognise you), “sl_pass” (received only by our team for the preview before launch, section 7), “fb_team_login” (protects the team sign-in process, 10 minutes) and “sl-consent” (cookie with your shared choice for the other Synapse Labs sites, 12 months, plus a copy in Local Storage, section 4). Cloudflare Turnstile is added as bot protection when submitting (see “Bot protection” above). Also necessary is your draft of an idea or a bug report: the entries “fb-idea-draft” and “fb-bug-draft” in Local Storage hold the fields of the form (without images) and the time of the last change so that the draft is not lost when the page reloads. It stays on your device only and is never sent to us before you submit it. We delete it after sending and otherwise automatically once it is older than 7 days; you can also delete it in your browser at any time. Because you explicitly use the form and the draft is needed for it, we do not need your consent: the legal basis is § 25 Abs. 2 Nr. 2 TDDDG (strictly necessary for a service you explicitly requested) and, for the processing, Art. 6(1)(b) GDPR. Withdrawing the shared choice does not delete the draft either. Under “Cookie settings” in the footer you can see all entries and change the shared choice for the other sites. We store nothing else in the browser (no language or theme choice, comments are not cached). There is no advertising or analytics on these sites.

Retention and deletion: We delete the images of a bug report 90 days after closing, and the report with all messages 12 months after closing. We close a bug report nobody has touched for 12 months; the same period applies from then on. For a report about an idea or a comment, we delete the name and the note of the person who reported it 90 days after the team has handled it, and the report itself (kind, reason, outcome) 12 months after that. If the report led the team to hide an idea or a comment, that note stays until the end of the third year after the decision, so that we can substantiate the reason and defend ourselves (Art. 17(3)(e) GDPR). Reports the team has not handled after 6 months we close as handled, without a decision and without deleting anything; the same periods then apply as for handled reports. Hidden ideas and comments lose their text and images 12 months after hiding; the team’s reason, which the author reads under “My ideas”, stays until the end of the third year after the decision. An idea you withdrew we delete 30 days later. We delete the team’s log after 24 months, the queue of notifications 30 days after sending, and the list of what we sent you and when (kind and time, never the text) after 90 days. When a status changes, the log names the first name of the team member who made the change; this note belongs to the idea and disappears with it. We delete the entry of your profile (name and profile picture, a copy of your account) when you have not signed in for 24 months and you have no idea, comment, bug report or report. If you delete your account, we delete your ideas, your comments, your bug reports with all messages and images, your votes and follows; your notification settings are deleted by the account together with your account. If others built on one of your ideas or comments (votes, replies, merged ideas), only an empty placeholder “[deleted]” remains, without your text, your images, your name and your account ID, so that other people’s votes and replies do not point to nothing (Art. 6(1)(f) GDPR). A report you made stays as a note without your name and without your note (if it was still open, we close it as handled). You can also have a single idea or comment removed without deleting your account: write to support@synapselabs.studio. We always delete the data of children and young people on request, also after they have come of age. If the deletion of your account does not reach the sites, we catch it up weekly. At acc.synapselabs.studio, Data, you can have all data that Synapse Ideas and Bugs store about you (your ideas, comments, votes, follows, your bug reports with all messages including the internal notes, and your reports) sent as a file to your confirmed email address (Art. 15 and 20 GDPR, as described in section 10); the names of team members are not included.

17Website synapselabs.studio

Contact forms

If you write to us via a contact form, we process the information from the form (depending on the topic: name, email address, subject, message and further fields such as username, company, medium, portfolio link or affected system) in order to handle your request and reply to you. The message is delivered via our own mail server to the responsible mailbox (for example support@ or jobs@synapselabs.studio) and handled in our self-operated ticket system; after it is closed, we delete it together with our reply after 12 months, applications (jobs@) after 6 months and legal matters (legal@) after 6 years, counted from the end of the year in which we closed it; if you reopen a closed request, the period starts again. A request that nobody has touched for 24 months we close ourselves; then the period runs. If you want us to delete your request earlier, write to legal@synapselabs.studio; we then delete it with all messages, unless a law obliges us to keep it. We empty the other shared team mailboxes (for example for sign ups at services and automatic notices of our servers) after 12 months and 30 days respectively. We keep invoices and payment records for eight years, counted from the end of the year of the invoice (§ 147 AO). To the email address you provide, we send an automatic acknowledgement of receipt (at most once in three days per address and mailbox) and later our reply. The legal basis is Art. 6(1)(b) GDPR insofar as the request relates to a contract or its preparation, otherwise our legitimate interest in answering requests (Art. 6(1)(f) GDPR).

Newsletter and dev updates

We have two mail lists you subscribe to separately: the newsletter (news about our games and projects, sign-up in the footer of our pages) and the dev updates (one or two mails a month about what we are building, sign-up on our home page while the website is not open yet). We use the double opt-in procedure: after signing up you get a mail with a confirmation link that works for 48 hours. Only when you click it is the sign-up active. The legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time.

We store your email address encrypted, together with a check value of the address (so the same address is not on a list twice), the language, where you signed up, the times of sign-up and confirmation, and the version of the consent text. Unconfirmed sign-ups are deleted after 7 days. Against abuse we limit sign-ups per network; for that the IP address is only held briefly in memory and not stored. The page never tells whether an address is already signed up.

You can unsubscribe with the link in every mail or directly in your mail program (one-click unsubscribe). We then delete your address at once (from the delivery logs of our mail server after 14 days, section 3). We keep the check value and the times of sign-up, confirmation and unsubscribing until the end of the third year after the year in which you unsubscribed, so that we can prove that you consented and unsubscribed (Art. 6(1)(c) and (f) GDPR in conjunction with Art. 7(1) GDPR); the address cannot be recovered from the check value. If you want us to remove your address at once without using the link, write to legal@synapselabs.studio; we remove it within 30 days, usually the same day. Even then only the check value and the times stay as proof.

We send the mails through our own mail server. Pictures and our logo are part of the mail itself; nothing is loaded when you open it. We measure neither whether you open a mail nor which links you click. We only record whether our mail server accepted a mail and whether the recipient's mail server refused it (for example because the mailbox does not exist or is full). If the mailbox does not exist, we take the address off the list and delete it at once. An address that bounces before it was confirmed is deleted completely, without proof, because it never consented. Nobody in our team sees the addresses; they only see numbers (how many people signed up and how many mails arrived).

Live player counts

The player counts on this website are retrieved from Roblox by our own server. No personal data about you is transmitted to Roblox in the process.

Fonts

The fonts of this website are loaded locally from our server. No connection to Google servers is established in the process.

Our website links to offerings of Roblox, Discord, YouTube and TikTok. Only when you click a link are you redirected to the page of the respective provider. Its privacy provisions apply there.

Short links such as synapselabs.studio/go/… or name.synapselabs.studio first open a page of ours that shows the destination of the link; you only get there after clicking “Continue”. The page runs on our own server and is delivered via Cloudflare as described in section 3. To see how often our links are used, our server records for each request only the time, the link requested and the response code, without your IP address. These entries are combined within about one minute into one number per link and day and then deleted; we keep the daily numbers for at most 400 days. No cookies are set and no scripts are loaded. The legal basis is our legitimate interest in measuring the use of our links and detecting abuse (Art. 6(1)(f) GDPR).

18Status page and email notifications

At status.synapselabs.studio we operate a status page that shows whether the services of our projects Synapse Labs, AlphaCloud, Axon, glia and lust.bio are reachable, and informs about incidents and maintenance. The controller named in section 1 is also responsible here. The page runs on our own server and is delivered via Cloudflare as described in section 3; what is said there applies to the server log files. The status page sets no cookies, stores nothing on your device and loads no content from third parties.

If you subscribe to email notifications, we store your email address, the chosen projects, whether you also want maintenance announcements, the language of the emails, the status of the subscription, the times of sign-up, of sending the confirmation email and of confirmation, the version of the notice text you agreed to, and check values (hashes) of the links for confirming and managing. We use this data only to send you notices about incidents and maintenance of the chosen projects; the emails contain no advertising. We store neither your IP address nor information about your browser, and we do not measure whether you open an email or click links (no tracking pixels, no redirect links). To protect against abuse we limit the number of sign-ups per IP address; for this, only a check value of the address is held briefly in working memory.

We use the double opt-in procedure: the subscription only becomes active once you confirm it via the link in the confirmation email. We send at most one confirmation email per address in 24 hours. The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time with effect for the future by unsubscribing with one click via the link in every email; via the “Manage subscription” link you can change your selection. Emails are sent via our own mail server. If you reply to an email, it goes to our support; section 17 applies to this.

We delete unconfirmed sign-ups after 48 hours. We store confirmed subscriptions until you unsubscribe. When you unsubscribe, we delete your address and all associated data. We keep only an irreversible check value of the address formed with a secret key (HMAC), plus the time of your confirmation, the version of the notice text and the time of your unsubscribe, until the end of the third year after the year of your unsubscribe. This way nobody adds it again without a new confirmation by you in that time, and we can prove that you consented and unsubscribed. The legal basis for this is our legitimate interest in not sending emails against your will and in being able to defend ourselves against claims (Art. 6(1)(f) GDPR, Art. 17(3)(e) GDPR). We delete records of which notification was sent to which subscription 30 days after sending, at the latest when you unsubscribe. A confirmed address to which our mails repeatedly failed for good and that never received a mail is deleted. If you want to be removed without the link, write to legal@synapselabs.studio.

19Team hub, team mailboxes and team chat

For people who work in the team of Synapse Labs or AlphaCloud we run an internal hub with sign in through our own login service Pocket ID (passkeys only, sign in only for team members), a mailbox, team chat (Matrix), a password manager (Vaultwarden) and a files page. The hub, the login service, team chat and webmail are reachable over the internet; the connection runs through Cloudflare (section 3), which forwards the traffic of these services, encrypts it and fends off attacks. The admin area of the login service is additionally protected by Cloudflare Access: access is only possible for our owner, and Cloudflare stores his account details and the time of the sign in. The password manager and the Minecraft panel are only reachable through our private network. The controller is the one named in section 1; the legal basis is carrying out the cooperation (Art. 6(1)(b) GDPR, for volunteers Art. 6(1)(f) GDPR) and our legitimate interest in the security of the system.

Account: first name, surname, role, sender name, addresses and aliases, Discord ID, the accesses to Pocket ID and Vaultwarden. Sessions in the hub last up to 30 days and are deleted at sign out; we store no IP address, only the browser name. We delete the sign in history of Pocket ID with IP address and browser after 7 days (the hub deletes older entries hourly).

IP addresses: these services see the IP address that Cloudflare passes on to us as the visitor's address. The hub uses it only in memory to limit excessive requests. Pocket ID keeps it in the sign in history (7 days, see above). The mail server Stalwart blocks an address after repeated failed sign ins; this block is held in memory only. The chat server stores the addresses of devices for 7 days. We delete the logs of the servers (journal) after 7 days. The legal basis is our legitimate interest in the security of the system (Art. 6(1)(f) GDPR).

Leaving: whoever leaves the team is blocked on the last day. Three months later we delete the mailbox with all mail, the access, the password vault, the chat account (with deletion of the profile and the messages as far as Matrix can) and the entry in the hub. In these three months we secure what we have to keep (for example an invoice that is a voucher). Where names appear in old entries of the hub we replace them with “former member”.

Administration log: what team members do in the hub (for example adding people, deciding reports) we log with the name, the action and a number for 24 months for security and traceability; free text about decisions on third parties is not in the log. Reports of the desktop app about the setup we delete after 14 days.

“Is writing” display: When you write the answer to a bug report in the hub, the reporting person sees your display name for a few seconds (“Name is writing”); for the answer to an idea, only “The team is writing” is shown publicly. An internal note never sends such a display (section 16).

Chat: messages in the rooms the hub manages stay for 12 months, direct messages for 6 months, files as long as their message. The chat does not show an online status. General rooms are not end to end encrypted, administration rooms are.

Mailboxes: shared mailboxes (for example for sign ups at services) we empty after 12 months, automatic notices of our servers after 30 days. The billing mailbox stays eight years from the end of the year of the invoice, the mailbox for legal matters six years, both for tax and commercial law reasons. The webmail profile (contacts, settings) we delete at the latest 30 days after somebody stopped signing in.

Backups: we back up the internal database and the mailboxes daily, encrypted, and delete the backups after 30 days. When we restore a backup we delete again the cases and people that were deleted after it was made; for that we keep a deletion list with the case number or the mail name of the person and the time, without content, for 3 years and 30 days. Server logs with IP addresses we delete after 7 days.

20Confidentiality agreement for team members (NDA)

Anyone who works in the team of one of our projects (for example AlphaCloud, Axon, glia or lust.bio) concludes a confidentiality agreement (NDA) with us. We request it for your Discord ID. You can only fill it in and sign it in your Synapse Labs account at acc.synapselabs.studio, and only with the account that this exact Discord login is linked to. We send the link to the confirmed email address of that account, our team can also give it to you directly. If a project is added later, you get an addendum that you accept in the same way.

Which data: for the request your Discord ID, the name we address you by, the projects and your role in them, who made the request and, where applicable, the number of the agreement the new one replaces. In the NDA your first and last name, date of birth, address, email address, Discord name and Discord ID (from your linked login), the place and time of signing and your drawn signature or the uploaded scan of the signed agreement. For minors also the kind of custody as well as name, email address, place of signing and signature of the legal representatives and the time of their confirmation. For an addendum the new projects, place, time and signatures. If you later report a new address or email address, the previous and the new details with their date.

Purpose and legal basis: The NDA and every addendum are a contract with you, we process the details to conclude, perform and enforce it (Art. 6(1)(b) GDPR). The date of birth also serves to check whether the consent of the legal representatives is needed. We process the details of the legal representatives to obtain and be able to prove their consent (Art. 6(1)(f) GDPR, legitimate interest in an effective and provable contract). Without the details the agreement cannot be concluded.

Security and who sees what: We store all details, signatures, scans and the generated PDFs encrypted (AES-256-GCM) with a key of its own only for the NDA that is not kept in the database. Lookups only use encrypted check values (HMAC), never the details themselves. Only our owner Elias Friedrich, as your contracting party, sees the decrypted details, signatures and scans. Other team members with access to our internal administration only see whether and for what an NDA exists (number, projects, role, status, dates), but no personal details. No AI evaluates the NDA, and no project receives the personal details. If your NDA names the project AlphaCloud or replaces an agreement with AlphaCloud, AlphaCloud receives only the number of the NDA, its status, the projects with your role and your Discord ID, so that AlphaCloud knows who may be given team roles there (Art. 6(1)(f) GDPR, legitimate interest in giving team rights only to people with an effective confidentiality agreement). If the NDA replaces an earlier agreement with AlphaCloud, its number stands on the new one. Synapse Labs countersigns automatically with a stored signature as soon as the agreement takes effect.

Emails: When the NDA or an addendum takes effect, you get your copy as a PDF by email to the address from the NDA (or the one reported last), for minors the legal representatives receive it too. The legal representatives also get an email with their own confirmation link, valid for 30 days, and one reminder after 7 days without confirmation. We do not use their addresses for anything else. We confirm a changed address or email address by email to the new address and, if the email address changed, also to the previous one. If a submitted NDA needs a correction or we decline it, we email you the reason. All emails go through our own mail server.

Unchangeable copies: Every submitted version, the effective version, every addendum and every uploaded scan is also stored as an unchangeable, encrypted copy with a checksum (SHA-256), so that it can later be proven what exactly was signed. The signed agreement itself is never changed.

Storage period: We delete an NDA that was not completed (draft, correction needed, declined) 30 days after its last change, an NDA waiting for the legal representatives 30 days after it was submitted, and likewise an addendum that was not accepted. We delete a submitted NDA that the team has not decided on for 90 days, with its files, after 90 days; the team is reminded after 60 days. We delete the email links of the legal representatives 30 days after they expired or were confirmed. We delete a request that did not lead to an NDA or an addendum, or that was withdrawn, after 30 days. We keep an effective NDA with its addenda, copies and reported changes for as long as duties under it exist and claims under it can become time-barred (§ 8 (4) of the NDA): after the end of your work, confidentiality continues for 3 years (§ 6 (2) of the NDA), after which claims can still be raised for 3 years. We therefore delete it at the end of the sixth calendar year after the year in which your work ended. If the end of your work is not recorded, the team reviews it after 5 years and we delete the NDA 10 years after the day it became effective at the latest. This also applies to an NDA that was replaced by a newer one. If AlphaCloud knows a copy, we report the deletion to it first. For an NDA of a minor we delete the email addresses of the legal representatives when the work ends; their names, places and signatures stay on the NDA, we do not change the stored PDF copy. The countersignature of Synapse Labs stays stored as long as signed NDAs exist. If you delete your Synapse Labs account, an effective NDA is kept as proof of the contract, only without a link to the account. We comply with requests for deletion from minors or former minors as soon as no concrete claim is to be expected any more.

Your rights from section 22 apply here too, and also to the legal representatives, including the right to object to the processing of their details under Art. 6(1)(f) GDPR.

21Retention periods at a glance

How long we keep data is stated for the service it belongs to: server log files in section 3, cookies and local storage in section 4, backups in section 6, the account in section 7, Synapse+ and contracts in section 8, AlphaCloud in the account in section 9, data export and deletion of the account in section 10, Axon in section 11, glia in section 12, lust.bio in section 13, Cortex SMP in section 14, support in section 15, Synapse Ideas and Synapse Bugs in section 16, the services of the website in section 17, the status page in section 18, hub, mailboxes and chat in section 19 and the confidentiality agreement in section 20.

22Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21). You can withdraw a consent you have given at any time with effect for the future. You can also lodge a complaint with a data protection supervisory authority.