Data Processing Agreement
Between the customer who accepts the Terms of Service ("Controller") and Xinru Tang, Möwenweg 5, 91056 Erlangen, Germany ("Processor"). Effective from 5 October 2026, last updated 20 November 2026. It forms part of the Terms of Service.
1. Subject matter, duration, nature and purpose
- Subject matter and purpose. The Processor analyses the Controller's Google Workspace domain to identify licences that appear unused, estimate their cost, and show account security facts and change over time. Its agent briefs the Controller's administrators by email, proposes actions, and carries out those an administrator approves.
- Nature. Automated reading of Google APIs, storage and computation, and, only on an administrator's approval of that specific change, releasing or re-assigning a licence (Annex 2).
- Duration. Until the Controller disconnects the domain, or the Terms end.
- Data and data subjects. Categories of personal data and data subjects: Annex 1.
2. Instructions
The Processor processes personal data only on the Controller's documented instructions, including with regard to transfers of personal data to a third country or an international organisation. These are the Terms of Service, this agreement, the Controller's use of the app's settings (for example, turning weekly rescans on or off), and an administrator's approval of a specific change. The exception is where Union or Member State law requires otherwise, in which case the Processor informs the Controller first unless the law forbids that. If the Processor believes an instruction infringes data protection law, it tells the Controller.
3. Confidentiality
Everyone authorised by the Processor to process the personal data is bound by confidentiality.
4. Security
The Processor applies the technical and organisational measures in Annex 2 (Art. 32 GDPR). It may improve them, but must not lower the level of protection.
5. Sub-processors
The Controller gives general authorisation for the sub-processors in Annex 3. The Processor will announce any addition or replacement 30 days in advance on this page and in the app. The Controller may object on reasonable data protection grounds. If the objection can't be resolved, the Controller may terminate. The Processor imposes the same data protection obligations on each sub-processor, and remains liable for them.
6. Assistance
The Processor helps the Controller, taking the nature of the processing into account:
- Data subject requests. The app lets the Controller export scan results and delete all data itself. For anything else, the Processor responds within 30 days of a request to contact@workspaceradar.com.
- Security, breach notification, DPIAs and consultation with authorities (Art. 32–36 GDPR). The Processor provides the information it holds.
7. Personal data breaches
The Processor notifies the Controller without undue delay, and at the latest within 48 hours, after becoming aware of a personal data breach. The notice includes the information required by Art. 33(3) GDPR as far as it is available. The notice goes to the email address of the administrator who connected the domain.
8. Deletion or return at the end
At the end of the processing, the Processor deletes or returns the personal data, at the Controller's choice:
- Return. Before disconnecting, the Controller can download the scan results itself, as CSV files, from the app at any time. That download is how personal data is returned.
- Deletion. When the Controller disconnects the domain (Settings → Disconnect this domain), the Processor deletes all personal data of the Controller at once, and withdraws its Google access. Earlier deletion applies as set out in Annex 1.
No copies are retained except where Union or Member State law requires, and except in the Processor's encrypted database backups, which expire and are overwritten within 7 days. If the Processor moves or shuts down its hosting, any copy of the database made for that (for example a final snapshot or an export) is encrypted and deleted within 7 days. Technical logs, which are not designed to contain personal data, expire within 30 days.
9. Audits
The Processor makes available the information needed to demonstrate compliance with Art. 28 GDPR, and allows audits by the Controller or an auditor it mandates. Audits need reasonable notice (at least 30 days), take place during business hours, and happen no more than once a year unless there is a breach. Each party bears its own costs; the Controller bears the costs of an auditor it mandates.
10. International transfers
Personal data is processed and stored in the EU, in Ireland (AWS region eu-west-1). The
Processor does not itself transfer it outside the EEA.
Amazon Web Services (Amazon Web Services EMEA SARL), the sub-processor in Annex 3, belongs to a group whose parent company is in the United States, so access from outside the EEA cannot be ruled out entirely (for example, for support, or under a legal order to the parent). Any such transfer is covered by the Standard Contractual Clauses in the AWS Data Processing Addendum, and by Amazon.com, Inc.'s certification under the EU-US Data Privacy Framework (Art. 45 and 46 GDPR). Any other transfer outside the EEA takes place only on the Controller's documented instructions and with a transfer mechanism under Chapter V GDPR.
Annex 1: Data subjects, data, retention
Data subjects: the Controller's Google Workspace users. The Controller's administrators are among them: their directory details and usage are processed like any other user's, and the app keeps, for the Controller, which administrator declared a price, decided one of the agent's proposals or approved an action, and which one receives the agent's emails.
Not covered by this agreement: the administrator's sign-in identity (the email address the administrator signs in with, held in the sign-in session and as the connecting administrator of the domain). The Processor uses it as its own controller to sign the administrator in, to know who connected the domain and to send that administrator the notices in §7 and in the Privacy Policy, section 5, as described in the Privacy Policy, section 2.
| Data | Retention |
|---|---|
| Users: Google user id, email address, organisational unit, suspended/archived status, account creation time, last sign-in time | 12 months per scan; the two most recent completed scans are always kept. A person's 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 |
| Users: licences (SKUs) held, add-on licences included; per-app last-activity timestamps and activity counts (Gmail, including mail apps over IMAP/POP and Gmail on the web, Drive, Chat, sign-in); whether a first sign-in was ever completed and whether a password change is due; the resulting activity verdict and licence cost | same |
| Users: 2-step verification status, number of admin roles, whether the user is an administrator or a super administrator, number of third-party apps, Google's password strength and length labels, less secure app access status | same |
| Suspended users who still hold a licence: how much storage the account uses (one figure per account) | same |
| Users holding a Gemini add-on: number of Gemini uses and latest use time | same |
| Users who turned on mail forwarding to an outside address (last six months): email, the outside domain only, and when | same |
| 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; 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; application setting changes): the event, its time, the administrator who made it and the account it concerns (held as the Processor's internal record of the account, an outside address as its domain only), and short facts as the event needs: for app, Gmail and email settings, their names only, never their values; for sign-in and licensing settings, 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, its scope count and, if short, its scope list; product and licence names; an email monitor's end date; data transfer app names; outside mail-route and monitor destinations as domains; the organisational unit a setting applies to; and whether a role is the super administrator role. No IP addresses, role names, app, Gmail or email setting values or mailbox export search terms | 180 days (setting changes 35 days), never longer than Google keeps the log; deleted with its scan and on disconnect |
Raw Google API responses, restricted by the Processor's requests to the fields above: Google user id, email address, organisational unit, suspended/archived status, administrator status, creation and last sign-in time, licence held, the usage and security values above, and, for Gemini add-on holders, 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 above (other addresses in a kept value as ***@domain; the administrator who made a change, including one outside the Controller's domain such as a reseller, and the accounts an event names are kept as Google wrote them, even when the account matches no user of the Controller), kept 30 days like every raw response. No IP addresses, names, other profile details or content |
30 days |
| The agent's findings (a situation noticed about a user, such as a licence nobody used, tied to the user's account record in the scan, with its cost where it has one), its proposals (what it suggests doing, with who decided it, when, and any reason the administrator typed) and the rules an administrator gives it (for example "never propose anything for this person"), with who added them | Findings 12 months after they are resolved; decided proposals 12 months after the decision; rules until deleted or disconnect |
| Actions carried out on an administrator's approval of that specific change (releasing a licence, re-assigning it): the user, the licence, who approved it and when, the outcome, and Google's request and response for each check and for the change, verbatim (the user's Google id, email address, suspended status and whether they are an administrator, or the licence assignment) | 12 months after the action finished |
| The agent's emails: the recipient's address, the email's text and its delivery record. Users are named in an email only if an administrator switched names on | The text 30 days; the record 12 months |
| The Controller's encrypted Google access token; email of an administrator who declared a price | Until disconnect, or automatically after 12 months in which no administrator opened the app, unless a paid subscription is running (Privacy Policy, section 5). A declared price, with its administrator's email, is also deleted when the Controller changes the billing currency |
| Database backups containing any of the above | 7 days after the data left the live database |
| A copy of the database made only when moving or shutting down the hosting (a final snapshot or an export) | Deleted by the Processor within 7 days |
| Technical logs (record ids, error codes, error types, and for some errors an error message and code location; no personal data by design. A failed scan is logged with its error type and location only, and the database is set not to put data values in its error messages) | 30 days |
No special categories of data (Art. 9 GDPR) are processed. The Processor does not process the content of email, files, calendars, chats or AI prompts.
Annex 2: Technical and organisational measures
- Encryption.
- In transit: HTTPS for all traffic.
- At rest: Google access tokens are encrypted with AES-GCM, bound to the tenant as associated data, with a key id for rotation. The database and its snapshots are kept on an Amazon Lightsail attached disk, encrypted at rest by the hosting provider with keys it manages.
- Access control and separation.
- Every query on customer data is scoped to the tenant, and the database enforces tenant-scoped foreign keys.
- The database has no public address (not publicly accessible) and accepts connections only from the application. Application credentials are held in an access-restricted file on the encrypted disk, not in code or images.
- Sessions use
HttpOnly,Secure,SameSite=Laxcookies. - Administrator sign-in is through Google.
- Data minimisation.
- Google permissions limited to the directory, reports and licensing.
- No content scopes.
- Only counts and timestamps are kept from activity logs.
- An automated build check fails if any code other than the approved-action path makes a changing request to Google.
- Changes only on approval. A change to the Controller's Google Workspace is made only for a specific change an administrator approved, after a fresh read of the user from Google, and is recorded with the approval and Google's request and response (Annex 1). A change Google did not confirm is never sent again automatically.
- Deletion.
- Raw responses are deleted automatically after 30 days.
- Full deletion on disconnect, verified by an automated test that checks every tenant table.
- Database backups are kept 7 days; a copy made when moving or shutting down the hosting is deleted within 7 days; technical logs are kept 30 days.
- No third-party scripts in the app. Inside the signed-in app there are no analytics scripts, trackers, or externally loaded fonts. Google Analytics runs only on the public start page and only with the visitor's consent; the anonymous visit statistics described in the privacy policy are sent from the server. Neither contains Customer Personal Data.
- Availability. Automated daily snapshots of the database disk, kept 7 days.
- Organisational measures. The Processor is a sole trader. Only the Processor personally can access production, read logs or restore backups, using personal credentials and SSH keys; the server accepts SSH only from the Processor's own network address and, for the length of a deployment, from the Processor's automated deployment job, which uses its own key and only installs and restarts the software. No staff or contractors have access. A suspected incident is investigated at once and notified under §7.
Annex 3: Sub-processors
| Sub-processor | Service | Location |
|---|---|---|
| Amazon Web Services (Amazon Web Services EMEA SARL, Luxembourg) | Hosting, database, backups and logs; delivery of the agent's emails, of the notice before a domain is deleted for inactivity, and of the notice when a paid plan ends because Google refused our access (Amazon SES) | EU, Ireland (eu-west-1) |
Google is not a sub-processor. It is the source of the data, and the Controller's own provider. GitHub hosts the Processor's source code and build pipeline and receives no personal data of the Controller, so it is not a sub-processor either.