Privacy Policy

Wørkit (“wørkit”, “we”, “us”) is a delivery platform on which an organisation runs its internal projects and its client engagements. This policy explains what personal data the platform handles, why, and what choices you have.

It covers wørkit.com and the per-organisation workspaces hosted on its subdomains. It does not cover any third-party product your organisation chooses to connect, which remains governed by that provider’s own terms.

The distinction below determines who you should ask about your data, so it comes first.

• Workspace content — your employer decides. Projects, tasks, messages, documents and everything else created inside a workspace belongs to the organisation that owns that workspace. They decide who joins, what is stored and how long it is kept. We process it on their instructions. If you are an employee asking to see, correct or delete something in a workspace, your organisation’s administrator is the right first contact.
• Account and billing data — we decide. The records needed to run the platform itself (your sign-in identity, your organisation’s subscription) are ours to manage, and for these you can contact us directly.

• Identity. Name, email address and profile photo, from Google sign-in or from an email and password. Authentication is handled by Firebase Authentication; we never see or store your Google password.
• Workspace profile. Job title, department, reporting line, skills, capacity and similar fields, entered by you or your administrator.
• Workspace content. Projects, tasks, milestones, messages, notes, whiteboards, uploaded documents, approvals and agreements — including anything you choose to put in them.
• Activity records. Audit entries and activity feeds recording who changed what and when, plus presence (whether you are currently online) so colleagues can see who is available.
• Connected-service data. Only what the connection you authorised requires — see sections 4 and 5.
• Billing. Subscription plan, seat count and invoice history. Card details are entered directly with our payment processor and never reach our servers.
• A session cookie. One first-party cookie (firebase_session) holding your signed session so the server can tell it is really you. The server issues it with HttpOnly, Secure in production, and SameSite=Lax protections. It expires after five days and is not used for tracking.

Note editors keep unsaved drafts in this tab's session storage so a failed save or note switch does not discard your work. Drafts are removed after a successful save or sign-out; closing the tab ends this temporary browser storage. Conflicting edits remain available to copy or download.

If you connect your Google account, wørkit reads your calendar so your meetings appear alongside your tasks. This is optional, personal to you, and separate from your organisation’s other settings — an administrator cannot connect it on your behalf.

What we ask for, and why

• openid, userinfo.email, userinfo.profile — to record which Google account you linked, so the settings page can show it and you can confirm you connected the right one.
• calendar.events.readonly — to read events from your calendar and display them on your wørkit calendar. This is the narrowest Google Calendar permission that works: it covers events only, not your calendar settings or sharing rules, and it cannot create, edit or delete anything.

How it is handled

• Events are fetched on demand for the month you are viewing and rendered in your browser. We do not copy your calendar into our database or build a mirror of it.
• Your calendar is visible only to you. Colleagues, administrators and your organisation’s owner cannot see it, and there is no view anywhere in wørkit that shows one person’s calendar to another.
• You can choose to share an individual meeting into a wørkit conversation. That posts a copy of that one meeting’s title, time, location and joining link as a message — it grants no access to your calendar, is never automatic, and covers only the meeting you picked. Attendee lists and email addresses are not included.
• Some conversations are shared with another organisation (a B2B project involving a client or partner). Sharing a meeting into one of those discloses it to that organisation’s members. wørkit names the organisation on the button before you post, so the destination is never a surprise.
• Access tokens are stored encrypted at rest in an isolated, server-only store that no browser and no other user can read, and are used solely to make the calendar request described above.

What we never do

• We never write to, modify or delete anything in your Google account.
• We never sell, rent or trade Google user data, under any circumstances.
• We never use Google user data for advertising, profiling or marketing.
• We never use Google user data to train, fine-tune or evaluate any artificial-intelligence or machine-learning model, our own or anyone else’s.
• No human at wørkit reads your calendar. The narrow exceptions permitted by Google’s policy — your explicit request for support, a security investigation, or a legal obligation — are the only circumstances in which a person could access it.

