Privacy Policy & Terms of Service

Privacy Policy

Below is what personal data Clapper ("Clapper", "we", "us") collects, why we collect it, who else touches it, how long it survives, and what you can make us do with it. It covers the Clapper website and the web app at clapper.in.

1. Who is responsible for your data

Clapper is an independent software project, operated from India. We act as the data controller for the limited account and usage data described below. Any privacy question, correction, or deletion request goes to purohit.krick@gmail.com.

The operator's full legal identity and postal address are provided on request to any user, regulator, or authority that asks for them.

2. The most important point: your production data stays on your device

Clapper is offline-first. Your projects, scenes, shot lists, takes, clip numbers, camera setup notes, imported script PDFs and generated exports (PDF, Premiere XML, Resolve XML, CSV) are saved locally in your browser, in IndexedDB or local storage, on the phone or computer you are working on. That content is not uploaded to us. We cannot see it. That cuts both ways. Clear your browser storage or uninstall the app and the data is gone. Keep your own exports.

3. What we do collect, and why

We do not collect your name (beyond what Google returns with your email), phone number, location, contacts, or payment details. We build no advertising profiles of our own and we sell nothing to data brokers. We do run one third-party advertising tracker, the Meta Pixel, and the next section sets out exactly what it does and how to stop it.

4. Advertising measurement: the Meta Pixel

Clapper is free and has no budget for a marketing department, so we run ads on Instagram. To know whether an ad brought a working crew member or just burned money, this site and the app load the Meta Pixel, a small piece of tracking code from Meta Platforms (Facebook and Instagram). That is genuine third-party ad tracking. We would rather say so plainly than bury it.

What the Pixel sets

• _fbp, a first-party cookie holding a random browser ID. It is what lets Meta recognise the same browser across visits and match it back to an ad. It is set on every visit, ad or not, and typically expires about three months after your last visit.
• _fbc, set only if you arrived by clicking one of our ads, because the ad link carries a click identifier (fbclid) in the URL. It records which click brought you. Same rough lifetime.

What is sent to Meta

• A page view each time you open a page on this site or in the app: the URL, the referring page, your browser and device type, and your IP address (Meta receives this by virtue of the request).
• A handful of product milestones, so we can tell a curious visitor from someone who actually used the thing. An event when a project is created, an event when a file is exported, and a few similar counts.

What is never sent to Meta

• Nothing from your script or shot list. Not a scene, not a line of dialogue, not a slugline.
• No project names, no file names, no clip numbers, no take data, no tags, no notes.
• No email address, no name, and no Google account identifier. We do not use Meta's Advanced Matching, so we do not hand Meta hashed contact details either.
• Nothing at all from the PDF, XML, or CSV you export. Those files are built on your device and never pass through Meta.

The milestone events are counts, not contents. "A project was created" is the whole message. Which project it was, and what is inside it, we could not tell Meta even if we wanted to, because it never leaves your device.

How to switch it off

All of these work, and none of them break Clapper. Logging takes, Script Mode, and every export keep working with the Pixel fully blocked. It does nothing except report to Meta.

• Use a browser that already blocks it. Safari (Intelligent Tracking Prevention) and Firefox (Enhanced Tracking Protection, on by default) restrict or bin these cookies without you doing anything. Brave and DuckDuckGo's browser block the Pixel outright. On Chrome, the Pixel runs unless you stop it.
• Install a content blocker. uBlock Origin, AdGuard, or Privacy Badger block the Pixel script before it loads. On iOS, any Safari content-blocker app does the same.
• Block or clear the cookies. In your browser's settings, block third-party and cross-site tracking cookies, or clear site data for this domain. Clearing site data will also clear your Clapper projects, so export first.
• Turn off ad tracking inside Meta. In the Facebook or Instagram app, open Settings → Accounts Center → Your information and permissions → Your activity off Meta technologies. From there you can see what sites have reported activity about you, disconnect it from your account, and switch off future activity. Ad targeting itself is at facebook.com/adpreferences.

Be clear about what each one buys you. Blocking the script or the cookie stops the data reaching Meta from your browser at all. The Meta-side controls are different: they mostly stop the data being used to target ads at you, and Meta may still receive and count it in aggregate. If you want none of it to leave your browser, use a blocker.

The Pixel is on the marketing site, the app, and our free template pages. If we ever add another advertising or analytics tracker, it will be named on this page before it ships.

5. Who processes data on our behalf (sub-processors)

• Google (Sign-in with Google) authenticates you and gives us your email address. Google's own privacy policy governs that.
• Supabase is our backend host. It stores your account email, your export counters, and anonymous usage events.
• Cloudflare (Turnstile) runs a privacy-friendly bot check when a gated action starts, to stop automated abuse. It is not an advertising cookie.
• Groq is an AI inference provider we use only in Script Mode, to extract scenes from the screenplay text you import. It processes that text to return the result and does not receive your account details.

We share the minimum necessary with each and do not sell personal data to anyone. Meta is deliberately not on this list. Meta does not merely process pixel data on our behalf. It also uses that data for its own advertising purposes, which makes it an independent recipient rather than a sub-processor. See Advertising measurement.

6. How long we keep it

