LISBON ISCInternational Sailing Club

Lisbon International Sailing Club

Privacy Policy

Last updated: 12 October 2026

This policy applies to the Lisbon ISC member platform operated by Lisbon International Sailing Club (LISC) at lisbonisc.org. It explains how the club accesses, uses, stores, shares, and deletes personal information, including information received from Google. LISC is a not-for-profit sailing club established in Portugal.

Who is responsible

The data controller is Lisbon International Sailing Club. You can contact the club at [email protected] or [email protected]. The club's published postal contact address is Praça Europa, 4, 1249-206 Lisboa, Portugal.

Information we handle

Member information can come from information you submit and from existing club membership records, including contact details, membership dates, and opening sailing-credit balances. These club records are separate from the information provided by Google sign-in.

Google data and permissions

Google sign-in

When you choose Google sign-in, the platform requests basic identity permissions: openid, email, and profile. Google provides your account identifier, email address, email-verification status, and, when available, your name and profile-picture URL. We also receive the authentication response and tokens needed to verify and maintain the sign-in connection.

We use this information to authenticate you, create or find your sign-in account, connect a verified email to an existing club member record, and display account information in the member platform. The same verified email can be used with Google or an email link/code to access the same account. Google sign-in does not give the platform permission to read your Gmail messages, Google Drive files, contacts, or calendar.

Gmail API for club service emails

The club separately authorizes its configured sender mailbox with the Gmail sending permission, https://www.googleapis.com/auth/gmail.send. This connection sends requested sign-in links and codes and administrator-issued membership invitations from the club's mailbox. It is not a request for access to a member's Gmail account when they sign in.

For this service, we handle the sender address, recipient address, email subject and message content, the sender's OAuth credentials and tokens, and the message identifier or delivery outcome returned by Google. The integration sends messages through the Gmail API; it does not read or analyze the sender's inbox or recipients' mailboxes. Sent messages may remain in the sender's and recipients' mailboxes under those accounts' retention settings.

Why we use information

We use information to authenticate accounts, manage invitations and membership, maintain member profiles, organize sails and bookings, administer sailing credits and manual payments, send service messages, respond to requests, keep administrative and financial records, and protect the platform against misuse. We do not sell personal information or use it for third-party advertising.

Where the GDPR applies, LISC processes information as needed to provide the membership and sailing services you request, to meet legal obligations, and for its legitimate interests in managing the club, keeping accurate records, and protecting its services. Where processing relies on consent, you may withdraw consent without affecting processing that took place before withdrawal. Optional profile information is used for the related club features.

Limits on use of Google information

LISC follows the Google API Services User Data Policy, including its Limited Use requirements, when using information received from Google APIs or transferring that information to another service. We use Google information for the account, membership, and service-email features described here.

We do not sell Google user data, share it with advertising platforms or data brokers, use it for targeted or personalized advertising, or use it for lending or financial creditworthiness assessments. We do not use Google user data, including data obtained from Google Workspace APIs, to develop, improve, or train artificial intelligence or machine learning models. This includes generalized models that are not personalized to individual users.

Human access to Google Workspace API data is limited to the authorizing user's explicit agreement to review specified data, necessary security or legal purposes, or internal use of aggregated data permitted by Google's policies. OAuth credentials and tokens are not displayed to other club members.

Who receives information

Authorized LISC administrators can access information needed to manage accounts, membership, payments, and club operations. Skippers can access information needed to manage their assigned sails. Eligible signed-in members can see information shown in member features, such as skipper names and member profile photos. Private payment proofs are accessible to their submitting member and authorized approvers.

Google processes authentication requests and the club's outgoing service emails. Google Cloud hosts account information and authentication records in the application database, and uploaded files in private storage. Cloudflare provides network and security services and processes related request information. If the club configures Brevo as its email provider, it receives the recipient and service-message content needed for delivery.

We share or transfer Google information only to operate the features disclosed here with the user's authorization, protect the service against misuse, or meet applicable legal obligations. A transfer connected with a merger or sale would require the authorizing user's prior consent where Google's policy requires it. We do not transfer Google information for unrelated purposes.

Where information is processed

The application and database are configured in Google Cloud's Europe-west1 region. Google, Cloudflare, and email providers may process limited information in other locations as part of their global services. When personal information is transferred outside the European Economic Area, LISC relies on a transfer mechanism permitted by applicable data-protection law, together with any required safeguards.

How long we keep information

We keep account and profile information while the account or membership is active and delete or anonymize it when it is no longer needed for club purposes, subject to applicable legal obligations. Membership, booking, payment, credit, and audit records may be retained after an account is closed when needed to preserve the club's records, resolve disputes, or meet accounting or other legal obligations. Payment proofs are retained only as long as needed for payment administration and applicable legal obligations. Technical logs and temporary sign-in records are kept for the operational periods of the systems that create them.

Google account identifiers, profile information, and authentication records are stored in our protected Google Cloud database. The club sender's OAuth credentials are stored in Google Cloud Secret Manager. Access and refresh tokens are kept only for the related connection and are removed when that connection is deleted or no longer needed, subject to any necessary security or legal retention.

Application sign-in sessions have a seven-day expiry and can be renewed by ongoing use; signing out ends the current session. Email sign-in links and codes are single-use and expire after ten minutes. Expiration prevents further use of the session or code; expired database records may remain until cleanup. Essential authentication cookies support sign-in and session security.

Deletion from active systems may leave recoverable copies in database backups, storage versions, or soft-deleted storage for their configured retention periods. These copies are restricted to recovery and security operations and are not used for normal member features. Deleting an account does not automatically erase service emails already delivered to a mailbox.

Your choices and rights

You can update some profile information in your account. You may ask the club to access, correct, delete, restrict, or provide your personal information, or object to certain processing, by contacting [email protected]. LISC will assess the request and may retain information where required or permitted by law, for example in accounting or audit records. You may also complain to the supervisory authority in your country. In Portugal, this is the Comissão Nacional de Proteção de Dados (CNPD).

Disconnect Google or request account deletion

You can revoke the platform's Google access in your Google Account connections settings. Revoking access prevents further use of the revoked authorization but does not automatically delete information already held by LISC or terminate every existing club session.

To remove a Google connection or request deletion of your account and associated Google information, email [email protected] from your registered email, identifying the account and what you want deleted. We verify ownership, explain any records that must be retained, and remove or anonymize information no longer needed. You can sign out to end your current session. Disconnecting Google does not itself cancel a club membership; an email link or code can remain a sign-in option for the same email.

How we protect information

We use HTTPS for the website and Google API connections, Google Cloud's managed encryption at rest for stored database and file data, restricted service identities, and application access controls. Uploaded proofs and photos are held in storage protected from public access, with authenticated delivery through the platform. OAuth credentials are restricted to the application and authorized operators; session and verification controls help prevent unauthorized account access. No internet service can guarantee absolute security.

Changes to this policy

The current version and its update date are published on this page. If we change how the platform accesses, uses, stores, or shares Google user data, we will update this policy and notify affected users through the platform or their registered email before the changed use begins. We will request any new permissions and consent required for that use.