Privacy Policy

Last updated: 29 October 2026

Protecting your personal data matters to us. In accordance with Art. 13 and 14 of the General Data Protection Regulation (GDPR), this privacy policy explains which personal data we process when you use Ouray (the "Service"), for which purposes, on which legal basis, and what rights you have.

1. Controller

The controller within the meaning of Art. 4(7) GDPR is:

[Name / company incl. legal form]
[Street and number]
[Postcode, city]
Germany

Email: [privacy@example.com]
Phone: [+49 …]

Further details can be found in the Legal Notice.

2. Data Protection Officer

[Option A – if appointed:] You can reach our data protection officer at: [name, address, email].

[Option B – if not required:] We are not required to appoint a data protection officer (Art. 37 GDPR, Section 38 BDSG). If you have any privacy questions, please use the contact details above.

3. Principles of our data processing

• Hosting in the EU: The Service and all databases are operated exclusively on servers in the EU: the application, database and file storage in Amsterdam (Netherlands), AI processing in Paris (France).
• No third-party embeds: We do not load any content from external servers. Fonts, scripts, styles and images are served exclusively from our own server. No connection to Google Fonts, content delivery networks (CDNs) or similar services is made when you visit the Service.
• No tracking: We do not use analytics, tracking or advertising tools and do not create usage profiles.
• Data minimisation: We only process data that is necessary to operate and secure the Service or to fulfil our contractual and legal obligations.

4. Hosting

The Service is hosted by:

Scaleway SAS, 8 rue de la Ville l'Évêque, 75008 Paris, France – server location: Amsterdam, Netherlands

The hosting provider processes personal data (in particular the connection data listed in section 5 and the contents of our database and our file storage (Object Storage)) solely on our behalf and according to our instructions. We have concluded a data processing agreement with the provider in accordance with Art. 28 GDPR.

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is the secure, fast and reliable provision of the Service. Where processing is necessary to perform a contract with you, the legal basis is additionally Art. 6(1)(b) GDPR.

5. Providing the website and server log files

Every time you access the Service, our server automatically processes information transmitted by your browser:

• IP address of the requesting device
• date and time of access
• requested page or file (URL) and HTTP method
• HTTP status code and amount of data transferred
• referrer URL (previously visited page), if transmitted
• browser and operating system used (user agent)

Purpose: delivering content, ensuring system security and stability, preventing and investigating attacks and abuse, and error analysis.

Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest follows from the purposes listed above.

Retention: Log files are deleted or anonymised after no more than [7] days. Data whose further retention is required for evidence purposes (e.g. after a specific attack) is excluded from deletion until the incident has been fully resolved.

Collecting this data is strictly necessary to operate the Service; you therefore cannot object to its provision as such.

6. Cookies and storage on your device

We only use strictly necessary cookies. We do not use tracking or marketing cookies, which is why we do not need a cookie banner.

Legal basis: Access to your device is based on Section 25(2) no. 2 TDDDG (German Telecommunications Digital Services Data Protection Act), as storage is strictly necessary to provide the service you explicitly requested (displaying the Service in your language and chosen colour theme or keeping you logged in to your account). The same applies to the constraints in local storage, which you set yourself. Subsequent processing is based on Art. 6(1)(b) GDPR (performance of a contract) for the login cookies and on Art. 6(1)(f) GDPR for the language and theme cookies; our legitimate interest is presenting the Service in your preferred language and colour theme.

You can delete or block cookies in your browser settings at any time. If the locale cookie is not stored, the language is determined from your browser's language settings. If the theme cookie is not stored, the dark theme is shown.

7. Fonts

We use the fonts "Geist", "Geist Mono" and "Open Sans". They are installed locally on our server. No connection to third-party servers (e.g. Google) is made when the fonts are loaded.

8. Contacting us

If you contact us by email, we process the data you provide (e.g. name, email address, content of your request) in order to handle your request.

Legal basis: Art. 6(1)(b) GDPR if your request relates to a contract or to pre-contractual measures; otherwise Art. 6(1)(f) GDPR (legitimate interest in answering requests).

Retention: We delete the data once your request has been fully handled, unless statutory retention obligations apply (e.g. Section 257 HGB, Section 147 AO).

