1. Controller
The controller within the meaning of Art. 4 (7) GDPR is:
Crela UG (haftungsbeschränkt)
represented by the managing director Felix Bonetsmüller
Schmerlenstraße 5
83059 Kolbermoor
Germany
Email: contact@crela.io
Phone: +49 8031 2821467
2. Data Protection Officer
A data protection officer is not appointed because the statutory requirements (e.g. § 38 BDSG) are not met. For data protection questions, please contact: privacy@crela.io.
3. Definitions
This Privacy Policy uses the terms of the GDPR, in particular:
- Personal Data: any information relating to an identified or identifiable natural person.
- Processing: any operation involving personal data (collecting, storing, transmitting, deleting, etc.).
- Controller: the entity that decides on purposes and means of processing.
- Processor: a service provider that processes data on instructions.
4. Legal Bases
Processing of personal data takes place on the basis of one of the following provisions:
- Art. 6 (1) (a) GDPR - consent
- Art. 6 (1) (b) GDPR - contract performance or pre-contractual measures
- Art. 6 (1) (c) GDPR - legal obligation (e.g. commercial and tax retention obligations, EU sanctions, the Digital Services Act)
- Art. 6 (1) (f) GDPR - legitimate interests
5. Processing Operations in Detail
5.1 Provision of the Website / Server Logs
When accessing the Crela website, the following data is technically collected:
- IP address
- date and time of access
- accessed URL
- HTTP referrer
- user agent (browser, operating system)
Purpose: Delivery of the website, security analyses (defense against attacks).
Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in security and stability).
Storage: Access logs are generated by our web server and stored within the server environment of our hosting provider (netcup, Germany). IP addresses are recorded in full and are not automatically shortened. Each service on our servers keeps at most 100 MB of logs; once this limit is reached, the oldest entries are overwritten automatically. For the web server, this means that access logs are kept for less than one day at current traffic (measured on 9 November 2026). We do not copy these logs to any other place.
5.2 User Account
Upon registration, we collect:
- email address
- password (hashed, never stored in plaintext)
- display name / username
- optionally profile picture and biographical information (voluntary)
If you sign in with GitHub or Google, you are redirected to that provider. It confirms your identity to us and passes on your email address, your name and, where available, your profile picture. GitHub, Inc. and Google Ireland Limited process your login with them as independent controllers under their own privacy policies.
For each sign-in session, our authentication service (Supabase, section 6) records the IP address and the user agent of your browser or of the Crela Launcher, when the session was created and when it was last used. If you use two-factor authentication, it also records the IP address of each confirmation with your second factor. Supabase also logs the requests to its service, including sign-in events, with the IP address.
Purpose: keeping you signed in, protecting your account against misuse.
Legal basis: Art. 6 (1) (b) and (f) GDPR.
Retention period: session records until you sign out, session and second-factor records at the latest until your account is deleted; Supabase keeps the request logs for 7 days.
Purpose: Authentication, provision of platform features (purchases, reviews, etc.).
Legal basis: Art. 6 (1) (b) GDPR (contract performance).
Retention period: until your account is deleted. You can delete your account at any time under Settings (Delete account), or ask us to delete it by writing to privacy@crela.io from the email address of your account; we then delete it within one month (Art. 12 (3) GDPR). Deleting the account removes your sign-in data (email address, password and linked GitHub or Google sign-in), your profile and the reviews and questions you posted. Data we must keep by law, in particular records of purchases and payouts and the tax records described in section 5.3, stays linked to a placeholder that contains no sign-in data. We use it only to meet these obligations and delete it after the retention period has ended, unless a tax assessment for the period concerned is still open (§ 147 (3) sentence 5 AO). Tools a Creator sold stay available to their buyers but are taken off the market; unsold tools are deleted.
If you use the Crela Launcher, we store for each connected device the device name, when it was connected and last used, and whether you signed it out. We email you when a new device connects, and you can sign devices out under Settings, Devices.
Purpose: protecting your account and your downloads.
Legal basis: Art. 6 (1) (b) GDPR.
Retention period: until you sign the device out or delete your account; signed-out devices are deleted after 30 days.
We store your acceptance of our terms (which version, when) for as long as the contract exists and for 3 years after it ends, so that we can prove the agreed terms (limitation period, § 195 BGB).
Legal basis: Art. 6 (1) (f) GDPR.
5.3 Purchases and Payment Data
Upon a purchase, we collect:
- name and billing address (for invoicing, VAT calculation and sanctions screening, section 5.9)
- email address
- purchased tools, purchase date, purchase price, VAT rate and VAT amount
- your VAT ID, if you enter one at checkout, and whether VAT was charged on the purchase
- the country in which your card was issued and the country of your IP address, as evidence of where you live (see "Evidence of your location" below)
- payment status (no direct storage of credit card data - exclusively processed by Stripe)
Purpose: Contract performance, invoicing, fulfillment of commercial and tax obligations.
Legal basis: Art. 6 (1) (b) and (c) GDPR.
Recipients: Stripe (payment processing and VAT calculation), tax advisor and tax authorities (where required).
Retention period: Records of purchases, refunds, chargebacks and payouts are part of our books and tax records and are kept for 10 years (§ 147 (1) No. 1 and (3) AO, § 22 (1) UStG). Invoices and credit notes are kept for 8 years (§ 14b UStG, § 147 (3) AO). The periods start at the end of the calendar year in which the record was made. They do not end as long as a tax assessment period for which the record is relevant is still open (§ 147 (3) sentence 5 AO). Withdrawal declarations (your name, email address, the declaration and the time we received it) and return requests are kept like the records of the purchase; a withdrawn or returned purchase stays in our records for the same period.
Chargebacks and fraud warnings: If your bank warns Stripe of possible card fraud, we may refund the purchase and withdraw the license. If you dispute a payment with your bank (chargeback), we may send Stripe evidence to answer it: the purchased tools, the time of purchase, your acceptance of the terms and of the withdrawal waiver, the times of downloads and license activations (with the platform, no device identifiers) and your email address. Stripe passes the evidence on to the card network and your bank.
Legal basis: Art. 6 (1) (f) GDPR (our legitimate interest in preventing fraud and in defending against unjustified chargebacks).
Tax records. For each sale, refund and chargeback we record the tax-relevant details as they were at that moment, so that later changes to your account do not change them: the tools and their price, the VAT amount and the VAT rate reported by Stripe, the date of supply and of payment, the country of your billing address, the country of residence you gave us (if any), the VAT ID you entered at checkout (if any), the invoice or credit note number, the related Stripe identifiers and the message in which Stripe reported the purchase to us, which contains your name, email address and billing address, but no phone number and no card details. These records cannot be changed afterwards; a correction is added as a new record that refers to the old one. We use them only to meet our tax and accounting obligations, never for marketing, for statistics about individual persons or for profiling. Access is limited to our managing director, a tax advisor if we engage one, and, during a tax audit, the tax auditors.
Legal basis: Art. 6 (1) (c) GDPR in conjunction with § 147 AO and § 22 UStG.
Retention period: 10 years, as described above.
Evidence of your location. VAT on software we sell depends on the country where the buyer lives. EU law lets us determine that country from pieces of evidence that do not contradict each other (Art. 24b and 24f Implementing Regulation (EU) No 282/2011). In addition to the country of your billing address, we therefore record with each paid purchase:
- the country in which your card was issued, as reported by Stripe; if you pay with Link, the country of the card or bank account behind it; for SEPA direct debit, the country of your bank. For other payment methods Stripe reports no country and we record none;
- the country of the IP address from which you started the payment. We determine it on our own server from the lists of the regional internet registries and record only the country, the name of the list and its date.
We do not store your IP address for this purpose, neither in full nor shortened. We pass only the country to Stripe with the checkout, so that it can be matched to your purchase. If these countries differ, we mark the purchase and check it later; delivery is not delayed. We also use these countries for sanctions screening (section 5.9).
Legal basis: Art. 6 (1) (c) GDPR in conjunction with Art. 24b and 24f Implementing Regulation (EU) No 282/2011 and § 22 UStG.
Retention period: 10 years, as described above.
Before your first paid purchase we ask once for your country of residence and save it with your account. If you claim a free tool from an IP address registered in Ukraine, we also ask for it, unless we already have it. If you choose Ukraine, we also ask whether you live in Crimea, Sevastopol or a part of the Donetsk, Luhansk, Zaporizhzhia or Kherson regions occupied by Russia, and save your answer. We use both to check whether EU sanctions allow us to provide software to you (section 5.9). We use your country of residence to check, before you pay, whether we can sell paid tools to your country under tax rules: we sell only to countries we have checked, and when our sales to consumers in other EU countries approach the threshold above which VAT of their country applies, we pause sales to them for a while. In addition, from 11 December 2027, if your cart contains software whose manufacturer has not yet provided the documents required by the EU Cyber Resilience Act, we offer such software only outside the EU.
Legal basis: Art. 6 (1) (c) GDPR.
Retention period: in your account until you change it or delete your account. With each paid purchase we also copy your country of residence, but not your answer about the occupied regions, into our tax records (see "Tax records" above), where it is kept for 10 years.
5.4 Tool Submissions (for Creators)
Upon a tool submission, we process:
- identity and contact details of the Creator (legal name, address and country, email) and the tax details we need for paid tools and payouts: legal form, whether you sell as a business, whether you use a small business exemption and its number, tax number, VAT ID, the kind of work your tools are (software, games or design work), whether you have a permanent establishment in Germany, if you live outside Germany whether you declare that you are the beneficial owner of the payments, if you sell as a sole trader or freelancer and live outside Germany your form of address, first and last name and your date of birth if you live in another EU member state (German tax law requires us to state these details when we report the tax withheld from your payouts to the German Federal Central Tax Office, § 50a EStG, § 73e EStDV), if you live in the United States the details of your Form W-9 (your taxpayer identification number, whether it is an SSN, ITIN or EIN, your federal tax classification and when you certified them; we show only the last four digits of the number in your account), and whether you are a shareholder or managing director of Crela UG (haftungsbeschränkt) or related to one. Before each payout we compare your tax country with the country of your Stripe account. We check a VAT ID from another EU country with the German Federal Central Tax Office (BZSt), which compares your name and address with the VAT register (§ 18e UStG), and a German VAT ID with the EU VIES service; we keep the result of each check
- the submitted software files (binary, symbol file)
- metadata of the submission (title, description, platform, framework, version, age rating of games)
- automatically generated pipeline findings (security findings) and the evaluation by an AI model
- documents for the EU Cyber Resilience Act that you provide for a tool: its category, a link to your declaration of conformity and a contact for vulnerability reports (shown publicly), and uploaded documents such as the declaration, technical documentation or certificates (not public; we show them to market surveillance authorities on request)
We need the address to issue credit notes and keep records of your payouts, for tax purposes (e.g. the VAT treatment of our commission) and to be able to name you as the manufacturer of your tools to authorities where product safety law requires it.
Of your manufacturer details, only the name and, if you provide it, the website are shown publicly on the product pages of your tools on crela.io and in the Crela Launcher. Your postal address, its country and your email address are not public. We keep them to be able to name the manufacturer of a tool to authorities and to a person who claims damage from it, where the law requires this (Art. 8 (3) Directive (EU) 2024/2853, Art. 23 Regulation (EU) 2024/2847, Regulation (EU) 2023/988), and disclose them only in those cases. Instead of your home address you can give a business or c/o address at which you can receive mail. If the address is outside the EU, the product page names Crela as the responsible person in the EU, without naming the country. Legal basis: Art. 6 (1) (c) and (f) GDPR.
For the AI evaluation, the findings and parts of the submitted software and its metadata are sent to the AI providers listed in section 6. They can contain personal data of the Creator, for example a name in the metadata or a user name in a file path.
Purpose: Contract performance, provision of the tool to end users, security review, statutory obligations (CRA, DSA, tax law).
Legal basis: Art. 6 (1) (b) and (c) GDPR.
Retention period:
- Tool files, pipeline findings, review reports, SBOMs and screenshots of the test run of a rejected build: 90 days after the rejection;
- the same for an approved build: as long as it is the current version of the tool (also for buyers after the tool was taken off the market), and 5 years after a newer version replaced it;
- Symbol files (
tool_files.file_type='symbols'): 30 days from pipeline run - automatic deletion via cron, since build paths in symbols often contain Windows usernames (GDPR data minimization); - Manufacturer details: while your account exists your name and website are shown with your tools; if you delete your account, we keep your manufacturer details for 10 years, not publicly, because we must be able to name the manufacturer of a product sold through Crela (Art. 23 Regulation (EU) 2024/2847, Art. 8 Directive (EU) 2024/2853); legal basis Art. 6 (1) (c) and (f) GDPR;
- Documents for the EU Cyber Resilience Act: as long as the tool exists on Crela. From 11 December 2027, when the Act applies: if a tool that was offered on Crela is deleted, also together with your account, we keep its documents for 10 years, or until the end of the tool's security support period if that is later, not publicly, because we must be able to present them to market surveillance authorities (Art. 19 Regulation (EU) 2024/2847); before that date, and for a tool that was never offered on Crela, the documents are deleted with the tool; legal basis Art. 6 (1) (b), (c) and (f) GDPR;
- Your tax details as they were when your share of a sale was recorded (country, tax status, VAT ID with the result of its check, basis and amount of your share): with the records of the payout, 10 years (section 5.3); earlier versions of your tax details are kept as well, because each payout refers to the version that applied;
- Self-billing invoices (Gutschrift) that we issue to you for your supplies to Crela, with the version and date of your self-billing agreement: 8 years from the end of the year of issue (§ 147 AO);
- Records of payouts and credit notes: see section 5.3.
5.5 Creator Payouts (Stripe Connect)
To receive payouts, Creators set up an account with Stripe (Stripe Connect Express). We pass your email address and your Crela user ID to Stripe. Stripe collects the data it needs to verify your identity and to pay you (e.g. name, date of birth, address, identity document, bank account) directly from you and processes it as an independent controller under its own privacy policy (stripe.com/privacy). For accounts in the EEA, the responsible Stripe company is located in Ireland; data is also processed by Stripe, LLC in the USA (EU-US Data Privacy Framework). We receive from Stripe your account ID, whether payouts are enabled for your account and the status of each payout. If you delete your Crela account, we close your Stripe account only after your last credit note has been sent and no payment can be reclaimed any more.
If you live outside Germany, German law requires us to withhold tax from your payouts (§ 50a EStG). For each payout we record your name, address and country, the amount, the tax rate and why it applies, the tax withheld and the date of payment (§ 73d EStDV), and we report these details every quarter to the German Federal Central Tax Office (BZSt), which may use them to inform the tax authorities of your country. On request we give you a certificate of the tax withheld. Legal basis: Art. 6 (1) (c) GDPR. We keep these records for 10 years.
If you live in the United States, US tax law requires us as the payer to report your payouts to the US Internal Revenue Service (IRS). Once a year we send the IRS and you a Form 1099 with your name, address, taxpayer identification number and the amount paid to you in that year. Legal basis: Art. 6 (1) (f) GDPR (our legitimate interest in meeting the US reporting obligation that applies to our payments to you and avoiding penalties under it). The IRS is a US public authority; there is no adequacy decision for this transfer, which is necessary to perform our contract with you (Art. 49 (1) (b) GDPR). We keep these records with the records of your payouts for 10 years.
Purpose: Payment of your share of sales.
Legal basis: Art. 6 (1) (b) GDPR; Stripe verifies your identity to meet its own legal obligations (anti-money laundering).
Retention period: see section 5.3.
5.6 Reports of Illegal Content (Notice and Action)
When you report a tool, a review or a question as illegal (button "Report"), we process:
- the reason category and your explanation
- the reported content and its wording at the time of the report
- optionally your name and email address (if you are signed in, we use your account and its email address)
- your statement that the report is made in good faith
We confirm receipt and inform you of our decision. If we act against the content, we inform the person who posted it of our decision and the reasons (Art. 17 DSA); we do not pass on your name or email address.
Purpose: Fulfillment of reporting obligations under Art. 16 DSA, protection against illegal content.
Legal basis: Art. 6 (1) (c) GDPR (legal obligation) and (f) GDPR (legitimate interest in platform safety).
Retention period: 5 years (preservation of evidence in case of official requests for information or legal proceedings).
5.7 Build Delivery
Upon each download by an end user, the Crela Launcher processes:
- IP address (for delivery)
- purchased tool ID
- build hash manifest (for integrity verification)
Purpose: Technical delivery, protection against tampering.
Legal basis: Art. 6 (1) (b) GDPR.
Retention period: Delivery logs 30 days, then deletion.
When you start a tool from the Crela Launcher, we store how long it ran, how it ended (exit code) and its version, linked to your account. Creators only see the average use of their tools, never individual records.
Purpose: showing Creators how their tools are used, finding tools that crash.
Legal basis: Art. 6 (1) (f) GDPR.
Retention period: 12 months.
Age signal: At its first start, at most once a day after that and at each download, the Crela Launcher asks the operating system of your device for the age bracket of its primary user (under 13, 13 to 15, 16 or 17, 18 or older), where the operating system offers one (currently Windows 11 for Microsoft accounts). The launcher keeps only the age bracket and the time of the request on your device (encrypted on Windows) and passes the age bracket to each tool you start from it. Crela does not receive the age bracket. The Creator of a tool that reads it decides how it is used and is responsible for that.
Purpose: compliance with California's Digital Age Assurance Act (California Civil Code §§ 1798.500 to 1798.505), which requires app stores to request this signal and to pass it to developers.
Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in complying with this law).
Retention period: until the next request replaces it, or until you use "Remove all data" in the launcher.
5.8 License Activation
To activate purchased tools, Crela operates its own license system on its own infrastructure. No license or activation data is transmitted to any third-party license provider. When a tool is activated on a device, the following is processed:
- license key
- device fingerprint (a hash of hardware characteristics; no directly identifying data)
Purpose: License management, protection against unauthorized use.
Legal basis: Art. 6 (1) (b) GDPR.
Retention period: until license termination.
5.9 Sanctions Screening
EU sanctions prohibit us from providing software to persons in certain countries and regions (currently Russia, Belarus, Iran, North Korea and the regions of Ukraine occupied by Russia). When you buy or claim a tool, download, update or activate it, or update the Crela Launcher, we determine the country of your IP address from a list of the regional internet registries that is kept on our own server. The IP address is not stored for this purpose and not passed on; if a request is blocked, we record only the country and the requested page (section 5.13). For paid purchases, the country of your IP address is also recorded as tax evidence (section 5.3). When you buy, we also check the country and region of your billing address and the country of your card; purchases with a billing address in a sanctioned country or region or with a card from a sanctioned country are refunded, and the payment and the refund are recorded in our tax records (section 5.3). When you claim a free tool, we also check the country of residence you gave us, if any, and, for Ukraine, your answer whether you live in an occupied region (section 5.3); if you claim from an IP address registered in Ukraine, we ask for both first. If either points to a sanctioned country or region, you cannot claim the tool.
EU sanctions also prohibit us from making funds available to listed persons. If you are a Creator, we therefore check your legal name from your tax profile against the consolidated EU financial sanctions list, when you save your tax profile and before each payout. If the check shows a possible match, we hold your payouts and a person at Crela reviews the match, if necessary using further details from your tax profile or your Stripe account; we do not reject you automatically. We keep a record of each check (the name as checked, the date, the version of the list and the result) for 5 years. Legal basis: Art. 6 (1) (c) GDPR in conjunction with Regulation (EU) No 269/2014 and the other EU financial sanctions regulations.
Purpose: Compliance with EU sanctions.
Legal basis: Art. 6 (1) (c) GDPR in conjunction with Regulations (EU) No 833/2014, 765/2006, 692/2014, 267/2012, 2017/1509 and 2022/263.
Retention period: The billing address and the country of your card are kept with the purchase or the refund (section 5.3). If we refund a purchase because of sanctions or missing documents under the EU Cyber Resilience Act, the message in which Stripe reported the payment (with your name, email address and billing address) stays in our tax records for 10 years (section 5.3).
5.10 Human Review Requests
If our review pipeline rejected your build or paused sales of your tool automatically (section 11), you can use "Request human review" in your Creator dashboard. We process your request, your messages and our decision in a conversation in your dashboard and, if we lift a sales pause, who lifted it, when and why.
Purpose: Human review of automated decisions.
Legal basis: Art. 6 (1) (b) and (c) GDPR, Art. 22 (3) GDPR.
Retention period: until 6 months after the conversation was marked resolved, at the latest until your Creator account is deleted.
5.11 Email Communication
When you contact us, we process the data transmitted to handle your inquiry. Emails to our addresses (@crela.io) are forwarded by Cloudflare (Email Routing) to a mailbox at Google (Gmail, Google Ireland Limited), where we read and answer them. Emails we send from the platform (e.g. purchase confirmations) are sent via Resend.
Legal basis: Art. 6 (1) (b) GDPR (pre-contractual) or (f) GDPR.
Retention period: until conclusive handling + 6 months, unless statutory retention obligations apply. Emails and messages on the platform between you and us that concern an invoice, a payment, a refund, a credit note or a payout are business letters under tax law. We keep them for 6 years from the end of the calendar year in which they were sent or received (§ 147 (1) Nos. 2 and 3, (3) AO), also if you delete your account. We mark such conversations on the platform; all other messages on the platform (support conversations with a Creator or with us) are deleted 6 months after the conversation was marked resolved. Conversations about a return or a report of illegal content are kept as long as the return or the report.
5.12 Cookies and Similar Technologies
The Crela website stores on your device only what is technically necessary for the functions you use. We do not use advertising, marketing or cross-site tracking cookies, and our reach measurement (section 5.14) stores nothing on your device.
Cookies:
crela_csrf: a random value that protects forms and requests against forgery by other websites. It is set on your first visit and kept for one year.- Cookies whose names begin with
sb-: your sign-in session. They are set when you sign in and removed when you sign out; without a visit they expire after 400 days.
Entries in the local storage of your browser:
crela-consent-v1: that you have seen the cookie notice, in which version and when. It stays until you clear your browser data.crela.prelaunch-notice: which version of the pre-launch notice you have closed. It stays until you clear your browser data.crela_tool_draft: for Creators, the draft of a tool form that was not submitted yet. It is removed when you submit the form.crela-buyer-terms-later(session storage): that you chose "later" in the notice about new terms. It is removed when you close the tab.
These entries stay in your browser; only the cookies are sent to our server. Payments are made on Stripe's own website, where Stripe sets its own cookies under its privacy policy (stripe.com/privacy). For embedded videos see section 5.15.
Legal basis: § 25 (2) No. 2 TDDDG (technically essential), no consent required.
5.13 Error Reports
To find and fix errors, the website, our servers and the Crela Launcher record error messages: the error text, the page address without query parameters, the user agent of your browser and technical details of the error. They can contain technical identifiers, for example the ID of a tool or an account the error relates to. Your IP address is not stored with them. In the Crela Launcher you can turn error reports off under Settings, "Send error reports to Crela"; the log file on your computer is not sent. Error reports are not our record of payments: if we refund a payment because of sanctions or missing documents under the EU Cyber Resilience Act, the payment and the refund are recorded in our tax records (section 5.3).
Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in a working service).
Retention period: 30 days, then automatic deletion.
5.14 Reach Measurement (Umami)
To understand how our website is used and to improve it, we count page views with Umami, a web analytics tool that runs on our own server. No analytics data is shared with any third party.
No measurement script runs in your browser. We set no cookies for this, store nothing on your device and read nothing from it. When your browser requests a page, our server passes on to Umami what the browser sends with every request: the address of the page without query parameters, the referrer (the page you came from, also without query parameters), the language setting of your browser, the user agent and your IP address. From the user agent Umami derives your browser, operating system and device type, and from your IP address your country, region and city. The IP address itself is not stored.
Umami stores one record for each visit and each page view, with the time. Records of the same visitor are linked by an identifier that Umami calculates from the IP address, the user agent and a secret value that changes every month. The identifier stays the same within one calendar month and is a different one in the next; the IP address cannot be read from it. These records are pseudonymous: they contain neither your name nor your account nor your IP address, and we do not link them to your account. We use them only for statistics about all visitors.
If your browser sends the "Do Not Track" or the "Global Privacy Control" signal, we do not count your page views. This is how you can exercise your right to object (Art. 21 GDPR); because the records contain no name and no account, we cannot find the records of a single person afterwards.
Purpose: reach and performance analysis.
Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in understanding and improving the reach and performance of our website). Because nothing is stored on your device and nothing is read from it, § 25 TDDDG does not apply.
Retention period: the records are deleted after 12 months.
5.15 Embedded Videos
Product pages can contain YouTube videos chosen by the Creator. The video is loaded only when you click on it, from the domain youtube-nocookie.com. YouTube (Google Ireland Limited) then receives your IP address and the page you are on and can store information on your device.
Legal basis: your consent by clicking (Art. 6 (1) (a) GDPR, § 25 (1) TDDDG).
5.16 Backups
We back up our database so that data is not lost: our database provider Supabase daily (the last 7 days are kept), our server every 6 hours (7 days are kept) and once a day to a computer of our managing director in Germany (the last 7 copies are kept). Data deleted in the platform disappears from the backups after these periods.
Legal basis: Art. 6 (1) (f) GDPR and Art. 32 GDPR (security of processing).
6. Recipients / Processors
We use the following processors. Unless noted otherwise, they process personal data on our behalf under a data processing agreement pursuant to Art. 28 GDPR:
| Service | Location | Purpose | Third-country safeguard |
|---|---|---|---|
| Supabase (contracting party Supabase Pte. Ltd., Singapore) | Data stored in the EU (Ireland); access from outside the EU (Singapore, USA) possible | Database, authentication | SCC |
| Cloudflare, Inc. | USA, global network | Object storage (R2) and delivery of media.crela.io, DNS, forwarding of emails to our addresses | EU-US DPF, SCC |
| Stripe (Stripe companies in Ireland, Stripe, LLC in the USA) | Ireland, USA | Payment processing, VAT calculation, Creator payouts (see also section 5.5) | EU-US DPF, SCC |
| Anthropic, PBC | USA | AI evaluation in the review pipeline | SCC |
| OpenRouter, Inc. | USA | AI gateway for the review pipeline (failover if Anthropic cannot be reached directly) | SCC |
| Resend, Inc. | USA | Sending transactional emails | EU-US DPF, SCC |
| netcup GmbH | Germany | Server hosting (web and worker) | EU-based |
Other recipients:
| Recipient | Role | Data and purpose | Third-country safeguard |
|---|---|---|---|
| European Commission (VIES) and the tax authority of the member state concerned | Public authority | German VAT ID of business Creators, to check it (Art. 6 (1) (c) GDPR) | EU-based |
| Federal Central Tax Office (BZSt), for VAT ID checks | Public authority | VAT ID of business Creators from other EU countries with their name and address, to confirm them (§ 18e UStG; Art. 6 (1) (c) GDPR) | EU-based |
| Google Ireland Limited (Gmail) | Mailbox provider under its own terms | Emails sent to our addresses (section 5.11) | EU-US DPF for transfers to Google LLC |
| Stripe | Independent controller | Identity verification of Creators, fraud prevention (section 5.5) | EU-US DPF |
| GitHub, Inc.; Google Ireland Limited | Independent controllers | Sign-in with GitHub or Google, if you choose it (section 5.2) | - |
| Tax office responsible for Crela (Finanzamt), Federal Central Tax Office (BZSt) | Public authorities | VAT and tax returns; on request or in a tax audit, records of individual purchases and payouts (Art. 6 (1) (c) GDPR, § 147 (6) AO) | EU-based |
| US Internal Revenue Service (IRS) | Public authority | Form 1099 for Creators living in the United States: name, address, taxpayer identification number and amount paid (section 5.5; Art. 6 (1) (f) GDPR) | Art. 49 (1) (b) GDPR |
| Tax advisor | Recipient bound to professional secrecy, if we engage one | Bookkeeping and tax returns | EU-based |
| Other authorities | Recipients where required by law | Official requests | EU-based |
The following services receive no personal data from us: the review pipeline sends them only file hashes, names and versions of software components or web addresses found in submitted software, or fetches public data from them: OSV.dev (Google), the CISA catalog of known exploited vulnerabilities, MalwareBazaar and URLhaus (abuse.ch, Switzerland), and the reference exchange rates of the European Central Bank.
7. Transfers to Third Countries
Where personal data is transferred to recipients outside the EU/EEA, this is done only:
- to recipients in countries with an adequacy decision (Art. 45 GDPR);
- to recipients in the USA who are certified under the EU-US Data Privacy Framework (EU-US DPF; adequacy decision (EU) 2023/1795);
- on the basis of the EU Standard Contractual Clauses (SCC, Art. 46 (2) (c) GDPR, decision (EU) 2021/914) in the data processing agreement of the provider;
- with explicit consent of the data subject (Art. 49 (1) (a) GDPR).
The safeguard for each recipient is shown in section 6. We check the DPF certification of our US providers regularly; for providers listed with both, the SCC continue to apply if the DPF ceases to apply.
8. Data Subject Rights
You have the following rights against Crela:
- Right of access (Art. 15 GDPR)
- Right to rectification (Art. 16 GDPR)
- Right to erasure (Art. 17 GDPR)
- Right to restriction of processing (Art. 18 GDPR)
- Right to data portability (Art. 20 GDPR)
- Right to object (Art. 21 GDPR)
- Right to withdraw consent (Art. 7 (3) GDPR) - withdrawal takes effect for the future
- Rights regarding automated decisions (Art. 22 GDPR, see section 11)
Where we must keep data by law (sections 5.3, 5.4 and 5.11), we cannot erase it before the retention period ends (Art. 17 (3) (b) GDPR). Until then we use it only to meet these obligations; your right of access remains.
Please direct inquiries to privacy@crela.io. Crela will process inquiries without delay, no later than within one month (Art. 12 (3) GDPR).
Users in New Zealand
If you are in New Zealand, the Privacy Act 2020 applies to us in addition to the GDPR. Our privacy officer is our managing director, reachable at privacy@crela.io. You can ask us for access to and correction of your personal information. If a privacy breach is likely to cause serious harm, we notify the Privacy Commissioner and you. You can also complain to the New Zealand Privacy Commissioner.
Users in Singapore
If you are in Singapore, the Personal Data Protection Act 2012 applies to us in addition to the GDPR. Our data protection officer is our managing director, reachable at privacy@crela.io. You can ask for access to and correction of your personal data and withdraw your consent. We notify the Personal Data Protection Commission of a notifiable data breach within three days after assessing it, and you where the law requires it.
Users in Japan
If you are in Japan, the Act on the Protection of Personal Information (APPI) applies to us in addition to the GDPR. The controller, its address and its representative are named in section 1, the purposes of use in section 5. You can ask us to notify you of the purposes, to disclose your data (also electronically), to correct or delete it, to stop using it or to stop providing it to third parties, by writing to privacy@crela.io; we charge no fee. Complaints go to the same address. We handle personal data in Germany, other EU/EEA states and the United States, and we apply our security measures after understanding the data protection systems of these countries. The Personal Information Protection Commission recognises the EU/EEA and the United Kingdom as having equivalent protection. Our service providers in the United States (section 6) are bound by contracts that ensure equivalent measures (APPI Article 28 (1)); on request we give you information on these measures (Article 28 (3)).
Users in Hong Kong
If you are in Hong Kong, you can ask us under the Personal Data (Privacy) Ordinance (Cap. 486) for access to and correction of your personal data by writing to privacy@crela.io; for an access request we may charge a fee that is not excessive. We do not use your personal data for direct marketing without your consent.
Users in Sri Lanka
If you are in Sri Lanka, we also comply with the Personal Data Protection Act No. 9 of 2022, as amended, as its provisions come into force. We transfer your data to processors in the EU and the United States only under binding contractual safeguards (EU Standard Contractual Clauses). You can exercise your rights under that Act by writing to privacy@crela.io and complain to the Data Protection Authority of Sri Lanka.
9. Right to Lodge a Complaint with a Supervisory Authority
You have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for Crela is:
Bayerisches Landesamt für Datenschutzaufsicht (BayLDA)
Promenade 18, 91522 Ansbach
Email: poststelle@lda.bayern.de
https://www.lda.bayern.de
You may, however, also contact the supervisory authority of your own habitual residence or place of the alleged infringement.
10. Obligation to Provide Data
Provision of your personal data is neither legally nor contractually mandatory. You are not obligated to provide your data. However, without this data we cannot conclude or perform contracts with you (e.g. a purchase without account and payment data is technically not possible).
11. Automated Decision-Making, Profiling
Every build a Creator submits is checked by our review pipeline: virus scanners and malware databases, static analysis of the files, a comparison of its components with known vulnerabilities, a short test run on a review machine, and an evaluation of all findings by an AI model (section 6). In most cases a person at Crela decides on the result. In the following cases the pipeline decides on its own; these are automated decisions within the meaning of Art. 22 GDPR:
- Rejection of a build that is an installer instead of the program itself (KO-12) or that lacks files the program needs to run (incomplete bundle). The rejection names the finding and what to change.
- Pause of sales of a tool if a known vulnerability in one of its components, for which a fixed version exists, is not fixed in time: within 14 days if the vulnerability is being actively exploited, 30 days if it is critical and 60 days if it is high. We warn the Creator 7 days before the deadline. Buyers keep access to the tool.
These decisions are necessary for the contract with the Creator (Art. 22 (2) (a) GDPR): Crela only sells software that passes its review. They decide whether a build is published and whether a tool can be bought. You have the right to obtain human intervention, to express your point of view and to contest the decision: use "Request human review" at the decision in your Creator dashboard. A person at Crela reviews the case within one month and can approve the build or lift the pause. On request we explain which data the decision was based on and what would have led to a different result (Art. 15 (1) (h) GDPR).
Builds that pass all checks can be approved automatically; games rated 16 are always decided by a person. Crela does no profiling.
12. Changes to This Privacy Policy
Crela adapts this Privacy Policy when its processing or the law changes. The current version is available at https://crela.io/privacy. We inform registered users of significant changes by email.


