Sailing Jury Decision ← Back to homepage
Legal

Privacy Policy

Effective 06 June 2026 · Last updated 18 August 2026

This privacy policy describes how the Sailing Jury Decision Google Workspace add-on (“the add-on”) handles your information. The add-on is a personal-effort tool maintained by Yoann Peronneau (“the developer”) to assist sailing jury panels in drafting and filing race decisions.

1. Who is responsible for your data

The data controller, under the meaning of the General Data Protection Regulation (GDPR), is:

Yoann Peronneau

France

The developer is a private individual, not a company. The add-on is provided free of charge as a contribution to the international sailing judging community.

2. What the add-on accesses

When you install and use the add-on, it requests the following Google account permissions:

  • See your Google Docs documents when you open them with this add-on (documents.currentonly). This lets the add-on read the text of the document you actively have open in Google Docs.
  • See, edit, create, and delete only the specific Google Drive files you use with this app (drive.file). This is the narrower variant of the Drive permission set. The add-on cannot see any file in your Drive other than those you explicitly use it on. It uses this scope specifically to export the active document to DOCX format so it can read jury member dropdown values (which the Apps Script DocumentApp API does not expose).
  • Display and run third-party web content in prompts and sidebars inside Google applications (script.container.ui). This lets the add-on render its side panel and dialog.
  • Connect to an external service (script.external_request). This is used to fetch the shared standard wording snippets from the developer’s public Google Sheet and to call the Google Drive API.

You can revoke these permissions at any time via your Google account settings: https://myaccount.google.com/permissions

3. What information the add-on processes

While in use, the add-on reads:

  • The text content of the Google Doc you have open.
  • The jury member names entered as smart-chip dropdowns in the document.
  • The decision date, time, and other fields you’ve entered in the document’s tables.

It also fetches a public, read-only list of standard wording snippets from a Google Sheet maintained by the developer. This fetch does not transmit your data anywhere — it only retrieves wording suggestions for display in the side panel.

4. What the add-on does not do

The add-on does not:

  • Send your data to the developer or any third party.
  • Use analytics, telemetry, or tracking services.
  • Use artificial intelligence services that might log or retain your content.
  • Read any document other than the one you actively open and explicitly use the add-on with.
  • Store your document content on any server outside Google’s infrastructure.

5. Where your data is processed and stored

All processing happens within Google’s Apps Script infrastructure, under your own Google account. The add-on runs as code, not as a hosted service — the developer does not operate any server that receives your data.

Temporary caches:

  • CacheService (user-scoped, 1-hour maximum lifetime): the add-on caches the standard wording snippets and a “this document has been authorized” marker, to keep the side panel fast. These caches expire automatically and are stored within your Google account.
  • PropertiesService (user-scoped): not currently used for any persistent data.

Your document content is held only in memory during the brief execution of an extraction (typically under one second) and is then discarded.

When you click “Copy for sailti / RRS / m2s / ROMS”, the extracted decision payload is written to your operating system’s clipboard. From that point on, the payload is under your control — it stays in your clipboard until you paste it somewhere or copy something else.

6. Data security and protection

The add-on follows a minimum-data design and relies on Google’s infrastructure to protect the confidentiality of your data. Specific security measures include:

Encryption in transit. All communication between the add-on and Google’s APIs occurs over HTTPS / TLS. No data is ever transmitted in clear text. The add-on never transmits data to any developer-controlled server, because there is no developer-controlled server in the data path.

Encryption and access controls at rest. Any data the add-on processes is handled within Google’s Apps Script infrastructure, which inherits Google’s standard security protections — encryption at rest, network isolation, and identity-based access controls. The developer does not operate any servers or storage independent of Google.

Minimum-data design. The developer does not store your document content. No databases, no analytics, no backups are maintained by the developer. Apps Script may log uncaught exceptions (error messages and stack traces) to Google Cloud Logging within the developer’s Cloud project; these logs do not contain document content under normal operation. The only persistent storage the add-on writes is a small per-user cache flag (Apps Script’s CacheService, automatically expiring within one hour) indicating per-document Drive consent; this cache contains no document content.