9. User account and use of the Service

When you create a user account and use the Service, we process:

• Account data: first name, last name, email address and password. We only store the password as a hash (Argon2id), never in plain text.
• Proof of acceptance: the time at which you acknowledged the privacy policy and accepted the terms during registration (accountability under Art. 5(2) GDPR).
• Login data: for each login, a session record with a hashed refresh token, its expiry time and, if applicable, the time it was replaced by a new token. When you log out, the session's records are deleted. These records allow us to securely renew and end sessions and to detect misuse of stolen tokens.
• Project data: the projects you create with title, genre, status, optional logline and the time of creation and last change, plus the story profile of a project (chosen catalog modules, episodes, running time, budget class, supporting character) and its development documents (such as logline, characters, world, tone and themes, pitch, exposé, treatment, series bible, season arc, episode outline and key art prompt) in all versions, each with your additional instructions, your edits, suggested changes and your decision on them, and a snapshot of the project and story profile at the time of creation. We store the project's logline as a version of the logline, also when you change it in the project settings. Projects are only visible to you. If you enter information about other people in these fields (e.g. names in the logline), we process it as well. If you upload a cover image, we store it scaled down and re-encoded in a private storage area (Object Storage) of our hosting provider in Amsterdam (see section 4); in the process we remove metadata such as camera data and location. If the image shows people, we process these depictions as well; only upload images you are allowed to use. To keep the main subject in view when the image is cropped, we send a reduced copy of the cover image to a language model (see “AI-assisted story development”) and store only the position of the subject it finds. The cover image is deleted when you remove or replace it, at the latest with the project.
• Content data (IP Content Generator): the ideas you enter, your constraints (e.g. genre, format, scope, supporting character), the catalog modules recognised in them and the generated suggestions (title, logline, perspective, rationale, the works a suggestion draws on with a short reason). See also “AI-assisted story development” below.
• Usage counter: per day, the number of your AI requests and the tokens used, without any content. We use it to limit misuse and to provide usage limits.
• Editorial log (only for staff with editorial rights): for changes to the story catalog, which account published which version and when.
• Usage data: time of registration and of the last change to your account.

Purpose: providing your account, secure login and the contractually agreed features.

Legal basis: Art. 6(1)(b) GDPR (performance of a contract); for the proof of acceptance additionally Art. 6(1)(c) in conjunction with Art. 5(2) GDPR.

Retention: For the duration of the contractual relationship. You can delete a project at any time in its settings; it is then deleted immediately and permanently. Expired session records are deleted at your next login or session renewal, and at the latest together with your account; deleting your account also deletes all of your projects. After your account is deleted, the data is deleted within [30] days unless statutory retention obligations apply; in that case processing is restricted.

You can request the deletion of your account and a copy of your data at any time by sending an informal email to the address in section 1.

AI-assisted story development

When you enter an idea in the IP Content Generator, we send your idea and your constraints to a language model. The model maps the idea to modules of our story catalog and generates suggestions for stories from it. When you have documents created in a project, we send the project's title, genre and story profile, the documents already created in the project (including logline, characters, world and tone) and your additional instructions to the language model. After each document except the key art prompt, we send that document together with the logline, characters, world and tone to a language model again, which checks whether these foundations should be adjusted; this results in suggestions that you can accept or discard. Suggestions and documents are AI-generated and labelled as such, documents also in the download. When you upload a cover image, we send a reduced copy (without metadata) to a language model, which only returns where the main subject is.

• Provider: Scaleway SAS, 8 rue de la Ville l'Évêque, 75008 Paris, France (“Generative APIs”), as a processor under Art. 28 GDPR. Processing takes place in data centres in Paris, i.e. in the EU.
• No storage and no training: Scaleway does not store requests and answers as a rule (zero data retention) and does not use them to train or improve models. Exception: in the event of technical errors or to investigate misuse, Scaleway may store a complete request for up to two weeks. Scaleway also stores metadata without content (e.g. time, token count, status code).
• On our side: We store your searches (idea, constraints, recognised modules, suggestions) so you can reopen them in your history. We store documents as versions in the project, together with model, temperature and catalog version, so it stays traceable how a text was created. We do not write the content of your ideas and documents to log files.
• Purpose and legal basis: providing the feature you use, Art. 6(1)(b) GDPR (performance of a contract).
• Retention: Searches are deleted automatically 90 days after they were created. If you adopted a suggestion into a project, the related search is kept as long as the project exists. You can delete single searches or all of them at any time in your history; they are then deleted immediately and permanently. Documents are kept as long as the project exists and are deleted with it. The usage counter is deleted after 90 days, at the latest together with your account.