Disconnecting

You can disconnect at any time from your wørkit Settings page or the Calendar page. Disconnecting revokes our access at Google and deletes the stored token immediately. You can also revoke it from your Google account permissions page, which takes effect straight away.

An administrator may connect other products to a workspace. Each is optional, each can be disconnected, and disconnecting deletes the stored credential rather than keeping it for later.

• Slack, Microsoft Teams. We send notifications outward — task assignments, missed deadlines and similar. We do not read your message history; the permissions we request deliberately exclude it.
• GitHub. Reads repository branches and commits so they can be linked to tasks.
• Jira. One-way import of issues into wørkit tasks. We only ever read.
• Your own AI provider. If your organisation supplies its own OpenAI or Anthropic key, limited task and roster summaries are sent to that provider to phrase a digest or explain a suggestion. Decisions are made by our own code; the model only writes the wording. Nothing is sent anywhere unless your organisation connects a key and switches the feature on.
• Your own storage bucket. An organisation may direct file uploads to storage it controls, in which case those files never sit on our infrastructure at all.

• To provide the platform: showing your work, your colleagues’ work and your schedule.
• To authenticate you and keep accounts secure.
• To notify you about things that change what you should do next.
• To bill your organisation and support its administrators.
• To investigate abuse, debug faults and keep the service running.
• To meet legal obligations.

We do not sell personal data. We share it only with the infrastructure providers who run the service on our behalf, under contract:

• Google Cloud / Firebase — authentication, database, file storage and hosting infrastructure.
• Vercel — application hosting and delivery.
• Razorpay — subscription payments. They receive billing details directly; we receive a payment result, never your card number.
• Any product your own organisation chooses to connect (section 5), which receives only what that connection needs.

We may also disclose data where legally compelled, or to protect the rights and safety of our users, and, if wørkit is ever acquired or merged, as part of that transaction, with notice to you beforehand.

Workspace data, files and our application servers are hosted in Mumbai, India, and live presence runs in Singapore. Sign-in runs on Firebase Authentication, a global service, and our other subprocessors and any products you connect process data in their own regions, which may be outside your own country. Transfers rely on the safeguards those providers offer, including standard contractual clauses where applicable.

• Workspace content: for as long as your organisation keeps its workspace. If an administrator closes it, we delete it 30 days later, and copies in our daily backups are overwritten within a further 14 days.
• Notification records: automatically deleted 60 days after they are created.
• Connected-service tokens: until you or an administrator disconnects, at which point they are deleted immediately.
• Desktop sign-in codes: the one-time code that carries a sign-in from your browser to the wørkit desktop app expires five minutes after it is issued, and is void the moment it is used.
• Audit records: retained for the workspace’s lifetime, since their purpose is accountability over time.
• Exports: generated when an administrator asks for one and sent straight to their browser. We keep only a count of exports taken, to apply fair-use limits, never the file itself.
• Billing records: retained as long as tax and accounting law requires, after the subscription ends.

Credentials are isolated from ordinary workspace data and are never readable by a browser; every organisation’s data is separated by enforced access rules; and all traffic is encrypted in transit. Our Security page describes the specific measures in detail.

Depending on where you live, you may have the right to access, correct, export, delete or restrict processing of your personal data, to object to processing, and to complain to a data protection authority.

For anything inside a workspace, contact your organisation’s administrator first — they control that data and can act immediately. For account-level data, or if your administrator cannot help, write to us at monikmalik.w.007@gmail.com. We respond within 30 days.

You can disconnect any connected account yourself at any time, without asking anyone.

Wørkit is a workplace product, not intended for anyone under 16. We do not knowingly collect data from children. If you believe a child has an account, contact us and we will remove it.

If we change this policy materially we will update the date at the top and notify workspace administrators before the change takes effect. Continuing to use wørkit afterwards means you accept the revised policy.

Questions, requests or complaints: monikmalik.w.007@gmail.com.