WorkKit Privacy Policy
WorkKit is made by GroupWork LLC ("we"). This policy explains what WorkKit does with your information.
What stays on your phone. When you use WorkKit's tools, the photos, videos, receipts and documents you choose are processed on your phone. We never upload them, never see them, and never store them — unless you attach one to a support ticket, or, while signed in, save one as a Contact Editor template or as the logo on your saved Scanner title page (below). Your expense reports, Photo PDF drafts, saved places, and the index Photos by Place keeps of where and when your photos were taken stay in WorkKit on your phone and are removed when you delete the app. Files you save go to your phone's photo library or Files; files you share go only where you send them. Your phone's own backup (iCloud or Google) may include what you save, as it does for any app.
Photos, camera and location. WorkKit asks for access only when you use it: your photo library when you choose photos or a video, or when Photos by Place looks for photos taken near a place you saved (it reads the location and time stored in those photos, on your phone); the camera when you take a photo or scan a receipt; and your location only when you tap Use Current Location to save a place. If you search for an address, the address you type is sent to Apple's map service (on Android, your phone's) to find it. You can change these permissions at any time in your phone's Settings.
Contacts. Contact Editor asks for access to your contacts when you open it. It lists your contacts on your phone so you can pick which ones to update, and it changes only the photo and company of the contacts you choose. Your contacts are never uploaded.
Reading receipts. When you ask WorkKit to suggest a label for a receipt, it reads the receipt's text on your phone. The text is not sent anywhere.
Sharing to WorkKit. Photos, videos and PDFs you share to WorkKit from another app wait in WorkKit's Inbox, on your phone, until you use or delete them.
Employer expense policies. If your employer has arranged it with GroupWork and you sign in with a work email address it has confirmed, WorkKit shows an Expense Policy helper. WorkKit downloads your employer's policy to your phone to answer your questions; your questions and receipts stay on your phone.
If you sign in (optional). You can use WorkKit's tools without an account. If you sign in with a GroupWork account, we store: your name, email address, company (if you add one), profile photo (if you add one), a user ID, your WorkKit settings (such as your theme, week start and tool defaults), your Contact Editor templates (a label, a company name and a photo), and your saved Scanner title page (a company name, a name, a short note, a colour and a logo), so they appear on your other devices. Your scans themselves stay on your phone. Signed out, templates and the title page stay on your phone. Deleting a template, resetting the title page or deleting your account removes it. This is the same account you use for other GroupWork apps, so your name and profile photo appear there too. We use this information to run your account, sync your settings, and answer the support tickets you send. Account data is stored with our database provider (Supabase); profile photos are stored with Cloudflare and shown through short-lived private links.
Terms agreement. When you agree to our Terms of Service in any GroupWork app, we record which version you agreed to, in which app, and when. It is kept with your account so another GroupWork app does not ask you again, and it is deleted when you delete your account.
Support tickets. If you're signed in, you can send us a ticket from Support → Report a Problem. A ticket contains what you write, the category you pick, any screenshots or photos you attach, your account ID, and — if you leave them switched on — your name and email. It also includes a technical report about the app: the app and operating-system versions and which update is running, device model, screen size, text size and theme, language and time zone, whether you're online, whether you're signed in and how long the app has been open, how many files wait in your Inbox (a number, never the files), the names of the screens you visited recently (never what was on them), recent error messages, and the ID of the last crash report WorkKit sent. We try to remove file names, amounts, places and email addresses from error messages before they're included, but we can't promise every message is free of them or of other text. Because a ticket carries that crash-report ID, that crash report — and other crash reports from the same phone, which our crash-reporting provider can group together — including the approximate city it works out from your connection, can be connected to your account. Photos you attach are sent without their location or other embedded details. Tickets are stored with our database provider (Supabase) and are used only to fix problems and reply to you. To help us respond faster, a ticket — its text, category, account ID, technical report and any attached images — is processed by Anthropic's Claude AI, which classifies it and drafts an internal summary for us. To do that it may also count other support tickets that report the same problem (it cites their numbers but never copies their text into yours) and read the crash reports connected to your ticket or from the same app version. In that review it does not use your name or email address and receives nothing else from WorkKit or your account (the coding tool under "Building and fixing WorkKit" is separate). Tickets are kept while we work on them and as product history; ask us to delete yours at privacy@groupwork.cloud.
If you can't sign in. The sign-in screen has a "Trouble Signing In? Contact Support" link. A report sent from it contains what you write, your email if you give one, and the same technical report a ticket carries; it has no account ID. It is stored, used and processed exactly like a ticket, including by Anthropic's Claude AI. Ask us to delete it at privacy@groupwork.cloud.
Building and fixing WorkKit. Our developers also use Anthropic's Claude as a coding tool, and that tool can access our systems, including our database. That database holds what WorkKit keeps on our servers for a signed-in account: your profile, your synced settings, your Contact Editor templates, your saved Scanner title page, and your support tickets and the photos attached to them. The files you work on in WorkKit's tools stay on your phone and are not in it. We reproduce problems and test fixes on test accounts with made-up data wherever we can, and investigating a problem can involve reading records from the account that reported it. We are working to narrow this access to the minimum a problem requires. Anthropic does not train its models on what we send (we turned that off) and keeps it under its own terms.
Approximate location (from your network, not GPS). When you send a support ticket, or a report from the sign-in screen, we record the approximate location of the network you send it from: the country, and outside the European Union, the rest of the European Economic Area, the UK and Switzerland also the region, city and network provider (for example "Columbus, Ohio · Spectrum"). Our servers and Cloudflare work it out from your connection — never from your phone's GPS or location setting. We use it only for support and troubleshooting, for account security, and for overall usage statistics. It is never sold, never used for advertising or to profile you, never shown to other users, and never sent to the AI service that helps us read tickets. GroupWork's support staff can see it, as can the providers that store or process it for us (Supabase and Cloudflare), under contract and for no purpose of their own, and the AI coding tool described under "Building and fixing WorkKit". Region, city and provider are deleted automatically after 90 days; the country stays with the ticket.
Crash reports. If WorkKit crashes, it sends a report so we can fix the problem, through our crash-reporting provider (Sentry). Reports contain technical details — the app version, the device model and operating system, and where in the code the problem happened. Reports from the app's built-in code also carry a random ID that our crash-reporting provider creates for each installation of WorkKit. It identifies the installation, not you, and a reinstall gets a new one. They do not include your name, email, account, photos, videos or file names, and we remove those details before a report leaves your phone. If you send a support ticket, it carries the ID of your latest crash report, which connects that report to your account. WorkKit does not add your location to a crash report, but a crash report may include an approximate location (city) that Sentry works out from the IP address of the connection it arrives on. Crash reports are deleted after about 30 days.
Anonymous usage counts. To see how WorkKit is used, it counts app opens and which tool was opened, through our analytics provider (PostHog). To tell installs apart, the app keeps a random anonymous ID that is removed when you delete the app. These counts are not connected to your account, name or email, and do not include your location. They are kept for up to 7 years under our analytics provider's retention period. WorkKit does not collect these counts in the European Economic Area or the United Kingdom. Support tickets never include this ID.
On Android. Reading a receipt and scanning a document use Google's ML Kit on your phone: your photos, scans and their text stay on your phone. ML Kit sends Google anonymous technical information — your device model, Android and app versions, how long a task took and any error codes, with an ID for this installation that isn't tied to you or your account — which Google uses to run and improve the service.
What we don't do. No advertising. No tracking across other companies' apps or websites. We don't sell or share your information for advertising.
Deleting your account. In WorkKit, open Account → Delete Account. Deletion covers your whole GroupWork account in every GroupWork app. You have 30 days to change your mind by signing back in; after that your GroupWork account — the one login you use in every GroupWork app — is permanently deleted, together with the data WorkKit keeps for it (your settings, Contact Editor templates and saved Scanner title page). Our database is backed up daily: each copy is kept for 30 days and then deleted, and OneDrive keeps a deleted copy in its recycle bin for up to 30 more days before erasing it, so a deleted account is gone from our backups within a further 60 days. That is separate from any backup of your own phone. You can also start from the web: https://groupwork.cloud/workkit/delete-account. Support tickets you sent are not deleted with your account: they keep what you wrote, anything you attached, and the name and email they were sent with. Ask us at privacy@groupwork.cloud to delete them.
Children. WorkKit is not directed to children under 13.
Changes. If this policy changes, we'll update the date above and, if you have an account, let you know with a notification in the app.
Contact. questions@groupwork.cloud