watchmycreation is operated by Sajai Digital (sole proprietorship), Flat No. 1101, J Wing, Empire Square, Kalewadi Road, Near KWT Tower, MIDC Chinchwad, Pimpri Chinchwad, Pune, Maharashtra 411019, India. Contact support@watchmycreation.com or +91 98504 69469.
This policy explains what we collect, why, who else sees it, how we protect it and where it is processed. The short version: viewers have no accounts, and we collect as little as the service can work on.
If you are a viewer
We collect:
- The phone number you give at checkout, if any. We ask Razorpay’s checkout not to require a phone number, but Razorpay may still ask for one, or for an email address, before you can pay, or fill one in from an earlier payment you made through Razorpay. When the payment completes, we store any contact Razorpay passes us — usually a phone number — with your order. We use it to find your ticket if you lose your code and write to us, and a masked form of it is shown over the film while you watch (see below). We do not text you your ticket, and we never use your contact for marketing. If Razorpay passes us only an email address, we may email a copy of your ticket to it.
- Payment details are never seen by us. Payments are processed by Razorpay. Your card, UPI ID and banking credentials go to them directly and are never stored on our systems. We keep only a payment reference, the payment method (UPI or card, for example) and the amount.
- Your access code and contact, shown over the film. While a film plays, the ticket’s access code and, if we have one, your contact with the middle digits hidden are drawn over the picture, as a deterrent against recording and re-sharing it. That means anyone you share the link with, and anyone who sees a recording of the screen, can see them.
- Playback records — when a ticket was first played, each playthrough and whether it was finished, how much streaming time the ticket has used, and, for a playthrough you have not finished, how far into the film you got. That last figure is what lets the same link pick the film up close to where you stopped. It is kept with the ticket’s playback records, and is deleted if we reissue the ticket’s access. These records are what enforce the access window and the play limit.
- Technical data — IP address and browser user-agent, used for rate limiting, to protect checkout from abuse, and to show which kind of device a film is already playing on. The IP address is also recorded in our audit log, with the record it belongs to, in three cases: when a review is posted, when a film is reported, and when a payment confirmation sent from a browser fails its signature check.
- Your country, for a purchase in US dollars. At checkout we read the country Cloudflare’s network places your connection in, which it works out from your IP address, and it decides whether you are charged in Indian Rupees or, where we sell that film in US dollars, in US dollars. For a purchase made in US dollars we store that country with the order and print it on the invoice, as the record that the ticket was supplied to someone outside India, and we keep it with the invoices for 8 years. For a purchase in rupees it is not kept.
- An age declaration, on 18+ films only. If you confirm you are 18 or over at checkout, we record that you did and when. We do not verify it and we hold nothing else about your age.
We do not create viewer accounts, and we do not track you across other websites.
If you write a review
Only someone who bought a ticket and finished the film can review it. We do not ask for your name and we do not store one. What we keep is the star rating, what you wrote, the date, and — privately, never published — which ticket it came from, so that one ticket leaves one review and so we can act if a review is reported. Our audit log also records the IP address the review was posted from.
A review is published indefinitely and cannot be edited or deleted, including by you. We say so on the form before you write one. A review that is reported and found to break our rules is hidden rather than erased, and a refunded ticket's review is hidden automatically. Because a review is linked internally to a purchase, it is personal data even though it carries no name — write to privacy@watchmycreation.com if you need to raise something about one.
If you report a film
The Report this film form asks what is wrong and, if you choose to give them, your name and a way to reach you — which a copyright complaint must include, so we can tell you what we decided. We keep them with the complaint in our complaint register and use them only to handle it. Our audit log also records the IP address the report came from.
If you are a filmmaker
We hold your name, email address, phone number, city, a short bio, a profile photo and links if you add them, your films, and the payout details you enter (a UPI ID, or a bank account number and IFSC). If you give them, we also hold your state, your GSTIN and your postal address, which go on the invoice that documents each payout. Payout details are used only to pay you.
Your phone number is required when you register. We use it only to contact you about your account, your films and your payouts. It is not verified, it is not used to sign in, and it is never published: it is visible to you and to our administrators.
We also hold your PAN, which we need before we can release a payout, and the date you confirmed you are 18 or over. We do not verify either against any government record — both are declarations you make to us. Your PAN is shown in full only to you; our administrators see it masked. It is never published or shared except where tax law requires it.
We record your acceptance of these documents. When you register, and again each time you submit a film, we store which document you accepted, its version, what you were doing, the time — and the IP address you accepted it from. That record is the evidence that the agreement exists, so it is kept for 8 years, with the invoices. You can see your own record in your studio; it does not show the IP address, which we keep but do not publish back to you.
Once your account is approved, your name, city, bio, photo and links appear on your public profile page, beside your published films. We email you your sign-in codes and messages about your account, your films and your payouts; messages that are not needed to run your account can be switched off from the link at the foot of each one.
Cookies
We use one strictly necessary cookie, to keep filmmakers and administrators signed in. The player keeps a session identifier in your browser’s session storage while a film plays, and the site remembers your language in your browser. We do not use advertising or cross-site tracking cookies.
Who else sees your data
- Razorpay — to take payment and issue refunds.
- Cloudflare — hosting, our database, file storage and video delivery; and Cloudflare Email Sending, which delivers sign-in codes and account emails to filmmakers and administrators, and, where Razorpay gave us only an email address, a copy of a viewer’s ticket.
- YouTube or Vimeo — only if you press play on a trailer. A film page shows the poster and a play button and loads nothing from either service until you click it; the trailer then comes from that service (for YouTube, its privacy-enhanced domain), which receives your IP address and browser details under its own privacy policy.
- Unsplash — some stock photographs on the site, such as the home page’s main image and the picture shown for a film that has no poster of its own, are loaded from Unsplash, which receives your IP address and browser details when those images load.
- Sentry — when something on the site goes wrong in your browser (a page error, a failed upload, a player that stops, a payment the gateway declines), your browser sends a technical error report directly to Sentry, our error-monitoring service in the United States, which receives your IP address and browser details. A report says what failed, on which part of the site, in which browser and operating system, and what the page did just before. Before it leaves your browser we remove access codes, ticket and receipt links, order and payment references, email addresses, phone numbers and payout details. We do not record your screen. When something goes wrong on our servers while handling your request (for example a payment, an upload or an email we could not send), our servers send Sentry a report of what failed, with the same details removed; it does not include your IP address. Sentry keeps reports for up to 30 days.
- The other side of a rights complaint. When someone complains that a film infringes rights they hold, we send the complaint and their contact details to the filmmaker, and the filmmaker’s contact details to them, so that the two of them can resolve it. That exchange happens only for a complaint about rights, and our Intellectual Property Policy sets out exactly what is passed on and when.
- Authorities — where the law requires it, or on a valid order of a court or government agency.
Filmmakers are not on that list, and that is deliberate. A filmmaker is shown how many tickets their film sold and what they earned. They are never given a viewer’s name, contact detail, payment reference or access code, and nothing in our Filmmaker Agreement permits us to hand one over.
We do not sell personal data.
How we protect your data
We hold filmmakers’ bank account and UPI details and their PAN. Financial information such as bank account details is sensitive personal data under the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011. We collect it only to pay the filmmaker it belongs to, who gives it to us for that purpose. These are the security practices in place:
- Encrypted connections. Every page on the site, including the studio where payout details are entered, is served over HTTPS, and a request made over plain HTTP is redirected to HTTPS. Check that the address begins with https:// before you enter payout details or your PAN.
- No passwords. We store no passwords, for anyone. Filmmakers and administrators sign in with a single-use code sent by email. We store only a keyed hash of each code, never the code itself, and a code expires within minutes and stops working after a few wrong attempts.
- Sessions that can be ended at once. A signed-in session is a random token in an HttpOnly cookie, which scripts on a page cannot read. Sessions are held on our servers so they can be revoked immediately, and an account’s status is checked on every request, so a suspended account loses access at once. Administrator sessions expire sooner than filmmakers’.
- Limited access to payout details. A filmmaker’s bank and UPI details and PAN are available only to that filmmaker, signed in, and to our administrators, who need them to make payouts; administrators see the PAN masked. An administrator account cannot be self-registered: it exists only if we create it.
- A record of changes. Administrative actions and money events are written to an audit log, and so is each save of a filmmaker’s payout details, when and by whom. When a save actually changes those details, we send an email to the address on the account, naming which ones changed.
- Payments. Card, UPI and banking credentials are entered with Razorpay and never reach our systems.
- Films. Videos play only through signed links that expire within minutes, and cannot be downloaded as a file from the player.
No system is perfectly secure. If we become aware of a breach that affects your personal data, we will tell you and the authorities as the law requires.
Where your data is processed
Our database is hosted by Cloudflare, with its primary copy in Singapore. Posters, videos, sessions and cached pages are stored and served from Cloudflare’s network, which operates in many countries, so a request is usually answered from a location near whoever made it. Payments are processed by Razorpay. We do not claim that your data is kept only in India.
How long we keep it
- Playback records — which ticket was played, when, and how far it got — are deleted 90 days after the ticket’s access window closes. A nightly job does this; it is not a promise we keep by hand.
- The original file of a film a filmmaker uploads is kept privately in Cloudflare R2, as a backup the platform can re-encode from, until the film is deleted. If a film is taken down, its original is kept for 180 days afterwards as the record of what was removed, and longer if a court or a government agency requires it.
- Drafts — a film started in the studio but not submitted — that are not edited for 7 days are deleted automatically, with any video and poster uploaded to them. We email the filmmaker 2 days before. Editing the draft, uploading to it or submitting it restarts the count. A nightly job does this.
- Complaints, and reports about a film or a review, are kept for 3 years.
- Your acceptance of our agreements is kept for 8 years, with the invoices: it is evidence of a contract, not an operational log.
- Orders, payments, invoices and payout records are kept for as long as tax and accounting law requires, which is 8 years. Nothing deletes them on a schedule, and the job above is written so that it cannot reach them.
- A filmmaker’s payout details are kept while the account exists.
Your choices
You can ask us what we hold about you, ask for it to be corrected, or ask us to delete it where we are not required to keep it. Write to privacy@watchmycreation.com. We answer a request about personal data within 30 days. Note that deleting a ticket’s record also destroys the access it grants.
If you are not satisfied
Our Grievance Officer is reachable at grievance@watchmycreation.com. We acknowledge every complaint within 24 hours and resolve it within 15 days. The full procedure is on our Grievance Redressal page.