• Account email & export counters: kept while your account exists, deleted when you ask us to delete your account.
• Anonymous usage events: deleted automatically after 90 days.
• Rate-limiting records: deleted automatically within minutes.
• Meta Pixel cookies: stored in your browser, not by us, and typically expiring about three months after your last visit. You can delete them sooner at any time. How long Meta keeps what it has already received is set by Meta's own retention policy, not ours.
• On-device data: controlled entirely by you, on your device.

7. Your rights

Under India's Digital Personal Data Protection Act, 2023 and, where applicable, the EU/UK GDPR, you may:

• Ask what personal data we hold about you and get a copy;
• Correct inaccurate data;
• Have your account and associated data deleted;
• Withdraw consent (e.g. by signing out and stopping use of gated features);
• Object to advertising tracking. You do not need to email us for that one. Blocking the Meta Pixel in your browser takes effect immediately and is more reliable than asking us to do it. See Advertising measurement.

To delete your data: email purohit.krick@gmail.com from the address you signed in with, or with the subject "Clapper data deletion request." We will delete your account email, profile, and export counters. We will confirm within 30 days. On-device data is removed by clearing your browser storage or uninstalling the app.

8. Security

Data in transit is encrypted over HTTPS. Backend tables use row-level security, so a signed-in user can only read their own row, and the authoritative counters are written only by trusted server code. No system is perfectly secure. What we can do is hold very little, and we do.

9. Children

Clapper is a professional tool intended for film and video crews and is not directed at children under 13 (or the equivalent minimum age in your country). We do not knowingly collect data from children.

10. International transfers

Our sub-processors may process data on servers outside India. Where that happens, we rely on the provider's own safeguards and transfer only the limited data described above. The same goes for Meta, which receives pixel data on infrastructure outside India, principally in the United States, under its own transfer safeguards. If you would rather that did not happen, block the Pixel. See Advertising measurement.

11. Changes to this policy

If we make material changes we will update the "Last updated" date at the top of this page. Continued use after a change means you accept the updated policy.

Terms of Service

Use the site or the app and you agree to what follows. If you do not agree, please do not use Clapper.

1. What Clapper is

A free, phone-first tool for logging takes, numbering camera clips, and exporting shot logs and editing timelines. Some features, namely Script Mode and Premiere and CSV export, require a free Google sign-in. Logging takes and PDF export do not.

2. Your licence to use it

We grant you a personal, non-exclusive, non-transferable, revocable licence to use Clapper for your own film, video, and production work, including commercial productions. You may not resell, sublicense, reverse-engineer for a competing product, or use Clapper to break the law.

3. Your content is yours

You keep every right to the data you create in Clapper: your shot logs, notes, scripts, and exports. Because that content lives on your device, backing it up is your job. We claim no ownership over it.

4. Acceptable use

• Don't attempt to overload, probe, or circumvent the service's rate limits or quotas;
• Don't upload content in Script Mode that you don't have the right to process;
• Don't use Clapper for anything unlawful.

5. Free service, availability, and changes

Clapper is provided free of charge. We may change, limit, suspend, or discontinue any feature (including the free tiers, Script Mode, or exports) at any time, and we don't guarantee uninterrupted availability. Beta and AI-assisted features, such as Script Mode scene extraction, may produce imperfect results. Always verify clip numbers and exports against your actual media before you rely on them.

6. Limitation of liability

To the maximum extent permitted by law, Clapper and its operator will not be liable for any indirect, incidental, special, consequential, or punitive damages, or for lost footage, lost data, lost profits, or production delays, arising from your use of or inability to use Clapper. Because Clapper is provided free of charge, our total aggregate liability to you is limited to the amount you paid us to use it, which is zero. Some jurisdictions don't allow certain limitations, so parts of this may not apply to you.

7. Termination

You may stop using Clapper at any time and request account deletion. We may suspend or terminate access if you breach these Terms or misuse the service.

8. Governing law

These Terms are governed by the laws of India, and the courts at Ahmedabad, Gujarat shall have jurisdiction, subject to any mandatory consumer-protection rights you have where you live.

9. Contact

Questions about these Terms: purohit.krick@gmail.com.

Cookies & Storage Notice

Most of what Clapper stores in your browser exists only to make the app work. One item is advertising: the Meta Pixel cookie. It is listed below as such.

Strictly necessary

• Local storage / IndexedDB: stores your projects and takes on your device so the app works offline. Never sent to us.
• Sign-in session: if you sign in with Google, a session token is stored locally so you stay signed in. Cleared when you sign out.
• Cloudflare Turnstile: may set a short-lived token when a gated action runs, purely to confirm you are not a bot. Not an advertising cookie.

Advertising

• _fbp (Meta Pixel): a random browser ID that lets Meta recognise this browser and match it to one of our ads. Set on every visit; typically expires about three months after your last one.
• _fbc (Meta Pixel): set only when you arrive by clicking one of our ads, recording which click brought you.

These two are neither strictly necessary nor user-initiated: the app works perfectly with them blocked. Section 4 of the Privacy Policy sets out exactly what they send, what they never send, and several ways to switch them off.

Clapper does not currently show a cookie-consent banner. You can clear or block any of the above at any time from your browser settings, or with a content blocker. Note that clearing site data for this domain will also wipe your Clapper projects, so export first.

Contact

Clapper is an independent software project, operated from India.
Email: purohit.krick@gmail.com

For data access or deletion, email from the address you signed in with, or include the subject line "Clapper data deletion request."

The operator's full legal identity and postal address are provided on request to any user, regulator, or authority that asks for them.