Privacy policy

1. Visiting this website

You do not need an account to read these pages. The website code does not set cookies, use browser storage, run analytics or advertising scripts, or provide forms for collecting personal information. It does not access Google Drive.

Cloudflare hosts and delivers the site. As part of delivery and security, it can process technical request information such as your IP address, browser information, requested address and request time. This is different from application-level tracking; this policy does not claim that hosting infrastructure keeps no operational records.

See Cloudflare's privacy policy for its own processing practices.

If you email us, we receive your email address, message and any information you choose to provide. The project operator uses that information to answer your inquiry, verify your authority where necessary and handle your request. We retain this correspondence only as needed for those purposes, subject to the limited security or legal exceptions in section 6. Sending an email is separate from browsing this website or granting Google Drive access.

2. Google Drive access

Only the authorized project operator uses the separate Google Drive connection workflow. The requested scope is https://www.googleapis.com/auth/drive.file.

This permission applies to files created with the app or explicitly opened or shared with it, including files selected through Google Picker. It is not permission to read the operator's entire Drive. It is also not a read-only scope: Google permits creation, reading, editing and deletion within its per-file authorization boundary. The current development work uses selected-file access for content handling and testing; these public pages perform none of those actions.

The workflow can access selected file contents and associated metadata, including file identifiers, names, formats, sizes, folder relationships, sharing status and download capability. Its authorization records include the granted permission and connection timestamps. No Gmail, contacts or calendar access is requested by this Drive scope.

3. Purpose and permitted use

Selected files and their metadata support the operator-authorized educational workflow: identifying suitable learning materials and checking that the project can retrieve and handle them. Future delivery to learners is an intended feature, not a service offered by this website.

Google-derived information is to be used only for this disclosed workflow. It must not be sold, used for advertising, supplied to data brokers or used to train general-purpose artificial intelligence models.

Acadict's use and transfer of Google-derived information will follow the Google API Services User Data Policy, including its Limited Use rules, and the applicable Google Workspace user-data requirements.

4. Access and service providers

The authorized operator can view the materials they select. Google provides authorization and Drive storage; Cloudflare provides hosting and the separate application's processing infrastructure. Google also provides Gmail for the contact mailbox, so messages you send are processed by that email service. Those providers process information needed for their respective services.

These public pages do not display selected Drive files or distribute them to visitors. Any later learner-facing delivery must be limited to material the operator is entitled to share and to the intended, authorized audience. Connecting a Drive account does not itself publish its files on this website.

5. Authorization, storage and retention

The separate administrator workflow stores an encrypted authorization credential to support continuing, authorized access without a new sign-in for every operation. Short-lived access credentials are used during processing rather than saved as persistent application records. Google account passwords are not requested by these public pages.

The current operator connection supports ongoing authorized development. We retain application-held Google-derived data only as needed for the disclosed, authorized workflow and in accordance with applicable provider requirements. This public website has no connection to the credential store and does not store selected Drive content.

You can request deletion of application-held data using the procedure below. Revoking Google authorization does not, by itself, delete data already obtained by Acadict. The deletion deadline below does not authorize retaining data longer than applicable provider requirements allow.

6. Revoking authorization and requesting deletion

Revoke Google authorization

An authorized operator can visit Google Account connections, select the application they authorized and remove its access to Google data. Check the application's displayed identity before removing a connection. Google's connection-management guidance explains these controls.

Revocation removes the application's permission to access Google data through that connection. It does not itself delete application-held credentials, metadata or copies already obtained. To request their deletion, use the separate email procedure below.

Request deletion of application-held Google data

1. Send your request: email acadict.support@gmail.com, identify the affected Google account or connection and describe the data you want removed. Where possible, write from the email address associated with that connection. You do not need to grant new Google permissions to submit a request.
2. Verify the request: the project operator checks that you control the affected account or are authorized to request deletion. We may ask for the minimum additional information needed to verify this. Do not send passwords, sign-in codes, OAuth tokens or other secrets.
3. Manual removal within 30 days: within 30 days of verifying the request, the project operator deletes the affected application-controlled active OAuth credentials and connection metadata, and removes no-longer-required application-held Google-derived records and content copies. This includes stored connection credentials and any active access credentials under Acadict's control. The limited exceptions below apply.

These are separate actions: an Acadict deletion request is not a substitute for removing Google's authorization in your Google Account settings. Removing Google's authorization is not a substitute for asking Acadict to delete application-held data. Requests are handled manually; this public website does not run an automatic or self-service deletion function.

Original Drive files: an Acadict deletion request does not automatically delete original files remaining in your Google Drive. Those originals remain under your control in Google Drive.

Provider-managed remnants: backup or log remnants managed by service providers may persist temporarily according to their retention cycles, even after deletion from application-controlled active systems. No separate fixed retention period is promised for those provider-managed remnants.

Limited longer retention: Acadict may retain only the minimum data genuinely necessary for security purposes or legal obligations, and only for as long as that need remains. This exception does not permit retaining data for continued routine use after the requested deletion.

7. Security and future changes

The site is delivered over HTTPS. The administrator connection is access-restricted, and its stored authorization credential is encrypted. These measures reduce risk; they are not a guarantee against every form of unauthorized access, loss or copying.

This notice must be updated when the project's data handling changes. New uses of Google data require an appropriate disclosure and any necessary fresh consent before that new use begins. The date above identifies this version.