This policy explains what Object Cinema Studio collects, why, who else sees it, how long we keep it and what you can ask us to do about it. Object Cinema Studio is operated by Dream Reels LLC, a Kansas limited liability company. Questions and requests: [email protected].
This is a notice, not a consent form. Agreeing to our Terms of Service is not agreement to every use of personal data described here; where the law requires your consent for something specific, we ask for it separately.
The short version. We collect what we need to run your account and make your images and videos. To make them, your product photographs and your brief are processed by specialist generation, analysis and hosting providers, and are looked at by our small review team, led by our creative director, which makes and checks your order. We measure whether our advertising works with Meta. We do not sell your data. Our own cookies only keep you signed in and keep checkout working.
1. What we collect, and why
Before you give us an email. When you start from the Object Cinema Studio page we create a temporary account with no email address, tied to that browser, so your photographs and brief are kept while you work. If you never give an email address, that account and its photographs are removed after 30 days.
Sample pages. If we send your agency a private sample page, we record when it is opened and watched, which plan is tapped, when its link to our main site is followed, and the email you give to download it, and we are told of each except the link to our site. We keep your agency's work email domain with the sample, so that accounts on that domain are not offered a second free preview.
Account information — your email address and, if you set one, a password. The password is stored only as a salted scrypt hash; we cannot read it. We ask for your email address to make your free image, and we ask you to confirm it with a code before we make your free preview (a 15-second video made from the free image) and before you download or buy. An address that has not completed confirmation is not treated as confirmed. If you make a free image and do not buy, we send one follow-up email to that address about a day later, with a link to opt out. We send no other marketing email unless you ask for it.
Plans and orders — your plan, its renewals and anything you bought before plans, what each brief used, your orders and their status. We also store the identifiers Stripe gives us for your customer record and payments. We never see or store your card number; card data goes directly to Stripe.
Uploaded photographs and reference materials — the product photographs you upload, and any inspiration or reference images. These are the raw material the Service works from.
Product descriptions and creative instructions — what you type about your product, your creative brief, the things you ask us to avoid, and your saved visual directions and brand notes. The Service also stores what the AI reads off your product label — a transcription of the text printed on the packaging — because it is used to check that generated frames reproduce the label correctly.
Generated images and video — everything the Service produces for you, including your free image and free preview, intermediate frames and per-shot files, and the full history of earlier versions of a piece. The Service does not currently produce audio.
Technical data — our web server (nginx) and Cloudflare record standard request logs, which include IP addresses. The application itself writes a small operational log containing internal record identifiers and provider request identifiers; it does not log email addresses, passwords, prompts, briefs or image content. There is no session recording and no outside analytics service inside the signed-in application; what the application itself records about your progress is described in the next two paragraphs. Advertising measurement on the marketing site is described in Section 2.
Limits on free images — to limit how many free images one network can request in a day, we keep a scrambled (hashed) form of your network address with the request. We cannot turn it back into the address.
Which step you reached — the application records which step each account reached: photos added, photo check passed, brief seen, plan chosen, paid, delivered. We use it to see where people stop. It is not sent to anyone.
Support communications — if you email [email protected], we keep the message so we can answer it and refer back to it.
We collect all of this because it is necessary to provide the Service you have asked for and to bill you for it. Where the GDPR or UK GDPR applies, our legal bases are performance of a contract (running your account and generating your images), legal obligation (tax and accounting records) and legitimate interests (security, fraud prevention and keeping the Service working).
2. Who else receives it
We use the following providers. Each receives only what it needs.
Generation providers — these receive your photographs
Image generation services (United States) receive product photographs and prompt text built from your brief. The service we use states that it does not train on business API inputs or outputs unless its customer opts in, and may retain inputs and outputs for up to 30 days for abuse detection.
Photo analysis and quality-check services receive product photographs, inspiration images and text to check coverage, develop directions and inspect results. We use paid business processing for which submitted content is not used to improve the provider's products. Its abuse-monitoring retention is 55 days.
Video generation and temporary media hosting services (United States and other countries) receive photographs, previews and instructions and may pass them to the underlying model operator. Temporary provider file links can be accessible to anyone holding the link unless access controls are configured. Finished media in your Object Cinema library is served through authenticated, ownership-checked addresses; temporary provider links are not published to customers. The generation platform's terms exclude training on customer content except for models it marks as not enterprise-ready. Its default request-payload retention is 30 days; generated-media retention depends on per-request settings. We cannot make a blanket retention or training promise for every downstream model operator with which we have no direct contract.
For provider-specific privacy information or a request concerning recipients of your data, contact [email protected].
Infrastructure and business providers
Amazon Web Services — hosting. All of your account data, uploads and generated files are stored on a server in the AWS us-east-1 region in the United States. This server is shared with another product operated by the same company, Dream Reels; the two applications run under separate system users, with separate files, separate databases and separate credentials, but they are on the same machine. That is process separation, not infrastructure isolation, and we would rather say so than imply more than is true.
Cloudflare — sits in front of the site providing DNS, TLS and protection against attack. Cloudflare sees the metadata of every request, including IP addresses.
Stripe — payments. Stripe receives your name, email address and our internal account identifier, and it collects your payment details directly. Stripe acts in two capacities: as our processor when handling a transaction on our instruction, and as an independent controller for its own fraud prevention, regulatory compliance and service improvement. Stripe publishes its own privacy notice and sub-processor list.
Meta Platforms (United States) — advertising measurement, only for visitors who are not blocked by the rules in Section 8. Three parts, and they are different:
- In your browser. Meta's pixel loads on the Object Cinema Studio page and reports that the page was viewed, that the pricing section was looked at, and that a button leading into the application was pressed. It sets Meta's own cookies (see Section 8) and Meta receives your IP address, browser user-agent and the page you were on.
- From our server, four times at most per account: when you first upload a product photograph, when you first see your free image, when you start a checkout, and when a payment settles. Each report carries the Meta click and browser identifiers (
_fbc,_fbp) if the pixel set them, and the IP address and browser user-agent of that request. Once we have your email address, the report also carries a hashed version of it, hashed with SHA-256 before it leaves our machine, so we never send Meta your address in readable form; a payment report carries its value and, where Stripe recorded one, a hashed billing country. Meta can still match that hash against an account it already holds, which is the point of sending it, and we would rather you knew.
No Meta script runs inside the signed-in application at app.objectcinema.ai; the server reports above are the only way anything about your account reaches Meta. Meta is not sent your photographs, your briefs, your generated images or videos, or anything about what you made.
Resend (Resend Inc., United States) — email delivery. Resend receives your email address and the contents of the messages we send you: your confirmation code, free image ready, free preview ready, plan started, renewed, cancelled or payment failed, order received, order ready, sign-in code, password reset and confirmation that a password was changed.
Google Fonts — the site loads its typefaces from Google's font servers. This means your browser makes a request to Google on every page load, which necessarily discloses your IP address and browser user-agent to Google. We are looking at hosting the fonts ourselves to remove this.
What we do not use
There is no general analytics platform, no error-monitoring service, no session recording and no A/B testing tool anywhere in the Service. The application's own record of which step you reached is described in Section 1.
Correction, and we would rather state it plainly than quietly rewrite it. Versions 1.0 and 1.1 of this policy said there was no advertising pixel, no Meta Pixel and no Conversions API. That was true when it was written. It stopped being true on 7 September 2026, when we added Meta advertising measurement to the marketing site, and this policy did not keep up. Section 2 now describes exactly what that does. The same applies to email: earlier versions said we had no email-sending service and could not send you transactional mail. We do now, and it is described under Resend in Section 2.
We do not sell personal information for money.
We do share information for cross-context behavioural advertising, as that term is defined under California law, and we are not going to pretend otherwise: the Meta advertising measurement described in Section 2 sends Meta a hashed version of your email address and the value of your purchase, and Meta may use that to build audiences. Global Privacy Control is honoured automatically. If your browser sends that signal, no pixel loads, no Meta cookie is set and no purchase is reported — no email to us required. You can also opt out by writing to [email protected] from the address on your account.
We may also disclose information if we are legally required to, or as part of a merger, acquisition or sale of assets, in which case this policy continues to apply to it.
3. International processing
Our servers are in the United States. Our providers are US-headquartered and may process data in the United States and elsewhere. If you are in the EEA or the UK, using the Service therefore involves transferring your data to the United States. We rely on our providers' standard contractual clauses and equivalent transfer mechanisms where they offer them. We have not completed a formal transfer-impact assessment, and we say that plainly rather than implying a compliance posture we have not built.
4. How long we keep things
| What | How long |
|---|---|
| Account record, plans and orders | While your account is open |
| Uploaded photographs and reference images | While your account is open. If you have never paid for a plan, they may be removed 90 days after upload |
| Free image and free preview | While your account is open. If you have never paid for a plan, they may be removed 90 days after they were made |
| Delivered images and videos | While your account is open |
| A temporary account that never gave an email | 30 days |
| Server and application logs | Application log rotates at 7 days; Cloudflare and nginx logs follow their own retention |
| Billing records | As long as tax and accounting law requires |
| Backups of the database | 14 nightly snapshots on the server; nightly copies in encrypted cloud storage (Amazon S3, United States) kept for 90 days |
| Support email | While needed to answer, and for our records |
Database backups contain account records — including email addresses, password hashes, Stripe identifiers and plan and order history. A copy is kept on the server for 14 nights and a copy is sent nightly to Amazon S3 (United States), where it is encrypted at rest, not publicly reachable, and expires after 90 days. Your uploaded photographs are also copied nightly to S3 so they survive a server failure; those copies are removed when your account is deleted. Customer-visible generated clips, images, concepts, earlier versions and edited exports are also copied to private, encrypted S3 storage. Renderer scratch files and rejected takes are not included. These media backups are removed when the related account is deleted; unsuccessful cloud deletions are retried by the scheduled backup and deletion jobs.
4a. When we look at your content
Every order is made and checked by our small review team, led by our creative director. A member of that team opens your uploaded photographs, your brief and the images and videos made for you. The same team can open them to answer a support request or to investigate something that failed. Looking at your work never deletes anything and never sends you a message.
We do not use your photographs or your generated videos in our marketing, publish them, show them to anyone outside Object Cinema Studio, or use them to train any model — ours or anyone else's. If we ever want to show your work publicly we will ask you first, and you can say no.
Access is restricted to a single administrator account protected by a password, granted only from the server and only after control of that mailbox has been proved. Every change to a plan or an order and every internal note made through those tools is recorded with who made it and when.
5. Deleting your data
We keep your content while your account is open, as set out in Section 4.
To have us delete it, email [email protected] from the address on the account. We will confirm and remove your content within 30 days of the request.
You can also close the account yourself from the Account page (Close my account). That flags the account for deletion and it is removed, with its content, by our nightly process — within 30 days at the latest, in practice the next night. You can remove individual uploaded photographs from within the Service.
What deletion does not reach: database backups expire on their retention schedules rather than being individually edited: up to 14 nights for local backups and up to 90 days for encrypted cloud backups. Deletion of finished-media backup objects is handled as described in Section 4; billing records are kept as the law requires; and content already sent to generation, analysis, hosting and model operators is subject to their retention, which we cannot shorten on your behalf.
6. Your rights
Depending on where you live you may have the right to know what we hold, get a copy of it, correct it, delete it, restrict or object to processing, withdraw consent, and not be discriminated against for exercising any of these.
If you are in California, you have the rights to know, delete, correct and opt out of sale or sharing under the CCPA/CPRA. We do not sell personal information. We do share it for cross-context behavioural advertising in the one way described in Section 2 (the Meta pixel on the Object Cinema Studio page and the server reports), and you can opt out of that in two ways: turn on Global Privacy Control in your browser, which we honour automatically, or email [email protected] from the address on your account and we will stop reporting your purchases to Meta. The other rights are exercised through the channel below.
If you are in the EEA or the UK, you have the rights of access, rectification, erasure, restriction, objection and portability under the GDPR/UK GDPR, and the right to complain to your supervisory authority.
How to make a request: email [email protected] from the address on your account, and tell us what you want. Because there is no automated pipeline behind this, requests are handled by a person. We aim to respond within 30 days and will tell you if we need longer. We may need to confirm your identity before acting on a request.
You can download a copy of everything on your account — your photographs, your free image, your delivered images and videos, and a summary of your plan and orders — from the Account page (Download everything). It arrives as a ZIP. An order still in production is added when it is delivered.
7. Children
The Service is for people aged 18 and over. We do not knowingly collect personal information from children. If you believe a child has given us information, email [email protected] and we will delete it.
8. Cookies and similar technologies
We set three cookies of our own. oc_sess holds a signed session identifier and exists solely to keep you signed in; it is marked HttpOnly, SameSite=Lax and Secure, and lasts up to 30 days. oc_member holds only "1" while your account has a live plan, so a plan button on objectcinema.ai doesn't start a second plan; it lasts up to a year. oc_studio_direct ties a checkout started from objectcinema.ai to this browser; it is HttpOnly and lasts 24 hours. None carries personal information or is used for analytics or advertising. All three are strictly necessary for the Service to work.
The Meta pixel on the marketing site sets its own cookies, principally _fbp, and our own script writes a _fbc cookie from the click identifier when you arrive from a Meta advertisement. These are advertising cookies and they are not strictly necessary. They are set by the marketing site for the objectcinema.ai domain, so your browser also sends them to the signed-in application at app.objectcinema.ai; the application sets no Meta cookies of its own and reads these only to attach them to the server reports described in Section 2.
If your browser looks like it is in Europe, the pixel does not load at all. We do not advertise in the EEA or the UK, so rather than ask those visitors for consent we simply do not measure them: no Meta script is fetched, no Meta cookie is set, and nothing about the visit reaches Meta. If you go on to upload or buy, nothing is reported.
We decide this from your browser's own timezone setting, which is read on your device and sent to nobody. It is a rough test and we would rather describe it accurately than overstate it: a European using a VPN that reports a US location will be measured, and someone outside Europe whose computer is set to a European timezone will not. Where it cannot tell, it does not measure. The signed-in application has no pixel, so for the server reports our server decides instead from the country our network provider, Cloudflare, reports for the connection (worked out from your IP address): a connection from the EEA, the UK or Switzerland, or one whose country is unknown, is not reported.
We also honour Global Privacy Control, everywhere and not only in Europe. If your browser sends that signal, no advertising technology loads and none of the server reports is sent.
Because nothing optional is set for those visitors, there is no consent banner for them. For visitors elsewhere the pixel does load; if you would rather it did not, turn on Global Privacy Control, block third-party cookies, or email [email protected] and we will exclude you.
The application keeps a few things in your browser's own storage so a refresh does not lose them: your brief, your plan choice, a product name you have typed and, before you have given it to us, your email address as you type it. They stay in your browser and are not sent to anyone until you send them. Most clear when you sign out or close the tab. On the marketing site your browser also loads Meta's pixel script and Google's font servers, both described in Section 2. Inside the signed-in application, Google's font servers are the only third-party request.
Cloudflare may set its own security cookies as part of protecting the site.
9. Security
Passwords are stored as salted scrypt hashes and never in readable form. Sessions are held server-side, and the session cookie is signed and verified in constant time. Every request for a file or record checks that it belongs to your account before returning anything. Traffic between your browser and our site is encrypted, and the connection from Cloudflare to our server is encrypted with a certificate issued to the site. Secrets are held in files readable only by the account that runs the application, and are never sent to the browser.
Being straightforward about the limits: data at rest on the server is not separately encrypted beyond the disk it sits on; local database backups are compressed and are not separately encrypted; cloud backups are encrypted at rest; there is no automated intrusion alerting; there is no formal security certification, and we do not claim SOC 2, ISO 27001 or any equivalent. No service can promise perfect security. If a breach affects your personal data we will notify you as the law requires.
10. Changes to this policy
The version and effective date are at the top of this page and previous versions remain available at objectcinema.ai/legal/. For material changes we will give notice in the Service before they take effect. Where we can, we will also tell you by email at the address on your account.
11. Contact
Dream Reels LLC, doing business as Object Cinema [email protected]