Google User Data & Limited Use Disclosure

This document describes how NAL Services access, use, store, and share Google user data when you connect a Google Account. Today, the only Google integration we offer is Sign in with Google (authentication). Section 2 states exactly what that accesses. Section 3 explains what would happen if we later add Google Workspace features (Calendar, Drive, Gmail), and the commitments that would bind them.

It is part of, and must be read together with, the main Privacy Policy. Where the two address the same topic, the Privacy Policy's protections continue to apply.

Effective date: 2026-07-14

1. Our Limited Use Commitment

NAL'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 plain terms, the four Limited Use pillars we are bound by are:

1. Prominent user-facing features only. We use Google user data only to provide or improve user-facing features that are prominent in the NAL Service you granted access to. We do not use it for any unrelated purpose.
2. No transfer, except: (a) to provide or improve those features, with your consent; (b) for security purposes (for example, investigating abuse); (c) to comply with applicable law; or (d) as part of a merger, acquisition, or sale of assets, and only after obtaining your explicit prior consent.
3. No human access, except: (a) with your affirmative agreement to view specific messages, files, or events; (b) for security purposes; (c) to comply with applicable law; or (d) where the data has been aggregated and anonymised and is used for internal operations.
4. Never sold. We do not sell Google user data, and we do not transfer it to data brokers, information resellers, or any party for advertising, ad retargeting, personalised advertising, or credit-worthiness assessment.

2. What We Access Today — Sign in with Google

The only Google scopes NAL requests are the standard sign-in scopes.

We request scopes incrementally and only when needed. We do not currently request any Google Calendar, Drive, or Gmail scope. Features in NAL that mention a "calendar" or "files" (for example in BRAIN) use NAL's own self-hosted calendar and file storage, not Google APIs, and are outside this document.

This sign-in data is used solely for account identity — to create, authenticate, and maintain your NAL account. It is not used for any other purpose.

Note (not your data). NAL separately operates a YouTube publishing integration that uploads NAL's own generated videos to NAL's own YouTube channel, using an operator account. It does not access, read, or touch any end-user's Google account, and is unrelated to your Sign in with Google. It is mentioned here only for full transparency.

3. If We Add Google Workspace Features Later

If NAL later introduces a feature that reads your Google Calendar, Drive, or Gmail through Google APIs, then before that feature launches we will:

• update this document with a scope-by-scope disclosure (what is accessed, the prominent feature it powers, whether it is stored, and for how long);
• request each scope incrementally, with an in-context consent screen at the moment the feature needs it; and
• apply the following handling rule to the fetched data.

Handling rule (committed). The raw payload fetched from Google (a full email, file, or event) would be processed transiently — held in memory for the duration of your request and not written to a NAL database as a raw Google object. Any reply a Service produces from it (a summary, a quotation) is Google-derived content: if it becomes part of your conversation or output it is stored and retained as conversation content under Privacy Policy §8 and is deletable under §9. Derived content remains Google user data by provenance and stays bound by every commitment in Section 1 — including no training (Section 4) and the human-access limits (Section 5). Where a Service calls a third-party AI provider, only the minimum content needed for that single call is forwarded, under Privacy §4.4, and such content is never routed to NAL Net community workers (Privacy §4.5).

4. We Do NOT Train AI on Your Google Data

Consistent with Privacy Policy §4.1, Google user data is never used to train or improve any AI or machine-learning model, ours or anyone else's. Today this covers your Sign-in identity data; it would equally cover any Workspace content under Section 3.

5. Human Access Is Strictly Limited

A NAL person will only ever view your Google user data under the narrow conditions in the Limited Use commitment above — most commonly your affirmative agreement to view specific messages, files, or events (for example, when you explicitly ask a support engineer to look at one item to resolve a problem), or for security or legal reasons.

This is a narrower allowance than the optional Safety Review Consent, which covers human review of your conversations for safety. That consent does not extend to any content sourced from your Google account — including summaries or quotations of it. Content sourced from your Google account is only ever human-viewed under the specific-item affirmative-agreement condition described here.

6. Revoking Google Access

• You can revoke NAL's access at any time directly from Google at myaccount.google.com/permissions, which invalidates NAL's access immediately.
• NAL account settings show your connected Google account; a one-click in-NAL unlink is being rolled out — until it is available for your account, use the Google permissions page above, which takes effect immediately.

Revoking access stops future processing. It does not delete your NAL account or content; to delete those, see Privacy Policy §9.

7. Google Play Data Safety Alignment

For any NAL Android application that uses Sign in with Google, the Play Data safety section declares the corresponding data types (personal identifiers such as name and email) as collected for app functionality, not shared for advertising, and not sold, and links to this disclosure. The Data safety declaration and this document are kept consistent.

8. Related Documents

• Privacy Policy — full data-handling terms and your rights.
• Subprocessors & Partners — Google LLC is listed as a subprocessor.
• Safety Review Consent — optional human review of conversations (does not extend to Google-sourced content).

9. Contact