Privacy

Reel Studio is operated by Tiraisoft, Indonesia. This page describes what the product collects when you use it, why, how long it is kept, and who else handles it. Questions and requests about your data, including deleting your account, go to support@tiraisoft.com.

Cookies and tracking

We use no cookies to identify you and no advertising pixels. We do not build a profile of you across visits, and we do not sell or share your data.

We do measure how the product is used, so we can tell which parts of it are working. That measurement is first-party — it goes to our own servers and nowhere else — and it is scoped to a single visit: a random id is kept in your browser's sessionStorage and is discarded when you close the tab. We record which steps were taken and how long they took, the page path, and the host a visit arrived from (for example google.com), never the full link or anything you typed into a search box.

We also record three broad facts about the visit itself: the kind of device (phone, tablet, desktop, or an automated crawler), the operating system and its major version only — iOS 17, never iOS 17.4.1 — and the country and region the connection came from, which Cloudflare works out at its edge so that this measurement never sees or keeps the address itself (the free tool and the support chat, below, are the places an address is stored). We do not keep the browser's User-Agent string: it is read once to work out the device and the system, and then discarded, because the full string is detailed enough to single somebody out.

Each of those is counted on its own. We keep a daily total per device kind, and a separate daily total per country, and we never keep a row that combines them — so the numbers cannot be narrowed to "the one person on a tablet in Iceland". The cost of that, to us, is that we cannot ask which system a particular country's visitors run. We think that is the right way round.

We also measure how long each page was open and visible, so we can see which pages are actually read. The clock stops whenever you switch away from the tab, so a page left open in the background does not count as time spent reading.

We do not store your IP address for analytics. To count distinct visitors within a day we keep a one-way hash of it combined with the date and a secret, which cannot be reversed and cannot be matched to any other day. Individual event records are deleted after 30 days; only anonymous daily totals are kept after that.

If you are signed in, we keep one small record per account so we can tell repeat use from first-time use: your account id with the first day and the last day it was active. Two dates, and nothing else — not what you did, not which pages, not from where. It is your existing account id, not a new identifier: nothing is written to your browser to make it, and it does not exist at all for a visit you make signed out. It is deleted when your account is deleted.

What you make in the studio

When you use the studio we keep, with your account, each job — the prompt, the model and settings you picked, the pictures you attached to it, how many credits it cost and how it ended — and the files in your bank: the pictures and videos the models make for you and the ones you upload, with their size and dimensions. An upload is identified from its contents, never from its name.

The files are private. Each one is reached through a link that carries a signature and stops working within 7 hours, so a link copied out of the page does not stay usable. Deleting an item from your bank removes its file from storage straight away; the job records that mention it stay with your account. Everything — jobs, files and records — is deleted when your account is deleted.

Free tool

The free tool — the prompt generators, which work without an account — is different: to enforce its daily limit it keeps the IP address of the connection, as the raw address, with a count of how many times it was used that day. That record expires on its own after about a day (26 hours). Before a request is answered, the tool also runs a browser check to keep automated abuse out, and the IP address is sent with it to Cloudflare, which runs the check.

Support chat

The sections above describe measurement and the free tool. The support chat is different, because it exists to keep a conversation, and none of the measurement's properties apply to it. If you send a message in it, we store:

• the transcript — every message you send and every reply;
• who it belongs to — your account id if you are signed in, otherwise a random visitor id that the chat creates when you send your first message and keeps in your browser's localStorage, so the conversation can be reopened on a later visit;
• the IP address of the connection the conversation started from, stored with the conversation and used to limit abuse of the chat.

Each conversation is classified automatically (for example as a question, a bug report or a feature request). A short summary of a bug report or a feature request is emailed to our own feedback inbox so the team sees it.

Chat conversations are kept until they are deleted; they have no automatic expiry. A signed-in account's conversations are deleted when the account is deleted.

Who else touches your data

• Cloudflare — hosting, including storage of the pictures and videos in your studio bank, delivery of the support chat's bug-report and feature-request summaries to our feedback inbox, and the free tool's browser check (Turnstile), which receives the IP address of the connection.
• Third-party image and video model providers — the prompt and settings of each studio job, and any picture you attach to it, go to the provider that runs the model you picked, so it can make the result. An attached picture is handed over as a link the provider fetches, which stops working within 3 hours. The category is the disclosure, for the same reason as below.
• A third-party large-language-model provider — the text you submit is sent to it so the product can produce a result (when you ask the studio's assistant to improve a prompt, the pictures that prompt is about go with it), and so are your support chat messages, so it can write the reply and classify the conversation. The category is the disclosure: Article 13(1)(e) GDPR asks for the recipients or categories of recipients, and the provider is not named here.
• A third-party payment processor — paid plans and credit packs are paid for on its own site, so the card or account details you enter go to it and never reach us. It receives the plan you picked and an internal id that links the payment back to your account, and it sends back the subscription's status. The category is the disclosure here for the same reason as above: Article 13(1)(e) GDPR asks for the recipients or categories of recipients.