Home › Privacy Policy
Privacy Policy
Last updated: 20 October 2026 · Effective immediately
Template notice. This policy describes how the software actually handles data today. Before you sell paid plans, have it reviewed by a lawyer for the jurisdictions you serve (for example GDPR in the EU/UK, or the applicable data-protection law where you are based).
1. Who we are
TeamControlSheet (“we”, “us”, “our”) provides a web application for team task tracking, review, approval and performance ratings. For any privacy question, or to exercise a right described below, contact us at [email protected].
Where a workspace is created by an organisation (for example your employer), that organisation is the data controller for the workspace content and we act as its data processor. Your Team Leader is the first point of contact for access to your data.
2. What we collect
- Account data — your email address (the identity you sign in with), display name, designation, avatar image, role and reporting line. A short username is derived from your email automatically for use in task assignments and chat; you never choose or share it.
- Authentication data — your password is handled entirely by Supabase Auth and a refreshable session token is issued to your browser. We never receive, store or log your raw password in application tables or in browser storage.
- Workspace content — tasks, descriptions, comments, attachments, ratings, chat messages, deadlines and the append-only audit history your team creates.
- Technical data — last-seen timestamp (used for presence and to explain delays), plus error messages produced by the browser that help us diagnose failures.
- Optional Outlook import — only the emails you explicitly select are copied into tasks, together with their attachments and a link back to the message. Access is read-only and we never receive your Microsoft password.
We do not collect payment-card data (no paid plans are currently live) and we do not use advertising or behavioural tracking cookies.
2a. How registration works
- You register with your own email address and choose your own password. No email verification step is required — you are signed in immediately.
- There is no default, demo or shared account anywhere in the product, and no password is ever issued to you by anyone else.
- The first person to register creates the workspace and becomes its Team Leader. Everyone else joins with an invite link and stays pending until a Team Leader approves them.
- If you forget your password, Supabase emails you a one-time reset link. A Team Leader can retrigger that link, but never sees or sets your password.
3. How we use it
Only to provide the service:
- showing tasks to the people entitled to see them;
- sending you the reminders, nudges, escalations and digests you have configured;
- producing reports and performance analytics for your Team Leader;
- diagnosing faults and keeping the service secure.
We do not sell personal data, do not use your workspace content for advertising, and do not use it to train third-party models.
4. Who can see your data
Data is isolated per workspace at the database layer. Inside a workspace, access follows roles:
| Data | Visible to |
|---|---|
| Work tasks and their history | Approved members of that workspace |
| Personal tasks | Only their owner — not the Team Leader, not other members |
| Performance ratings | Team Leader and the named approver only |
| Direct messages | The two participants in that conversation |
| Profile and roster | Approved members of the same workspace |
These boundaries are enforced by database row-level security policies, not only by the interface.
5. Processors we use
- Supabase — PostgreSQL database, authentication and file storage. All workspace data rests here.
- Hosting provider — serves the static application files; it does not receive workspace content.
- Email delivery provider — used only if a daily digest is enabled, and only to send the address you supplied.
Each processor handles data on our written instructions and under its own data-processing agreement.
6. International transfers
Our infrastructure may store data in regions outside your own. Where that happens we rely on the processor’s standard contractual clauses or an equivalent lawful transfer mechanism.
7. Security
- All traffic is encrypted with TLS.
- Row-level security is enabled on every table, so a request can only ever reach its own workspace’s rows.
- Passwords are handled by the authentication provider using industry-standard hashing; they never enter application tables.
- Role changes — granting Team Leader, approving a member, changing a reporting line — are restricted at the database level.
- Self-review and self-approval of your own work are rejected by the database, preserving the integrity of the audit trail.
No system is perfectly secure. If we become aware of a breach affecting your data we will notify the workspace owner without undue delay.
8. Retention
Workspace content is kept while the workspace is active. Audit history is append-only by design, because its purpose is to be a reliable record. A Team Leader can remove a user at any time; a workspace owner can request full deletion of the workspace and all of its content.
When a Team Leader removes you from a workspace, your workspace profile is deleted and you immediately lose access to every task, file and message in it. Your login record remains in the authentication system but is attached to no workspace and can reach no data. To have the login record itself deleted, email us.
9. Your rights
Depending on where you live you may have the right to access, correct, export, restrict or delete your personal data, and to object to certain processing. Because most data belongs to your workspace, the fastest route is through your Team Leader. You may also email [email protected] and we will respond within 30 days.
10. Children
TeamControlSheet is a business tool intended for users aged 18 and over. It is not directed at children.
11. Cookies and local storage
We use no advertising or analytics cookies. The application stores:
- a session token in browser storage so you stay signed in;
- your day/night theme preference;
- a service-worker cache so the app can load quickly and work offline.
Clearing your browser storage removes all three and signs you out.
12. Changes to this policy
We will post any change on this page and update the date at the top. Material changes affecting how we use workspace content will be announced inside the application.
13. Contact
TeamControlSheet · [email protected]