Privacy Policy
WorkspaceRadar · Last updated: 20 November 2026
This policy explains what WorkspaceRadar ("we", "the app") reads from your Google Workspace domain, what we keep, for how long, and who sees it.
1. Who we are
WorkspaceRadar is operated by Xinru Tang, a sole trader, Möwenweg 5, 91056 Erlangen, Germany (Impressum). Contact for anything in this policy: contact@workspaceradar.com.
2. Two kinds of data, two roles
- The administrator's sign-in identity. This is the email address of the administrator who signs in with Google, which we use to sign them in, to know who connected the domain, and to tell the administrator who connected it about a personal data breach or before the domain is deleted for inactivity (section 5). We decide why we use it, so for this data we are the controller.
- Data about the people in your Workspace domain. This is their directory details and usage timestamps (section 3). Your organisation decides to have it analysed, so your organisation is the controller and we process it on your organisation's behalf, under our Data Processing Agreement. Administrators are people in your domain too, so this includes their own directory details and usage, and any record the app keeps for your organisation about an administrator's actions in it (who entered a price, who decided one of the agent's proposals, who switched one of its emails on).
3. What we read from Google, and what we change on your approval
When an administrator connects the app, Google asks them to grant these permissions. We use each one only for the purpose shown.
| Permission (Google scope) | What we read or change | Why |
|---|---|---|
admin.directory.user.readonly |
Each user's email address, organisational unit, whether the account is suspended or archived, when it was created, when it last signed in, and whether it is an administrator or a super administrator, and whether the account has ever completed a first sign-in and must change its password at the next one | To list the licensed accounts being assessed, and to show who the administrators are on the Security screen |
admin.reports.usage.readonly |
Per-user usage reports: when each person last used Gmail and Drive, and when they last read mail in a mail app (IMAP or POP) or in Gmail on the web, counts of emails sent and received, files created, and Chat activity counts; and account security facts: 2-step verification status, number of admin roles, number of third-party apps, Google's password strength and length labels, and less secure app access; and the domain's total storage use (one figure for the whole domain); and, for suspended accounts that still hold a licence, how much storage the account uses (one figure per account) | To decide whether a licence is actually being used, to spot paid seats that look like shared role mailboxes, to show the Security screen, to check whether a cheaper edition would fit, and to tell you what a suspended account still holds before you release its licence |
admin.reports.audit.readonly |
For people who hold a Gemini add-on: when they used Gemini (number of uses and the latest time). From the sign-in audit log: who turned on forwarding of their mail to an address outside your domain, when, and the domain of that address (we keep only the domain, never the address itself). Whether anyone used Google Vault in the last six months (yes or no, no details). Admin log. A fixed list of 42 Admin console events from Google's admin audit log, each requested by name: account suspension, deletion, archiving and renaming; offboarding steps (data transfer requests, mail routing, token revocation); admin privilege and role changes; email monitors and mailbox export requests; 2-step verification and app access settings; apps given domain-wide access and Marketplace apps installed or removed; automatic licence assignment; and application setting changes. We keep the event, its time, the account that made it and the account it concerns (as our own record of that account, not as an address), and, as the event needs, a few short facts: for app, Gmail and email settings, their names only, never their values; for sign-in and licensing settings (such as enforcing 2-step verification or automatic licence assignment), their short on/off or level value; the allowed 2-step verification method; the name of a trusted or Marketplace app or an API client, how many access scopes it was given and, if short, the scope list; product and licence names; an email monitor's end date; the names of the apps in a data transfer request; the organisational unit a setting applies to; and whether a role is the super administrator role. Addresses outside your accounts (a mail route's or monitor's destination) are reduced to their domain. We never keep IP addresses, role names, app, Gmail or email setting values, mailbox export search terms or text an administrator typed into a rule's description. Kept for 180 days (setting changes 35 days), never longer than Google keeps the log, and deleted when you disconnect. The raw responses (below) hold the same events for 30 days, with the same cuts, except that the accounts named are kept as Google wrote them (below) | To show whether a Gemini add-on is being used, and to warn you about mail forwarded outside your domain; and, from the admin log, to show you what changed in the Admin console and each departing user's offboarding steps |
apps.licensing |
Which Google Workspace licence each user holds, including add-on licences such as Vault, Voice, AppSheet and Archived User, and, on your approval, releasing or re-assigning one | To price each licence, and to release or re-assign a licence when you approve that specific change |
openid, email, profile |
The signing-in administrator's identity | To sign you in |
What we never read: the content of anyone's email, files, calendar, chats, Gemini prompts or any other content. We never read a password, only Google's label about it (for example "strong").
About "View and manage Google Workspace licenses". Google offers only one licensing permission, and it is described as read and write. The app changes a licence or a user only when an administrator approves that specific change in the app; each change is checked against Google first and recorded with Google's response, kept 365 days (see section 4). Our build process fails if any other part of our code makes a changing request to Google.
4. What we keep, and why
| Data | Why we keep it | How long |
|---|---|---|
| Your domain's Google customer id and primary domain; the plan type, renewal date and billing currency you tell us; whether weekly scans are on; when we sent the warning before the deletion in section 5; for a paid plan, since when Google has refused our access, if it has | To identify your domain and show savings you can realise now vs at renewal | Until you disconnect, or 12 months without use (section 5) |
| The connecting administrator's email, and an access token that lets us scan again without you signing in (encrypted at rest) | To run the scans you ask for and, if weekly rescans are on, the weekly rescan; to carry out a change you approved; to warn that administrator before the deletion in section 5; for a paid plan, to check once a day that Google still accepts our access, and to tell that administrator if the plan ends because it does not (section 5) | Until you disconnect, or 12 months without use (section 5) |
| Per-user directory details, licences, usage timestamps and counts, the resulting verdict and the licence cost | To produce the dormant-licence list, the savings figure and the history | 12 months, except that your two most recent completed scans are always kept. A person's directory details are deleted once no kept scan refers to them, no kept admin log event names them (at most 180 days) and no scan has seen them for 12 months |
| Per-user account security facts (listed in section 3) | The Security screen | Same as the row above |
| For Gemini add-on holders: number of Gemini uses and the latest time | The AI seats screen | Same as the row above |
| For people who turned on forwarding to an outside address in the last six months: their email, the outside domain and when | The Security screen | Same as the row above |
Actions (action_evidence): the change you approved, who approved it and when, and, for each check before it and for the change itself, the request we sent to Google and Google's response (the person's Google id, email address, suspended status and whether they are an administrator, or the licence assignment) |
To show what was changed, by whose approval, and what Google answered | 365 days |
The raw responses Google returned. We ask Google for only the fields listed in section 3, so these hold each user's Google id, email address, organisational unit, suspended and archived status, whether they are an administrator, creation and last sign-in time, licence, the usage and security values listed above, and, for Gemini add-on holders, records of when they used Gemini; forwarding records with the outside address reduced to its domain, and admin log events as Google sent them, cut to the facts described above (any other address in a kept value is reduced to ***@domain, but the administrator who made a change, even one outside your domain such as a reseller, and the accounts an event names are kept as Google wrote them, including an account that matches none of your users); never IP addresses, prompts or other content, names or other profile details |
So that every figure we show can be traced back to what Google said | 30 days, or until you disconnect if sooner |
| A price you entered to correct ours, and the email of the administrator who entered it | To use your price instead of the list price, and show who set it | Until you disconnect, or until you change the billing currency (prices in the old currency are deleted) |
| Admin log events (from the admin audit log, section 3): what was changed, when, by whom and to which account, with the short facts listed in section 3 | To show what changed in the Admin console and each departing user's offboarding steps | 180 days (setting changes 35 days), never longer than Google keeps the log, or until you disconnect if sooner |
| If you use the contact form: your name, email address and message | To answer you | Not stored by the app. Forwarded by email to our mailbox the moment you send it, and kept there until your request is dealt with, at most 12 months |
| If you use the contact form: your IP address | To stop abuse: at most 5 messages per address per hour | Held in memory for at most one hour, never written to the database or the logs |
| If your domain has started a paid plan (from the moment a checkout is opened): the Stripe customer and subscription ids, the subscription's status, its size and billing interval now and for the current period, renewal date and whether it is set to end, keyed by your Google customer id. No name, email address or card details: Stripe collects those itself | To know what you paid for, and to make sure a subscription ends when you disconnect | While the subscription runs, and until 30 days after it has ended if your domain is no longer connected; then deleted automatically. It is kept after you disconnect, so that a subscription still running is ended and never charged again |
| Database backups, containing all of the above | To recover from a failure | 7 days, after which they are overwritten (section 5) |
| Technical logs: internal record ids, error codes, error types and, for some errors, an error message and the code location where it happened. We do not write email addresses or anyone's data to them on purpose. A failed scan is logged with only the error type and where it happened, and our database is set not to include data values in its error messages | To run and fix the service | 30 days |
The agent's records and emails. When the agent is switched on, after each scan it keeps findings: situations it noticed, such as a licence nobody has used, a person without 2-step verification or mail forwarded outside your domain, each tied to the person's account record in the scan, with its cost where it has one. It keeps proposals: what it suggests doing about a finding, such as releasing one licence. Every proposal is decided by you; the app records who decided it, when, and any reason you typed, and it carries out a proposal only when you approve that specific one. It keeps the rules you give it (for example "never propose anything for this person") with who added them. Its emails, the weekly briefing and the other routines, go only to the administrator who switches one on, at their sign-in address, and stop with the unsubscribe link in every email; the one exception is a single sample briefing sent to the connecting administrator after their first scan, which names nobody. Names in email are off unless you switch them on in Settings: with them off, emails describe seats without anyone's email address. We keep each email (its recipient, text and delivery record) so you can see it under Activity: the text for 30 days, the record for 12 months. Findings are kept 12 months after they are resolved, decided proposals 12 months after the decision, the rest until you disconnect. The emails are sent through Amazon SES in Ireland. The sign-in session that keeps you signed in is stored in our database, and ends at the latest 12 hours after you signed in (section 7).
Weekly rescans. Weekly rescans are a paid feature (see the Terms of Service, section 4). The setting is on by default, and it takes effect while your domain is on the paid plan, or before charges start: the app then rescans your domain once a week so it can show what changed. You can turn it off on the History screen. With it off, or on the free plan, the app contacts Google for your domain only when you sign in or open the app (which starts a scan if none is recent and your plan allows one), when you start a scan, when a change you approved runs, and when the domain is disconnected. If nobody from your organisation opens the app for 90 days, weekly scans pause on their own, and they resume the next time someone opens it.
Contact form. The form asks only for your name, email address and message, and you choose what to write. We use them only to answer you; the legal basis is our legitimate interest in answering questions about the service, or steps towards a contract you asked for (Art. 6(1)(f) and (b) GDPR). The message is sent by email (Amazon SES) to our mailbox and is not kept by the app. The form uses no tracking and no third-party captcha: a hidden field and a per-address limit keep spam out. Please don't send us employee lists or other personal data about your users.
5. Deleting your data
In Settings → Disconnect this domain, the app first withdraws its access at Google, then deletes all your Workspace data it holds about your domain, every table included, in one step. Only the subscription record described below stays. If Google does not confirm the withdrawal, we still delete all your Workspace data, and we tell you to remove the app's access in your Google Admin console yourself.
A paid plan. Disconnecting also sets a running subscription to end at the close of the period already paid, or ends it at once if a payment is overdue, so you are not charged again. The subscription record in section 4 (no Workspace data and no personal data) is kept for that purpose, and deleted automatically 30 days after the subscription has ended unless you have connected again.
Inactivity. After 12 months with nobody from your organisation opening the app, we do the same automatically, unless your domain has a paid subscription running. About 30 days beforehand we send one email to the administrator who connected the domain, at the address they sign in with; signing in once before the date in that email keeps everything. If the email cannot be sent, we keep trying, and the deletion goes ahead at most 60 days late.
Access withdrawn at Google. If Google refuses our access to a domain with a paid plan at every check over 7 days, for example because the app was removed in the Google Admin console instead of disconnected, we end the subscription as a disconnect does, so you are not charged again, and send one email to the administrator who connected the domain. Your data is kept as it is, and the rules in this section still apply to it; connecting again lets you renew the plan.
Backups. Deletion removes your data from our live database at once. Copies remain in our encrypted database backups for up to 7 days until those backups are overwritten; they cannot be edited to remove one domain. If we move or shut down our hosting, any copy of the database made for that (for example a final snapshot or an export) is encrypted, and we delete it within 7 days. If we ever restore a backup, we delete again everything that had been deleted since it was taken.
6. Who we share it with
Nobody, apart from the service providers who host or process it for us, and Link, Stripe's checkout service, which sells the paid plan as merchant of record under Stripe's Managed Payments:
| Provider | What for | Where |
|---|---|---|
| Amazon Web Services (Amazon Web Services EMEA SARL, Luxembourg) | Hosting the app, its database, backups and logs | EU, Ireland (AWS region eu-west-1) |
| Amazon Web Services (Amazon SES) | Delivering contact-form messages to our mailbox: your name, email address and message; when the agent is on, delivering its emails: the recipient's address and the email itself; delivering the notice before a domain is deleted for inactivity, and the notice when a paid plan ends because Google refused our access: the connecting administrator's address and the domain name | EU, Ireland (eu-west-1) |
| Google Ireland Limited (Google Workspace, under Google's Cloud Data Processing Addendum) | Our mailbox, where contact-form messages and emails to us arrive and from which we reply | Google's data centres, which may be outside the EU, including the USA (Google LLC is certified under the EU-US Data Privacy Framework) |
| Google Ireland Limited (Google Analytics 4) | Counting visits and sign-up steps from our server, with no personal data; and, only if you accept the cookie banner on the start page, measuring how visitors use that page (see "Visit statistics" below) | Google's data centres, which may be outside the EU, including the USA (Google LLC is certified under the EU-US Data Privacy Framework) |
| Link, Stripe's checkout service, as merchant of record under Stripe's Managed Payments (named at checkout and on your receipt) | Selling and billing WorkspaceRadar Paid. Stripe collects your payment details and billing email itself; we never see them. We send Stripe only your Google customer id and your domain name | The EU and Stripe's data centres outside it. Transfers outside the EU are covered by the safeguards described in Stripe's privacy policy |
We contact Google only to sign you in; to make the read requests and, on your approval, the changes in section 3, using your domain's own permission; to withdraw that permission when the domain is disconnected; and to send the visit statistics below. We do not sell data. We do not use it for advertising. Our fonts and icons are served from our own site. Unless you accept Google Analytics on the start page (below), opening our pages makes your browser contact no other company, and inside the app it never does. The CSV files you export are downloaded by you and sent to no one else.
Visit statistics. To see how many people find us and how many get to a savings number, our server (not your browser) tells Google Analytics when one of these steps happens: the start page is opened, Connect is clicked, Google's sign-in succeeds or fails, a domain's first scan finishes or fails, a checkout is started, and a subscription starts or ends (with its size and billing interval only). Each message contains only the name of the step, a broad category of where the visit came from (for example "search engine Google", "ChatGPT" or "direct"), and for a failure a short error code. It contains no IP address, no browser details, no email address, no domain and no identifier: every message carries a new random number, so Google cannot link two of them to each other or to you. No cookie is set and nothing is stored in your browser. Because none of this relates to an identifiable person, it is not personal data; we describe it here so that you know about it. Search engines and automated tools are not counted.
Google Analytics on the start page, only with your consent. When you first open our start
page, a banner asks whether we may use Google Analytics. Only if you click Accept does your
browser load Google's analytics script, which sets two cookies (_ga and _ga_<id>, kept for 90
days) and sends Google information about your visit to that page: the pages and links of it you
use, your browser and device type, your approximate location derived from your IP address, and
where you came from. Google Analytics 4 does not store IP addresses. Google signals and ad
personalisation are switched off, and the data is kept for 2 months. It runs only on the start
page, never inside the app after you connect. If you click Decline or ignore the banner,
nothing is loaded and no cookie is set. The legal basis is your consent (Art. 6(1)(a) GDPR and
§ 25(1) TDDDG). You can withdraw it at any time with Cookie settings at the bottom of the start
page; we then stop the measurement and delete the cookies. Your choice itself is remembered in
your browser's local storage (wr-analytics-consent), which is strictly necessary to respect it.
7. Cookies
The app sets two cookies. We treat both as strictly necessary, and your browser deletes both itself when you close it.
__Host-SESSIONkeeps you signed in. It contains only a random identifier. The sign-in it refers to ends when you sign out, or 12 hours after you signed in, whichever comes first.wr_appis a marker that holds only the value1, no identifier. It is used to hide the start page's public text before the first paint, so a signed-in browser goes straight to the app. It is set when a signed-in browser opens the start page or an app screen, and removed when a signed-out one does.
There are no advertising cookies. Only
if you accept Google Analytics on the start page are its two cookies, _ga and _ga_<id>, set
(section 6); without that consent there are no analytics or third-party cookies.
8. Security
- Access tokens are encrypted at rest (AES-GCM), bound to your domain's record, and use a key that can be rotated.
- All traffic uses HTTPS.
- The database is encrypted at rest, has no public address, accepts network connections only from the app, and is backed up automatically, with backups kept 7 days.
- Technical logs are kept 30 days.
- The session cookie is
HttpOnly,SecureandSameSite=Lax. - Every database query for your data is scoped to your domain.
- Only Xinru Tang, the operator, can access the production systems, with personal credentials and SSH keys; the server accepts SSH connections only from the operator's own network address and, for the length of a deployment, from the operator's automated deployment job, which uses its own key and only installs and restarts the software.
9. Google API Services User Data Policy
WorkspaceRadar's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- We use Google user data only to provide the features you see in the app.
- We do not transfer it except as needed to run the app, for security, or to comply with the law.
- No human at Xinru Tang reads it unless you ask us to (for example in a support request), or it is needed for security or required by law.
- We do not use it to train or improve general-purpose artificial intelligence or machine learning models.
10. Your rights
If you are in the EU/EEA or the UK, you have the right to:
- access your personal data, correct it, or have it erased;
- restrict or object to its processing;
- receive it in a portable format;
- complain to a supervisory authority (for us, the Bavarian State Office for Data Protection Supervision, BayLDA, in Ansbach; you may also complain to the authority where you live or work).
The administrator can export scan results (CSV) and delete everything (section 5) without contacting us. For any other request, write to contact@workspaceradar.com.
If you are an employee of an organisation that uses the app, your organisation is the controller of your data (section 2). Please direct requests to your organisation's administrator first. We will help them respond.
Legal basis (for the administrator's sign-in identity, where we are the controller): Art. 6(1)(b) GDPR, performance of the contract with your organisation, and Art. 6(1)(f) GDPR, our legitimate interest in knowing who connected a domain and in telling them before we delete it.
11. Changes
If we change this policy, we will update the date at the top. If a change reduces your rights, or changes what we read from Google, we will show it in the app before it takes effect.