Alexandria Logotype

Google Data Use Notice

Last updated: January 7, 2026

This notice complements the Privacy Policy and explains how Alexandria uses Google Drive when you choose to import content from Drive.

Summary

  • Alexandria reads only the file(s) you explicitly select via Google Picker to create a lesson/course.
  • Sync is optional (opt-in) and allows re-reading the same selected file(s) to keep the course updated.
  • We do not store a copy of the original Drive file; we store the transformed output in Alexandria, which may include text, images, and other resources needed for the lesson/course, until deleted under workspace rules.

1) What the integration does

Alexandria turns the content of a Google Drive document you explicitly select into structured text inside Alexandria (e.g., Markdown-like format).

2) What you will see in the app

Typical flow:

  1. Connect Drive
  2. Select file (s)
  3. Enable sync (optional)

3) Permission and consent screen

Alexandria requests a Google Drive permission intended for per-file access (the user selects the file via Google Picker).

Note: Google manages the OAuth consent screen. The wording shown there may describe, in general terms, access to “files you use with this app.” In all cases, Alexandria only accesses the files you explicitly select.

4) What we access (and what we don’t)

We access only:

  • The content of the files you select (read-only).
  • Minimum metadata needed to link and, if applicable, update.

We do not access:

  • Your entire Drive or broad file listings.
  • Files you did not select.

We do not:

  • Modify, create, overwrite, or delete Drive files.

5) Minimum metadata

To link the file to a lesson and manage sync (if enabled), Alexandria only process the metadata:

  • fileId
  • fileName
  • mimeType
  • exportedAt (timestamp returned by Google at the time of export/read)

If we need to store additional metadata in the future, we will update this notice.

6) What we extract

We extract the necessary content from the selected file(s), including text, headings/structure, links, and, where present, images or other embedded resources, to generate the lesson/course

7) Where processing happens

Processing happens on our systems hosted on Render (EU).

8) What we store

  • We do not store a copy of the original Google Drive file as such.
  • We do store the transformed output (lesson/course) in Alexandria, which may include structured text and derived copies of images and other resources needed for the lesson/course.
  • If you revoke Drive access, we cannot re-read/sync, but content already transformed and stored in Alexandria may remain until deleted under workspace rules (see Retention in the Privacy Policy).

9) Sync (opt-in)

If you enable Enable sync, Alexandria may re-read the same selected files to keep the course updated.

  • Re-reading may occur manually, upon publishing, or on a periodic basis, depending on product configuration.
  • Refresh token: stored only if sync is enabled, solely for this purpose, and limited to the selected file.

10) Revocation and access loss

  • You can revoke access in your Google account following this link. After revocation, Alexandria cannot re-read or sync that file.
  • If access is lost (revocation or Drive permissions), Alexandria will show an in-app notice.
  • Existing lessons remain in Alexandria until deleted by the Customer/user.

If a workspace loses access for commercial reasons (e.g., non-payment), the specific retention period is not yet defined and will be communicated once established.

11) Human access and support

Under normal conditions, processing is automated. Support access conditions for imported content are not yet defined; in any case, we will apply least-access principles.

12) Limited use

Drive content is used only to create or update lessons/courses from the file(s) you select. It is not used for advertising or unrelated purposes. Any human access, if it occurs, will be limited to what is strictly necessary (e.g., support upon request, security, abuse investigation, or legal compliance).

13) Contact

Questions about this integration: support@code-sherpas.rocks