Privacy
SensWit Privacy Statement
Applies to senswit.com and the SensWit web app.
This statement says what SensWit stores, why, who else sees it, and how you make it stop. It covers creators, agency users, and brand guests.
SensWit is a decision workspace. You accept a bet, ship a pack, and keep the receipt. We store that decision. We do not run an advertising network, and we do not sell personal data.
1. Who is responsible
The controller is [legal entity name], [registered address], India.
Privacy requests: connect@senswit.com, subject line “Privacy”.
2. What we store
| Data | Why |
|---|---|
| Name, email, login from Google, workspace role | To open an account and seat you in a Room |
| Channel or client you connect, with your permission | To scope the Room |
| Bets, packs, decisions, brand law, claim locks, approvals | To run the product |
| Transcripts, hooks, beat notes, thumbnail frames, content hashes | To compile a pack and later show a receipt |
| Schedule row: platform, time, hash, remote id | To post at the time you set |
| Support mail you send us | To answer you |
| Security logs: account id, room id, time, IP, user agent | To keep the service up and investigate abuse |
A creator channel is one Room. An agency client is one Room. A member of one Room does not receive another Room’s name, copy, or file. A request for a Room you are not in returns not found.
3. What we do not store
- Camera masters and project files. Those stay with you.
- A copy of your YouTube catalogue. A scheduled YouTube video stays on YouTube. We keep the video id and the hash.
- A working cut after the platform has accepted the post. If a cut must pass through our storage, it is deleted when the platform returns an id, and in any case within 90 days. The hash and the decision remain.
- Payment card numbers. A payment processor holds those.
- Advertising profiles. We do not sell data and we do not build ads on your content.
4. Why we use it
- To provide the account, the Room, the pack, and the schedule you asked for.
- To keep Rooms separate, block a claim you locked, and record who approved a pack.
- To secure the service, prevent abuse, and debug a failure.
- To send service mail. Product mail is optional and separate.
- To meet a legal duty, if one applies.
We do not train foundation models on your packs, transcripts, or cuts. A pattern, if the product later stores one, is a type — hook shape, offer shape — and not your name, script, face, or file.
5. Who else sees it
| Party | Why |
|---|---|
| Sign-in, and YouTube only if you connect a channel | |
| Cloudflare | Security and access in front of the app |
| Object storage (Cloudflare R2 or equivalent) | Thumbnails, transcripts, and a working cut until post |
| A model provider | A compile call for your Room only. The call is not a licence to train on your content |
| An agency admin of your workspace | Seats and law for Rooms they control. Not another client’s assets |
| Authorities | If the law requires it |
We do not sell personal data. We do not share a Room with another customer.
6. How long
- Account data: while the account is open, then deleted or de-identified within 30 days of a verified deletion request, unless a law says keep it.
- Decision records you exported: yours.
- Working cuts: deleted on successful post, or within 90 days.
- Security logs: 90 days, unless a longer hold is needed for an incident.
- Backups: overwritten on the backup cycle, not kept as an archive.
7. Your rights
You may ask to access, correct, export, or delete your account data, and to withdraw a permission you gave. Email connect@senswit.com. We may need to confirm it is you.
If you are in India, you may also use the rights under the Digital Personal Data Protection Act, 2023, including consent withdrawal and nomination where it applies. If you are in the EEA or UK, you may object, restrict, or complain to a supervisory authority. The contract is the basis for the account and the Room. Consent is the basis for an optional channel connection and for optional mail.
Deleting an account deletes the Rooms you own. It does not delete another customer’s Room. An agency must not ask us to delete a client’s data that the client, not the agency, controls. That request has to come from the client or from a person the client named.
8. Children
SensWit is not for anyone under 18. We do not knowingly create accounts for children.
9. Security
Access to a Room is checked on every read. Publish on an agency Room requires an approver who did not compile the pack. Logs store ids, not scripts. No control is perfect. If we learn of a breach that risks your data, we will tell you and, where the law says so, the authority.
10. Changes
If this statement changes in a way that matters, we will post the new date here and, if you have an account, email the address on it.