Scope restriction. The add-on uses the narrowest applicable Google OAuth scopes:

  • drive.file grants access only to documents you explicitly authorize via the per-document consent prompt — not to your entire Drive.
  • documents.currentonly grants access only to the document you currently have open in the editor.

URL allowlist. Outgoing network requests from the add-on are restricted to a short, explicit allowlist declared in the add-on’s manifest: the Google Drive v3 export endpoint and the public snippets spreadsheet. The add-on cannot make HTTP requests to any other URL.

Third-party data flow. When you click “Copy for sailti / RRS / m2s / ROMS”, the decision payload is placed on your operating system’s clipboard. You then explicitly paste it (via the companion bookmarklet you installed) into your event’s filing system. This transfer happens entirely on your device, between your clipboard and your own browser tab. The add-on does not transmit data to third parties on your behalf.

7. Third-party services

The add-on does not integrate with third-party services other than:

  • Google services (Drive, Docs, Sheets, Apps Script): these are operated by Google under Google’s own privacy policy at https://policies.google.com/privacy.
  • The developer’s standard wording Google Sheet: a public-read sheet maintained by the developer. No data flows to this sheet from your usage — only data flows from it (snippets) into your sidebar.

The companion bookmarklet (a separate piece of code installed in your web browser) reads from your clipboard and fills sailti, RRS, m2s, or ROMS forms directly in your browser. It does not send your data anywhere — the data flow is browser → clipboard → bookmarklet → form, all locally in your browser.

8. Legal basis for processing (GDPR Article 6)

Processing is based on:

  • Article 6(1)(b) — performance of a service you have requested: by installing the add-on and clicking its buttons, you ask it to read your document and produce the decision payload.
  • Article 6(1)(f) — legitimate interest: the developer has a legitimate interest in providing this tool to the sailing judging community, and the processing is limited to what’s necessary for the tool to function.

9. Your rights under GDPR

You have the right to:

  • Access — request a copy of any personal data the developer holds about you. (In practice, the developer holds none; usage is opaque to the developer.)
  • Rectification — request correction of any inaccurate personal data.
  • Erasure — request deletion of any personal data. (In practice, uninstalling the add-on removes any remaining cached data within ~1 hour.)
  • Restriction — request that processing be limited.
  • Portability — request your data in a portable format.
  • Object — object to processing based on legitimate interest.
  • Withdraw consent — uninstall the add-on at any time via https://myaccount.google.com/permissions.

To exercise any of these rights, contact the developer at the email address in Section 1. You also have the right to lodge a complaint with your national data protection authority (in France: the CNIL, https://www.cnil.fr).

10. Data retention

The add-on retains no data beyond the in-memory and short-lived cache described in Section 5. There is no long-term storage of your document content, your usage patterns, or your identity by the developer.

Google may retain logs of API calls under its own retention policies; these are governed by Google’s privacy policy, not this one.

11. International data transfers

The add-on runs on Google’s Apps Script infrastructure, which Google operates globally. Data may transit through Google data centers outside your country. Google maintains GDPR-compliant safeguards for these transfers under its own privacy framework.

The developer does not directly transfer data outside the European Union.

12. Children’s privacy

The add-on is intended for adult sailing jury members. It is not designed for, marketed to, or intended for use by anyone under 16. The developer does not knowingly collect any data from minors.

13. Changes to this policy

The developer may update this policy from time to time. The “Last updated” date at the top will change. Material changes will be communicated via the project website at https://jury.peronneau.net/.

Continued use of the add-on after a policy change constitutes acceptance of the updated policy.

14. Contact

For any privacy-related question, exercise of your GDPR rights, or general inquiry:

Yoann Peronneau

The developer aims to respond within 14 days. For urgent matters affecting more than one user, please indicate this in the subject line.

This policy is published at https://jury.peronneau.net/privacy.html.