Legal
Privacy Policy
- Last updated
1. Overview
Noiz ("we," "our," or "us") is committed to protecting your privacy and ensuring the security of your personal data. This Privacy Policy explains how we collect, use, disclose, store, and safeguard your information when you use our service at noiz.bio (the "Service").
This policy applies to all users worldwide, with enhanced rights for residents of the European Economic Area (EEA), United Kingdom, Switzerland, and California. We comply with:
- General Data Protection Regulation (GDPR) - EU Regulation 2016/679
- UK Data Protection Act 2018 and UK GDPR
- California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA)
- German Federal Data Protection Act (BDSG)
- ePrivacy Directive (Cookie Law)
This policy should be read together with our Terms of Service and Section 11, on what we store on your device.
2. Data Controller
For the purposes of the GDPR and other applicable data protection laws, the data controller responsible for your personal data is:
Noiz
Inhaber: Fabian Schneidruck
Leopoldplatz 13
76437 Rastatt
Germany
USt-IdNr.: DE367705746
Data Protection Contact
For all privacy and data protection inquiries, please contact our designated data protection representative:
Email: privacy@noiz.bio
Legal matters: legal@noiz.bio
Response timeframe: We aim to respond to all data protection inquiries within 30 days.
3. Legal Basis for Processing (GDPR Article 6)
We process your personal data only when we have a valid legal basis under the GDPR. The table below explains the legal bases we rely on for different processing activities:
| Processing Activity | Legal Basis | GDPR Article |
|---|---|---|
| Account creation and management | Performance of contract | Art. 6(1)(b) |
| Payment processing | Performance of contract | Art. 6(1)(b) |
| Profile hosting and display | Performance of contract | Art. 6(1)(b) |
| The waitlist, and the email that tells you we have opened | Steps at your request before a contract | Art. 6(1)(b) |
| Giving an AI app you connect access to your page | Performance of contract | Art. 6(1)(b) |
| Analytics and service improvement | Legitimate interest | Art. 6(1)(f) |
| Security and fraud prevention | Legitimate interest | Art. 6(1)(f) |
| Analytics measurement (see Section 11) | Legitimate interest, with opt-out | Art. 6(1)(f) |
| Tax and financial records | Legal obligation | Art. 6(1)(c) |
| Responding to legal requests | Legal obligation | Art. 6(1)(c) |
Legitimate Interest Assessment
Where we rely on legitimate interests, we have conducted a balancing test to ensure our interests do not override your fundamental rights. Our legitimate interests include:
- Improving and optimizing our services
- Preventing fraud and ensuring platform security
- Understanding how users interact with our service
You may object to processing based on legitimate interests at any time by contacting us.
Consent Withdrawal: Where we rely on consent, you have the right to withdraw your consent at any time by contacting us at privacy@noiz.bio or using the provided mechanisms (e.g., Privacy choices in the footer, unsubscribe links). Withdrawal does not affect the lawfulness of processing before withdrawal.
4. Categories of Personal Data
We collect and process the following categories of personal data, organized according to GDPR-compliant categories:
Identity Data
- Username (publicly displayed)
- Display name (optional, publicly displayed)
- Email address (used for authentication and communication)
- Password (hashed and encrypted, never stored in plaintext)
Contact Data
- Email address
- Contact form submissions
Profile Data
- Biography (optional, publicly displayed)
- Profile picture/avatar (optional, publicly displayed)
- Banner image (optional, publicly displayed)
- Social media links (optional, publicly displayed)
- Custom links and their order
- Pages and the widgets on them: the text, labels, values and links you put in them, and any Spotify, Apple Music, YouTube or Twitch item you add (publicly displayed once published)
- Theme and appearance preferences
- Premium status and badge information
- Connected Discord account details, if you connect one: your Discord id, handle, the address of your Discord avatar, the invite code of a server you chose to feature and, if you turn on live status, your latest Discord status (Section 8)
Technical Data
- IP address: kept in full for 30 days in sign-in security logs, so we can investigate attacks on your account; stored only as a one-way digest everywhere else, for as long as each purpose needs: 24 hours to 7 days in abuse limiters, 90 days in pseudonymized analytics and one year in admin access logs (see the retention table below)
- Browser type and version
- Device type (desktop, mobile, tablet)
- Operating system
- Referring website/source
Usage Data
- Profile view counts and statistics
- Link click and play analytics
- Pages visited within the Service
- Features used and interaction patterns
Privacy-First Profile Analytics
We use privacy-friendly first-party analytics to count profile views, link clicks and plays (a press on a player embedded in a profile). This helps profile owners understand how their noiz.bio page performs. We do not use third-party tracking pixels for this analytics system, do not store raw IP addresses, and do not sell analytics data. To keep these numbers trustworthy, we filter duplicate refreshes, obvious bots, social-preview crawlers and suspicious repeated activity: this helps reduce artificial traffic, though no system prevents every fake view or click.
- No cookies or persistent device identifiers are set for this analytics.
- Visitors are counted using a daily-rotating, one-way hash that cannot be reversed to an IP address or used to track you across other websites or from one day to the next.
- Each view is stored as a pseudonymous record, and creators see only totals: traffic source/referrer, UTM tags, coarse device/browser/OS, and country (only when the visitor's platform safely provides it).
- Bots, social-preview crawlers, duplicate refreshes and suspicious repeated clicks are filtered out of the counted totals. Analytics are private to the profile owner (and platform administrators).
- Deleting your profile or account also deletes its analytics data.
Transaction Data
- Purchase history
- Premium purchase and access status
- Payment timestamps
- Stripe customer ID (we do not store full card details)
- Your billing country and postal code, and a business name and VAT ID if you enter them, which Stripe collects at checkout to calculate VAT, and the VAT amount of your purchase
- If you buy Premium as a gift: the username you give it to and, on that person's purchase record, your account and username. We tell them by email who gave them Premium
- If you send a withdrawal declaration through the withdrawal function at noiz.bio/withdraw or its shortcuts on the Billing page and in the dashboard: the name you enter, the contract or order identifier as you typed it, the email address you choose for the confirmation, the date and time we received it, its reference number, whether the confirmation could be delivered and, if you were signed in, your account. The function works without an account. To limit abuse it keeps a one-way digest of your IP address in the abuse limiter, for up to 7 days. If you delete your account, the name and the email address on your declarations are blanked and the rest of the record is kept with the payment record
Security Data
- Two-Factor Authentication (2FA) enrollment status
- 2FA backup codes, stored only as one-way hashes
- Login attempt records
- Authentication events and timestamps
Content Data
- Uploaded images (avatar, banner)
- Background music files (if uploaded)
- Custom icons and media
Waitlist Data
- Your email address, and the username you asked us to hold, if you gave one
- When you joined and confirmed your address, and a hashed confirmation link that expires
- An invite code that lets you claim the name we hold for you, where you came from if the link you followed said so, and any note we write on the entry
- Whether and when we emailed you that noiz is open, and when you unsubscribed if you did
Template Data
- The templates you share: their name, description and categories, your page's look and copies of the files it uses, shown publicly with your username and a link to your page
- Which templates you keep among your favorites, and which of your pages applied which template
- Your page's look from just before you applied a template, so you can undo it
Connected AI App Data
- The AI apps you connect to your account: the name and identifier each app gives itself, the permissions you chose, and when you connected it
- A record of every change a connected app makes to your page: which action, what it changed, and when
Special Categories of Data: We do NOT intentionally collect special categories of personal data as defined in GDPR Article 9 (e.g., racial or ethnic origin, political opinions, religious beliefs, health data, biometric data, sexual orientation). If you voluntarily include such information in your profile, you do so at your own discretion.
5. How We Collect Your Data
We collect personal data through the following methods:
5.1 Direct Interactions
Data you provide when you:
- Create an account or register for our Service
- Complete your profile information
- Make a purchase or upgrade to Premium
- Contact us via email, support form, or social media
- Report a problem or provide feedback
- Connect an AI app, such as ChatGPT or Claude, to your account
5.2 Automated Technologies
Data collected automatically when you interact with our Service:
- Local storage on your device, all of it listed in Section 11 (noiz.bio sets no cookies; connecting an AI app is the one step that does, also in Section 11)
- Server logs recording requests to our infrastructure
- Our own server-side analytics, which stores nothing on a visitor's device (Section 11.2); a signed-in creator's browser keeps the note in Section 11.1 that keeps their own visits out of their numbers
- Security monitoring systems
5.3 Third Parties
Data we may receive from third parties:
- Payment Processors: Transaction confirmation and status from Stripe
- OAuth Providers: Basic profile information if you sign up or connect using Google or Discord (we receive only what you authorize. Section 8 lists exactly what Discord gives us)
6. Purposes of Processing
We use your personal data for the following purposes:
| Purpose | Data Used | Legal Basis |
|---|---|---|
| Provide and maintain the Service | Identity, Profile, Technical | Contract |
| Process payments | Identity, Contact, Transaction | Contract |
| Let an AI app you connect read or change your page | Identity, Profile, Usage, Connected AI App | Contract |
| Manage your account and authentication | Identity, Security | Contract |
| Send service-related communications | Identity, Contact | Contract |
| Provide customer support | Identity, Contact, Technical | Contract/Legitimate Interest |
| Improve and personalize the Service | Usage, Technical | Legitimate Interest |
| Detect and prevent fraud | Technical, Security | Legitimate Interest |
| Comply with legal obligations | All relevant categories | Legal Obligation |
| Send marketing communications | Identity, Contact | Consent |
7. Data Sharing and Recipients
We may share your personal data with the following categories of recipients:
- Service Providers: Third parties that help us operate the Service, including hosting, payment processing and email delivery. These parties process data only on our behalf and under our instructions.
- AI Apps You Connect: If you connect an AI app, such as ChatGPT or Claude, to your account, we send that app the page data the permissions you chose cover: your page's address, display name, bio, location and links, and, if you allowed it, your page's views and clicks. Never your email address, password, two-factor settings or payment details. The company behind the app (for example OpenAI or Anthropic) receives this as a separate controller under its own privacy policy, which decides what it does with the data and where it processes it; it is not our processor. You can disconnect an app at any time under Settings, Security, and it loses access right away.
- Sites a Creator Links To: When you press a link on a creator's page, the site it opens learns that you came from noiz.bio: your browser sends it the address noiz.bio, never the page you were on. If the creator turned on "Tag links to your sites", a link to their own website or shop also carries utm_source=noiz and utm_medium=link_in_bio. That site handles what it receives under its own privacy policy.
- Professional Advisers: Lawyers, accountants, auditors, and insurers who provide consultancy, banking, legal, insurance, and accounting services.
- Law Enforcement and Regulators: When required by law, court order, or governmental authority, or to protect our legal rights.
- Business Transfers: In connection with any merger, acquisition, reorganization, sale of assets, or bankruptcy proceeding. We will notify you of any such transfer and your options.
- With Your Consent: Any other third parties when you have given us explicit consent to share your information.
We NEVER Sell Your Personal Data
Noiz does not sell, rent, or trade your personal information to third parties for their marketing purposes. We do not participate in data broker transactions. Your data is never monetized through third-party advertising networks.
8. Sub-Processors and Third-Party Services
We use the following sub-processors and third-party services to operate Noiz. Each has been reviewed for GDPR compliance and appropriate data protection measures. Where a service does not meet that bar, its row says so plainly and the notes below explain what we do about it:
| Service | Purpose | Location | Safeguards |
|---|---|---|---|
| Stripe | Payment processing | USA | EU-US DPF, SCCs |
| Supabase | Database, authentication, edge functions | EU (Frankfurt) | EU-based processing, Art. 28 DPA |
| Cloudflare | Website hosting, storage and delivery of uploaded files (R2), CDN, edge compute, DDoS protection, the record of the AI apps you connect (Workers KV), and its public DNS resolver (cloudflare-dns.com), which we ask whether the domain of an email address you enter at sign-up, on the waitlist or when changing your address can receive mail. Only the part after the @ is sent | Uploaded files stored in Western Europe; served from the global edge (EU for European visitors); AI-app connections in Cloudflare's global key-value store | EU-US DPF, SCCs, Art. 28 DPA |
| Resend | Transactional email (sign-in links, confirmation, password reset), and a copy of the email you send to our @noiz.bio addresses, so we can read and answer it | USA | SCCs, Art. 28 DPA |
| Namecheap (Private Email) | Hosting of our @noiz.bio mailboxes (support, business, legal, privacy and security), where the email you send us is received and stored | USA (Phoenix, Arizona) | SCCs, Art. 28 DPA |
| Fontshare (Indian Type Foundry) | Webfont delivery, for four optional profile fonts only | Global CDN | IP address only, no cookies: see note below |
| Google (OAuth) | Social authentication (optional) | USA | EU-US DPF, SCCs |
| Valve (cdn.cloudflare.steamstatic.com, shared.akamai.steamstatic.com) | Game cover art, when a creator shows a games shelf on their page | USA | Covers are loaded by your browser from Steam's CDN rather than copied to our servers: see note below |
| GitHub (github.com) | A repository owner's avatar, when a creator shows a GitHub project on their page | USA | Loaded by your browser from GitHub rather than copied to our servers, and without telling GitHub which page you are on: see note below |
| Discord (discord.com, cdn.discordapp.com) | Social authentication (optional), reading the public details of a server a creator chooses to show on their page, and the live status of creators who turned that on | USA | Sign-in and server details are requested by our servers; a live status is sent by Discord to our bot; avatars, server icons, badges and game pictures are loaded by your browser from Discord's CDN: see note below |
| Hetzner Online (hetzner.com) | Hosting the bot we run in the Noiz Discord server, which gives the Premium role and reports the live status creators turned on | EU (Germany) | EU-based processing. Holds Discord ids and statuses in memory while it runs and nothing about visitors: see note below |
| Spotify (open.spotify.com) | Playing a track, album, playlist, artist page, podcast episode or show a creator has added to their page or to one of their pages | USA | Contacted as the page renders, before you interact with anything. Players below the fold are not loaded until you scroll near them. For a Spotify song, Spotify’s player script loads in the page and plays the song, so Spotify is contacted as the song nears the screen. The same goes for a Spotify playlist or album on a page, one song at a time. The titles, artists and covers are fetched by our server from Spotify’s public pages for the song, playlist or album, and the covers are served from noiz |
| YouTube (youtube-nocookie.com) | Playing a video or playlist a creator has added to their page or to one of their pages | USA | Contacted as the page renders, before you interact with anything; the no-cookie player is used. Players below the fold are not loaded until you scroll near them |
| Twitch (player.twitch.tv, clips.twitch.tv) | Playing a stream, a past broadcast or a clip a creator has added to their page or to one of their pages | USA | Contacted as the page renders, before you interact with anything. Players below the fold are not loaded until you scroll near them |
| Apple Music (embed.music.apple.com) | Playing a song, album or playlist a creator has added to their page or to one of their pages | USA | Contacted as the page renders, before you interact with anything. Players below the fold are not loaded until you scroll near them |
A note on uploaded files
Everything uploaded to Noiz (profile pictures, banners, backgrounds, videos, music, clips and other media) is stored in Cloudflare R2, Cloudflare's file storage, and served from r2.noiz.bio. Our database with Supabase in Frankfurt holds the address of each file, not the file itself.
The storage is located in Western Europe. That is where Cloudflare placed it when it was set up, not a contractual limit to the EU, so the safeguards in the Cloudflare row above apply to it. So that pages load quickly, copies of these public files are also kept in Cloudflare's caches close to the visitors who request them.
When a file is deleted, it is removed from storage and its cached copies are purged.
A note on fonts
Nearly all typefaces on Noiz are served from our own servers, so loading a page does not reveal your IP address to any font provider. That is a deliberate choice: most websites load fonts from a third party, and we do not.
Four optional typefaces are the exception: Satoshi, Array, Panchang and Technor. Their license does not permit us to host the files ourselves, so when a creator has chosen one of them for their page, your browser requests that font from Fontshare and Fontshare receives your IP address and browser user agent. No cookie is set and no account is involved. Every other profile, using any other font, contacts nobody.
Those same four are also loaded in your own dashboard, on the screens with a font picker, so each font's name can be shown in the font itself. That request is made by your browser while you are choosing a font, and never by someone visiting your page.
A note on Discord and live status
The Discord row above describes requests made by our servers, not by yours, with one exception we would rather state than bury.
The exception is Discord's images. If a creator shows a Discord server or their Discord profile on their page, the server's icon, the creator's Discord avatar, badges and server tag and, when their live status names a game, that game's picture are loaded by your browser directly from Discord's content delivery network (cdn.discordapp.com). Discord therefore receives your IP address and the usual headers your browser sends, including, depending on your browser's settings, the address of the page you are on, as the page loads, before you interact with anything. No account information of yours is sent, and you do not need a Discord account for this to happen.
Game covers are the same kind of exception. A creator can build a games shelf by picking from a list we keep, and each game's cover art is loaded by your browser from Steam's content delivery network (cdn.cloudflare.steamstatic.com, and shared.akamai.steamstatic.com for newer titles whose art Valve serves from there) as the page renders. Valve therefore receives your IP address and the usual headers, in the same way Discord's CDN does. The art is not copied onto our servers: it belongs to the games' publishers and is served from the store it belongs to. A creator who uploads their own cover instead is not covered by this (that image is in our storage like any other upload), and a page with no games shelf contacts Valve not at all.
Repository cards are the same kind of exception. A creator can show one of their GitHub projects on a page, and the card carries the repository owner's avatar, which your browser loads from github.com as the page renders. GitHub therefore receives your IP address and the usual headers, but not the address of the page you are on, because the request is made without a referrer. Nothing else about the repository is fetched: the name, description, language and star count are typed by the creator, and a page with no repository card contacts GitHub not at all.
Link icons are still copied into our own storage rather than hotlinked. Embeds changed on August 27, 2026: a YouTube or Spotify player used to sit behind a click and now loads with the page, so if a creator has added one, that provider is contacted as the page renders rather than when you press play. Players further down a page are not loaded until you scroll near them.
Discord is not a processor acting on our instructions. It is its own controller for the account you sign in with.
Live status
A creator can choose to show their live Discord status on their Discord card: whether they are online, idle, on do not disturb or offline, what they are playing, streaming or listening to, a custom status they wrote and, if they also choose it, how long ago they went offline. It is off until the creator turns it on in their dashboard, and each of those parts has its own switch.
Discord does not make another user’s status available to a website. It sends it only to a bot that shares a server with that user, so this works through the bot we run in the Noiz Discord server, and only for creators who are members of that server. As a member’s status changes, Discord sends it to the bot. The bot passes on the status of creators who turned the feature on and drops everything else without storing or logging it. It runs on a server we rent from Hetzner Online GmbH in Germany.
For those creators we store the latest status only: the status, the current activity as Discord reports it (its name, up to two lines of detail and when it began), the custom status text and the time the account was last seen online. There is no history. It is deleted when the creator turns the feature off, hides their Discord card, disconnects Discord or deletes their account, and it stops being shown when they leave the server or when our bot has not reported for three minutes. An account set to Invisible in Discord is reported to us as offline. This is part of the service the creator asks for by turning the switch on.
Nothing new is collected about visitors. An older version of this feature used a community-run service called Lanyard until August 2026; Noiz does not contact it any more.
Separately, for creators who switch their Discord card on, we read the account’s badges: HypeSquad, Early Supporter and so on. Those are read from Discord’s own API by our server, using our credentials, once per cache interval rather than once per visitor. The only thing sent is that creator’s own Discord user id. No visitor data is involved: not your IP address, not your user agent, not which profile you were looking at.
What connecting Discord stores
If you connect Discord to your Noiz account, we write four fields to your profile: three read from the OAuth identity you authorized, and one you type in yourself:
discord_user_id: your Discord account's numeric iddiscord_username: your Discord handle, as Discord reports itdiscord_avatar: the address of your Discord avatar as Discord serves it, on cdn.discordapp.com. Accounts connected before August 18, 2026, may still hold the copy we stored back then, until they reconnect.discord_server_id: the invite code of a server you chose to feature, if you featured one. Despite the column's name it holds an invite code, not a server id; we use it to ask Discord for that invite's public details (the server's name, its icon and the member counts Discord attaches to it); the icon itself is loaded by your visitor's browser from Discord's CDN, as the note above says.
We ask Discord only for your identity: id, handle, avatar and email address. We cannot read your messages, your friends, or the list of servers you are in, because we never request the permission to.
Storing is not showing. The Discord card and the server card are off until you enable them; connecting your account publishes nothing on your Noiz page on its own. Disconnecting Discord clears the id, the handle and the avatar address from your profile and sets both display switches back to off, so reconnecting later cannot quietly republish something you had turned off. Deleting your account deletes all of it, on the schedule in Section 10.
The Premium role in our Discord server
Connecting Discord has one effect outside your Noiz page. If your account has Premium and a connected Discord account, and you are a member of the Noiz Discord server, our bot gives you the Premium role there. Other members of that server can see the role, so it shows them that you have Premium. To do this, our bot fetches the Discord ids of Premium accounts from our server every few minutes; it receives those ids and nothing else. The role is removed within a few minutes if you disconnect Discord, if your Premium ends or if you delete your account. If you are not a member of that server, nothing happens.
Card widgets
A creator can add small cards to their page that show something from another service: the weather where they are, their Minecraft name and face, their Roblox status, their Steam profile, their YouTube channel, their TikTok profile, their Twitch channel or their GitHub profile. To fill a card, our server asks that service, using only what the creator gave it: a place, a Minecraft name, a Roblox user ID, the Steam account they signed in with, a YouTube handle, the TikTok account they connected, a Twitch channel name, or a GitHub username. Your browser does not contact these services when you open the page: pictures on the cards are served by Noiz, and nothing about visitors is sent.
- Weather: we find the place in our own copy of the GeoNames list of places (geonames.org, CC BY 4.0), then ask MET Norway, the Norwegian Meteorological Institute, for the forecast at its coordinates. Weather data from MET Norway.
- Minecraft: we ask Mojang, part of Microsoft, for the account and its skin, and keep only the 64 colors of the face.
- Roblox: we ask Roblox for the account’s name, status, followers and current game. The game is shown only when the player’s own Roblox privacy settings allow it.
- Steam: the creator signs in through Steam, which tells us their Steam account number (SteamID64) and nothing else; Steam never shows us their password. We store that number with their Noiz account, and ask Valve’s Steam Web API for the account’s public name, avatar, online status, the game being played, the most played game of the last two weeks with its hours, and the Steam level. What the creator’s Steam privacy settings hide stays hidden. Steam data is used only for the creator’s own card, at their request.
- YouTube: we use YouTube API Services to ask for the channel’s public name, handle, picture and its subscriber, video and view counts. A hidden subscriber count is never shown. YouTube’s data is covered by the Google Privacy Policy.
- TikTok: the creator connects their TikTok account through TikTok’s own sign-in and allows Noiz to read their profile (name, picture, @username, whether it is verified) and its numbers (followers and likes). TikTok gives us an account number for our app and access tokens, which we store encrypted and use only to fill the creator’s own card. The creator can disconnect at any time in the dashboard, which ends our access at TikTok and deletes the account number, the tokens and the card’s data at once; they can also remove our access in TikTok’s own settings.
- Twitch: we use Twitch’s API with Noiz’s own app to ask for the channel’s public name, picture and partner status, and, while it is live, the stream’s title, category and number of viewers. We do not ask for or show its followers, and the creator does not sign in to Twitch for this card.
- GitHub: we use GitHub’s API with Noiz’s own access key to ask for the profile’s public name, username, picture, number of followers and public repositories, and its public contribution calendar for the last year. The creator does not sign in to GitHub for this card.
We store all of this in our database in the European Union (Frankfurt, Germany). We keep the latest answer for each card for a short time, from a few minutes to a day, so the page loads quickly, and we delete it within a day once no card uses it. A YouTube answer is never kept longer than 29 days without being fetched again, and a Twitch answer never longer than 24 hours. A Steam or TikTok account no card uses is deleted within two days, TikTok’s tokens with it, and at once if the creator deletes their account. Pictures are kept by our content delivery network for at most a day.
Finding lyrics
When a creator presses Find lyrics in the dashboard, or adds a Spotify song link, our server asks LRCLIB (lrclib.net), a free community library of song lyrics, for timed lyrics by the song’s title and artist. For a Spotify link it first reads the song’s title, artist and length from Spotify’s public page for that song. It sends nothing else: not the creator’s name, account or address. We do not keep LRCLIB’s answer. To show a Spotify song in noiz’s own player, our server also reads the song’s title, artists, length and cover from that public page, and keeps them in its cache for a day; no visitor data is sent with that request. Lyrics the creator chooses are saved with their song or link, like lyrics they upload.
Links to sub-processor privacy policies:
9. International Data Transfers
Your personal data may be transferred to, stored, and processed in countries outside the European Economic Area (EEA). Our database is in the European Union (Frankfurt, Germany) and uploaded files are stored in Western Europe, but some sub-processors operate globally.
9.1 Transfer Mechanisms
When we transfer your data outside the EEA, we ensure appropriate safeguards are in place:
- EU-US Data Privacy Framework (DPF): For transfers to US companies certified under the EU-US Data Privacy Framework (e.g., Stripe, Google).
- Standard Contractual Clauses (SCCs): EU Commission-approved contractual clauses that provide adequate protection for data transfers.
- Adequacy Decisions: Transfers to countries that the European Commission has determined provide an adequate level of data protection.
- Binding Corporate Rules: Where applicable for multinational service providers.
9.2 Supplementary Measures
In addition to the above safeguards, we implement:
- Encryption in transit (TLS) to every sub-processor
- Data minimization - we only transfer data necessary for the specific purpose
- Regular reviews of our sub-processors' data protection practices
- Contractual requirements for sub-processors to notify us of government access requests
You may request a copy of the safeguards we use for international transfers by contacting privacy@noiz.bio
10. Data Retention
We retain your personal data only for as long as necessary to fulfill the purposes for which it was collected, or as required by law. The table below outlines our retention periods:
| Data Type | Retention Period | Basis |
|---|---|---|
| Account and profile data | Until account deletion + 30 days | Contract performance |
| Analytics data (pseudonymized) | 90 days | Legitimate interest |
| Templates you share | Until you delete your page or account. Removing a template takes it out of the gallery and deletes its files at once; its name, description and settings stay with your page. Pages that applied one keep their copy | Contract performance |
| Your look before you applied a template | 30 days | Contract performance |
| IP address in sign-in logs (full address) | 30 days | Legitimate interest / Security |
| IP digests in abuse limiters | 24 hours to 7 days | Legitimate interest / Security |
| Payment and transaction records, including withdrawals from a purchase | 10 years | Legal obligation (§ 147 AO, § 257 HGB) |
| Sign-in attempts | 30 days | Legitimate interest / Security |
| Records that your password or email address changed, or that an account was deleted, with the addresses involved | 30 days | Legitimate interest / Security |
| Admin access logs | 1 year | Legitimate interest / Security |
| Privacy-banner choice records | 12 months from your choice | Legitimate interest (showing we honored it) |
| Support inquiries | 3 years from receipt | Legitimate interest (§ 195 BGB) |
| Waitlist entries | Deleted 30 days after signups open on November 2, 2026. A name you asked us to hold stays held for you until then; an account you create keeps only what you enter when you sign up | Steps at your request |
| Changes made by AI apps you connected | Until account deletion + 30 days | Contract performance |
| Connections of AI apps (stored at Cloudflare) | Until you disconnect the app or delete your account, or 30 days after it was last used | Contract performance |
| Backup data | 30 days after deletion from production | Business continuity |
10.1 Retention Criteria
When determining retention periods, we consider:
- The nature and sensitivity of the personal data
- The potential risk of harm from unauthorized use or disclosure
- The purposes for which we process the data
- Whether we can achieve those purposes through other means
- Applicable legal, regulatory, tax, accounting, or other requirements
10.2 Deletion Procedures
When data reaches the end of its retention period, or upon valid deletion request, we securely delete the data. Aggregated counts that no longer relate to any person (page views per day, for example) may be kept indefinitely for statistics.
12. Data Security
We implement appropriate technical and organizational security measures to protect your personal information in accordance with GDPR Article 32:
12.1 Technical Measures
- Encryption in Transit: Noiz uses modern TLS encryption for data in transit. Connections currently support TLS 1.2 or later
- Encryption at Rest: Our database and file-storage providers encrypt stored data at rest (AES-256); this is their control, applied to everything we store with them
- Password Security: Passwords are hashed using industry-standard algorithms (never stored in plaintext)
- Two-Factor Authentication: Optional 2FA for enhanced account security
- Secure Payment Processing: Payments handled by Stripe (PCI-DSS Level 1 compliant)
- IP Hashing: Visitor IP addresses are hashed for privacy before storage
12.2 Organizational Measures
- Access Controls: Strict access controls and role-based permissions
- Security Reviews: Internal reviews of the code; the date of the last one is published on our Security page
- Incident Response: If we learn of a breach, we act as Section 13 describes
- Data Minimization: We only collect and retain data necessary for our purposes
12.3 Privacy by Design and Default
In accordance with GDPR Article 25, we implement data protection principles from the design phase of our services:
- Privacy-preserving defaults for all new features
- Data minimization in all collection processes
- Pseudonymization where possible (e.g., IP hashing)
However, no method of transmission over the Internet or electronic storage is 100% secure, and we cannot guarantee absolute security. If you have reason to believe that your interaction with us is no longer secure, please contact us immediately.
13. Data Breach Notification
In accordance with GDPR Articles 33 and 34, we have procedures in place to detect, report, and investigate personal data breaches.
13.1 Notification to Supervisory Authority
If we become aware of a personal data breach that is likely to result in a risk to the rights and freedoms of individuals, we will:
- Notify the relevant supervisory authority within 72 hours of becoming aware of the breach
- Document the breach, its effects, and remedial actions taken
- Provide the authority with all required information as per GDPR Article 33(3)
13.2 Notification to Affected Individuals
If a breach is likely to result in a high risk to your rights and freedoms, we will:
- Notify you without undue delay
- Describe the nature of the breach in clear and plain language
- Provide the name and contact details of our data protection contact
- Describe the likely consequences of the breach
- Describe the measures taken or proposed to address the breach
- Provide recommendations for you to mitigate potential adverse effects
13.3 Our Commitment
We take data security seriously and continuously work to prevent breaches. However, if an incident occurs, we are committed to transparent and timely communication with both authorities and affected users.
14. Your Data Subject Rights (GDPR)
If you are in the European Economic Area, United Kingdom, or Switzerland, you have the following rights under data protection law:
Right of Access (Art. 15)
Request a copy of your personal data we hold. We will provide this in a commonly used electronic format.
Right to Rectification (Art. 16)
Request correction of inaccurate or incomplete personal data. You can also update most information directly through your account settings.
Right to Erasure (Art. 17)
Request deletion of your personal data ("right to be forgotten"). This applies when the data is no longer necessary, you withdraw consent, or you object to processing.
Right to Restriction (Art. 18)
Request restriction of processing while we verify the accuracy of your data or the legitimacy of our processing.
Right to Data Portability (Art. 20)
Request transfer of your data in a structured, commonly used, machine-readable format (e.g., JSON, CSV) to another service provider.
Right to Object (Art. 21)
Object to processing based on legitimate interests or direct marketing. We will stop processing unless we have compelling legitimate grounds.
Right to Withdraw Consent (Art. 7)
Withdraw consent at any time where processing is based on consent. This does not affect the lawfulness of processing before withdrawal.
Right Not to be Subject to Automated Decisions (Art. 22)
Not be subject to decisions based solely on automated processing that produce legal or similarly significant effects (see Section 15).
14.1 How to Exercise Your Rights
To submit a data subject request:
- Email us at privacy@noiz.bio with your request
- Include your account email address for identification
- Specify which right(s) you wish to exercise
- We may ask for additional information to verify your identity
14.2 Response Timeframe
- We will respond to your request within 30 days
- For complex requests, we may extend this by up to 60 additional days (we will inform you)
- Requests are processed free of charge, except for manifestly unfounded or excessive requests
14.3 Right to Lodge a Complaint
If you are not satisfied with how we handle your request, you have the right to lodge a complaint with a supervisory authority (see Section 17).
15. Automated Decision-Making
In accordance with GDPR Article 22, we inform you about any automated decision-making processes that may affect you:
Our Position
Noiz does NOT use automated decision-making, including profiling, that produces legal effects or similarly significantly affects you. Some checks are automatic, listed in 15.1, and you can ask for a person to review any of them.
15.1 Automated Processing We Do Use
We use automated processing for the following non-consequential purposes:
- Content Filtering: An automatic word filter refuses usernames that contain slurs and hides such words from public pages
- Sign-up checks: A sign-up is refused automatically when another Noiz account uses the same inbox, or when the email address's domain cannot receive mail
- Spam Detection: Automated detection of suspicious activity patterns (human review before account restrictions)
- Analytics: Automated aggregation of usage statistics (no individual decisions made)
15.2 Your Rights
If you believe any automated processing has unfairly affected you, you have the right to:
- Request human intervention in any decision
- Express your point of view
- Contest any decision made
16. Children's Privacy
The Service is not intended for users under 13 years of age. We do not knowingly collect personal information from children under 13.
16.1 Age Requirements
- Minimum Age: 13 years old (worldwide)
- EU Users: In certain EU member states, users between 13-16 may require parental consent
- COPPA Compliance: We comply with the Children's Online Privacy Protection Act for US users
16.2 If We Discover Underage Users
If we become aware that we have collected personal information from a child under the applicable minimum age without proper consent:
- We will promptly delete that information
- We will terminate the associated account
- We will notify the parent or guardian if contact information is available
If you believe a child has provided us with personal information, please contact us immediately at privacy@noiz.bio
17. California Privacy Rights (CCPA/CPRA)
If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA):
17.1 Your California Rights
- Right to Know: Request information about the categories and specific pieces of personal information we have collected
- Right to Delete: Request deletion of your personal information (subject to certain exceptions)
- Right to Correct: Request correction of inaccurate personal information
- Right to Opt-Out: Opt out of the sale or sharing of personal information
- Right to Non-Discrimination: Not receive discriminatory treatment for exercising your rights
- Right to Limit Use: Limit the use and disclosure of sensitive personal information
17.2 "Do Not Sell My Personal Information"
Noiz does NOT sell your personal information. We do not sell, rent, or trade your personal data to third parties for monetary or other valuable consideration. We do not share your information for cross-context behavioral advertising.
17.3 Shine the Light
California Civil Code Section 1798.83 permits California residents to request information regarding disclosure of personal information to third parties for direct marketing purposes. We do not disclose personal information to third parties for their direct marketing purposes.
17.4 Removal of Content Posted as a Minor
If you are a California resident under 18 and have publicly posted content on our Service, you may request removal of that content by contacting us. Note that removal may not ensure complete removal if the content has been reposted by others.
18. Supervisory Authority
If you are located in the European Economic Area and believe we have not adequately addressed your data protection concerns, you have the right to lodge a complaint with your local data protection supervisory authority.
18.1 German Supervisory Authority
As we are based in Baden-Württemberg, Germany, our lead supervisory authority is:
Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg
Lautenschlagerstraße 20
70173 Stuttgart
Germany
Phone: +49 711 615541-0
18.2 Other EU/EEA Authorities
You may also lodge a complaint with the supervisory authority in your country of residence. A list of EU data protection authorities can be found at: European Data Protection Board
We encourage you to contact us first at privacy@noiz.bio so we can try to resolve your concerns directly before you escalate to a supervisory authority.
19. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors.
19.1 How We Communicate Changes
- We will post the updated policy on this page with a new "Last updated" date
- For material changes, we will provide at least 30 days' advance notice via email to your registered address
- Material changes include: new categories of data collection, new processing purposes, changes to data sharing practices, or changes to your rights
19.2 Your Continued Use
Your continued use of the Service after the effective date of any changes constitutes your acceptance of the updated policy. If you do not agree with the changes, you should discontinue use of the Service and delete your account.
We encourage you to review this Privacy Policy periodically to stay informed about our data practices.
20. Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us:
Noiz
Inhaber: Fabian Schneidruck
Leopoldplatz 13
76437 Rastatt
Germany
USt-IdNr.: DE367705746
Contact Channels
Privacy Inquiries: privacy@noiz.bio
Data Subject Requests: privacy@noiz.bio
Legal Matters: legal@noiz.bio
General Support: support@noiz.bio
Response Timeframe: We aim to respond to all privacy-related inquiries within 30 days. For data subject requests, we will respond within the timeframes required by applicable law.