Privacy Policy

Effective date: 22 August 2026 · Last updated: 22 August 2026

1. What we access in your Google Account

You sign in with Google. During sign-in we ask for the following scopes, and nothing else:

Scope	Why we ask for it
openid, email, profile	To create your account and show who is signed in: your email address, name and profile picture.
drive.file	To read and write the specific spreadsheets you choose. This scope gives access only to files you select yourself in the Google file picker, or that the Service creates for you. It does not give access to anything else in your Google Drive.

Inside a spreadsheet you have connected, the Service reads your data, creates service sheets whose names begin with _ALS_, writes formulas into those service sheets, and reads the results back. We do not write into your data sheet — the first sheet of a connected file is treated as read-only.

2. What we store on our servers

We keep the minimum needed to run an account and show you your projects. Specifically:

Account

• your Google account identifier, email address and whether Google reports it as verified;
• your name and the URL of your Google profile picture, and your locale;
• your plan, credit balance, account status and the times you created the account and last signed in.

Sessions

• a session record with its creation, update and expiry times;
• the IP address and browser user-agent string of the session, kept for security and abuse prevention;
• a hash of the anti-forgery (CSRF) token.

Google authorisation

• the OAuth refresh and access tokens issued to us by Google, stored encrypted, together with their scope and expiry. These let the Service reach the files you connected without asking you to sign in again on every visit.

Connected files and projects

• the Google file identifier, the file name, its link, its type and its status;
• the number of rows and columns, so the project list can show the size of a file without opening it;
• the times the project was created, opened and updated.

Analysis records

• which analysis was run, its parameters, the ranges it used inside your spreadsheet, how long it took, whether it succeeded, and any error message;
• the credits it consumed.

These records describe what was run, not the data it was run on and not the numbers it produced. Results are written into your own spreadsheet.

Payments and credits

• the payment provider’s identifiers for the transaction and for you as its customer, the amount, currency, status, package name and receipt link;
• a ledger of credit purchases and spending.

Card numbers and other payment credentials are handled by the payment provider and never reach our servers.

3. What we do not store

We do not copy the contents of your spreadsheets to our servers. The values in your data, the variables you define, the settings of a project, the output of an analysis and the history of your work all live inside your own Google Sheets file, in the _ALS_ service sheets and in your data sheet.

We do not sell your data, and we do not use it for advertising or for training machine learning models.

4. Cookies

The Service uses cookies that are strictly necessary for it to function:

• a session cookie, so the site knows you are signed in between requests;
• an anti-forgery (CSRF) cookie, which prevents another site from acting on your behalf.

We do not use advertising cookies, third-party analytics or cross-site tracking.

5. Who else sees your data

We share data only with the providers needed to run the Service, and only what each of them needs:

• Google — sign-in and access to the spreadsheets you connect. Your data stays in your own Google Drive under your own Google account.
• Our hosting provider — operates the servers on which the Service runs.
• A payment provider — processes payments when you buy credits, and holds the payment details we never see.

We may also disclose information where we are legally required to do so.

6. Google API Services Limited Use disclosure

ALS Stats Labs’ use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In practice this means we use Google user data only to provide and improve the features you asked for, we do not transfer it to others except as needed to provide the Service or to comply with the law, we do not use it for advertising, and no human reads it except with your explicit permission, for security purposes, or where the law requires it.

7. Retention and deletion

• Disconnecting a project removes our pointer to that file. The file itself, including everything ALS Stats wrote into it, stays in your Google Drive and remains yours. You may delete the _ALS_ service sheets yourself at any time.
• Deleting your account removes your account record, your sessions, your stored Google tokens and your project pointers. Records we must keep for accounting and tax purposes — payment transactions — are retained for as long as the applicable law requires.
• Sessions expire automatically and are removed after expiry.

8. Your rights and controls

You can, at any time:

• revoke the Service’s access to your Google account at myaccount.google.com/permissions, which immediately stops us from reaching any of your files;
• disconnect individual projects from within the Service;
• request a copy of the data we hold about you, ask for it to be corrected, or ask us to delete your account, by writing to the address below.

Depending on where you live, you may have additional rights under data protection law, including the right to object to processing and the right to lodge a complaint with your local supervisory authority.

9. Security

• All traffic between your browser and the Service is encrypted with HTTPS.
• Google refresh and access tokens are stored encrypted, not in plain text.
• We request the narrowest Google scope that lets the Service work, so that even in the worst case the reach of a leaked token is limited to the files you chose.

No service can promise perfect security, but we keep the amount of data we hold small enough that there is little to lose.

10. Features still in development

The Service is under active development. Two planned features will change what is processed, and this policy will be updated with the name of each provider before the feature becomes available to users:

• AI assistant — optional help with choosing and interpreting analyses. Using it will send the text of your request, and in some cases parts of your data or of an analysis result, to a third-party language model provider. It will be opt-in: nothing is sent to a model unless you ask for it. We will record which model was used, how many tokens it consumed and whether raw data was included.
• Paid plans — payments will be processed by a third-party payment provider.

11. Children

The Service is not directed at children under 16 and requires a Google account. We do not knowingly collect data from children.

12. Changes to this policy

When this policy changes we update the “last updated” date at the top. For changes that materially affect how your data is handled, we will also notify signed-in users inside the Service before the change takes effect.

13. Contact

Questions about this policy, requests for access or deletion, or anything else about your data: als.stats.project@gmail.com.