2026-11-08.2

Pilot privacy notice

Who handles your information?

This notice covers the Blaizes mobile pilot. Boosted by Design Oy is the data controller for the pilot. Send privacy requests to feedback@blaizes.com.

What we use and why

Your account identifier and email from the sign-in service match your invitation to your account. Session and device details protect access. An age confirmation and terms version may be recorded against your account. These account details are needed for a personal pilot account.

Your message, chosen character, conversation history and a memory drawn from earlier chats help generate a reply. The model provider may receive your message and the parts of your history and memory needed for the reply. Memory helps personalise the conversation. Avoid sharing sensitive information where possible.

If you use an image or audio feature, the relevant image, audio or text may be sent to its provider. You can use text chat without sharing media. A device notification token is used for notifications if you enable them. You choose separately whether to allow optional usage analytics.

Proposed legal bases

We propose performance of the agreement as the basis for the account and conversation data necessary to deliver the pilot. Security and abuse prevention can involve technical request identifiers. We propose a legitimate interest in protecting the service and its participants for that purpose, and consent for optional analytics. The basis for each feature, the balance of interests for security processing and any additional consent requirements will be reviewed before launch.

Where is your information processed?

Cloudflare hosts the service. The conversation database and media bucket are in the EU. Supabase processes sign-in information in London, United Kingdom. Google handles authentication when you choose Google sign-in.

OpenAI receives your message and the history and memory needed to generate a text reply. The project uses global processing, which can take place outside the EEA. Voluntary sharing of messages for model development is disabled. Our providers’ data processing agreements set out transfer safeguards, including EU standard contractual clauses where applicable. Contact feedback@blaizes.com for details or a copy of the applicable safeguards.

How long is information kept?

Conversation history and memory are kept while you use your account. Start deletion in the app settings. Access is disabled and your deletion receipt shows progress, including any outstanding provider clean-up. Your phone may hold account-specific copies. Copies on another device that is offline may persist for longer.

We remove the direct account identifier and any email address from the deletion register 31 days after deletion is complete. We keep a pseudonymous identifier for as long as the old identity could otherwise regain access. It has no fixed expiry date. A receipt digest, deletion status and timestamps also remain.

Deleted data may remain in Cloudflare database recovery history for up to 30 days. Persistent Worker logging is disabled for the mobile API. Supabase API and database logs are normally available for one day. OpenAI normally keeps abuse monitoring data for up to 30 days, with exceptions where law or safety requires longer retention.

Your rights

You can request access, correction or erasure. Depending on the circumstances, you can also request restriction or portability and object to processing based on a legitimate interest. You may withdraw consent at any time. Withdrawal affects future processing. Downloading your account data and deleting your account are separate actions.

Send requests to feedback@blaizes.com. You can complain to a competent supervisory authority. Finnish Data Protection Ombudsman guidance (in Finnish).