Please do not enter data about real people in your ideas that you are not allowed to share.

Works database

We maintain our own database of well-known films and series as a basis for the IP Content Generator. We regularly fetch its data (title, year, genre, source material, monthly Wikipedia page views) from the Wikimedia Foundation (Wikidata, Wikipedia, Pageviews API). These requests run on our servers, independently of your use; no data about you is sent to Wikimedia. We do not include works about real people (e.g. biopics).

For your idea, the IP Content Generator looks up matching works in this database by the recognised modules, on our servers. We pass the title, year, type (film or series) and shared modules of these works to the language model as inspiration (see “AI-assisted story development”); your idea is not sent to anyone else for this. The suggestions name the works they draw on with a link to the Wikipedia article. Only when you follow such a link do you open a page of the Wikimedia Foundation, where its privacy policy applies. We do not pass on the referring page (referrer). We store the works used together with the suggestion and delete them with it.

The sources and licences we use are listed on the page Sources and Licences.

10. Recipients of personal data

We only share personal data where permitted by law. Recipients may be:

• our hosting provider as a processor (see section 4)
• Scaleway SAS, Paris, France, as a processor for AI-assisted story development (see section 9)
• [further processors, e.g. email delivery, payment provider – each with name, purpose and location]
• public authorities where we are legally obliged to disclose data (e.g. law enforcement)

We do not share data for advertising purposes and never sell data.

11. Transfers to third countries

Personal data is not transferred to countries outside the European Union or the European Economic Area. Should this change, transfers will only take place if the requirements of Art. 44 et seq. GDPR are met (e.g. an adequacy decision or standard contractual clauses), and we will update this policy beforehand.

12. Retention

Unless a more specific retention period is stated in this policy, we only process personal data for as long as necessary for the respective purpose. Where statutory retention obligations apply (e.g. 6 years for business correspondence and 10 years for accounting records under Section 257 HGB and Section 147 AO), processing is restricted until these periods expire and the data is then deleted.

13. Data security

For security reasons, the Service uses TLS encryption (recognisable by "https://" in the address bar). In addition, we implement technical and organisational measures in accordance with Art. 32 GDPR to protect your data against loss, manipulation and unauthorised access. A strict Content Security Policy technically prevents content from being loaded from third-party servers.

14. Your rights

You have the following rights regarding your personal data:

• access (Art. 15 GDPR)
• rectification (Art. 16 GDPR)
• erasure (Art. 17 GDPR)
• restriction of processing (Art. 18 GDPR)
• data portability (Art. 20 GDPR)
• objection to processing (Art. 21 GDPR)
• withdrawal of consent with effect for the future (Art. 7(3) GDPR)

To exercise your rights, an informal message to the contact address in section 1 is sufficient.

Right to object under Art. 21 GDPR

Where we process data on the basis of Art. 6(1)(f) GDPR (legitimate interest), you have the right to object to this processing at any time on grounds relating to your particular situation. We will then no longer process the data unless we can demonstrate compelling legitimate grounds for the processing which override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims.

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), in particular in the member state of your habitual residence, place of work or place of the alleged infringement. The supervisory authority responsible for us is:

[Name of the competent state data protection authority, address, website]

15. Obligation to provide data

Providing the connection data listed in section 5 is technically required to use the Service. The information requested during registration (section 9) is required to conclude the contract; without it we cannot provide a user account. Beyond that, you are under no obligation to provide us with personal data.

16. Automated decision-making

We do not use automated decision-making, including profiling, within the meaning of Art. 22 GDPR. The AI suggestions in the IP Content Generator are prompts for you; they do not decide anything about you.

17. Changes to this privacy policy

We update this privacy policy whenever our data processing or the legal situation changes. The current version published here applies.

In case of discrepancies between the language versions, the German version prevails.