Privacy Policy

Last updated: May 7, 2026

This page explains what Docs Version History ("the service", "we") collects, how we use it, and the choices you have. The service is operated by Apon.

What we collect

Account information

When you sign in with Google, we receive a basic profile from Firebase Authentication: your email address, your display name (if available), and a stable user ID. We use this to identify you and gate access to your own content. We do not receive your Google password.

Content you create

When you save a schedule, the title, your text (plain and rich formats), the chunked output, your interval choice, the creation timestamp, and your user ID are stored in Google Firestore. This content is only readable by you when you are signed in.

Google Docs OAuth tokens

When you click "Connect Google Docs" and approve access, we exchange the authorization code for access and refresh tokens and store them as HttpOnly cookies in your browser (named gd_access_token, gd_refresh_token, and gd_expires_at). These cookies are scoped to the site and are not accessible to JavaScript. We do not persist these tokens on our servers or in our database.

Imported documents

Files you upload (.txt, .md, .docx, .pdf) are parsed entirely in your browser. The original file is not transmitted to our servers; only the extracted content is loaded into the editor and is treated the same as anything you type or paste.

Local storage

We use one entry in your browser’s localStorage, called googleDocsConnected, to remember whether you’ve completed the Google Docs connection flow so the UI doesn’t flicker on page load. It is a yes/no flag and contains no personal data. It is cleared when you log out.

How we use your data

• To authenticate you and serve only your own schedules to your session.
• To save, list, load, and delete schedules you create, on your request.
• To create Google Docs in your Google account and write content into documents you authorize, on your request.
• To debug failures (export errors are logged to the browser console so you can see them; we do not aggregate analytics or telemetry).

Google account data and the limited-use disclosure

Docs Version History’s use of information received from Google APIs adheres to Google’s API Services User Data Policy, including the Limited Use requirements.

• We only request the single scope we need: https://www.googleapis.com/auth/drive.file. This restricts our access to documents the app itself creates — we cannot read, list, or modify any of your other Drive content.
• Google account data is used solely to provide the user-facing features described in this policy. We do not transfer it to others except as needed to provide those features (e.g., to call the Google Docs API on your behalf).
• We do not use Google account data for advertising. We do not sell it. We do not allow humans to read it, except in the narrow cases allowed by Google’s policy (such as where you give us specific consent or where access is necessary to comply with the law).

Third parties we use

• Google— Firebase Authentication, Cloud Firestore, Google Docs API, Google Drive API.
• Vercel— hosts the application.

These providers process your data on our behalf and are subject to their own privacy policies. We do not share your data with anyone else.

Cookies

The cookies set by the service are functional, not advertising or analytics. They are listed under "Google Docs OAuth tokens" above.

Data retention and deletion

• Schedules you save remain in Firestore until you delete them in the app.
• Token cookies persist until they expire (1 hour for access, 30 days for refresh) or until you log out, at which point we clear them.
• You can revoke our access to your Google account at any time at myaccount.google.com/permissions.
• To delete your account and all stored schedules, email abuisaapon962974@gmail.com from the address tied to your account.

Children’s privacy

The service is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us information, please contact us.

Changes to this policy

We may update this policy from time to time. The "Last updated" date at the top reflects the most recent change. Material changes will be communicated through the app or by email.

Contact

Questions, requests, or concerns: email abuisaapon962974@gmail.com.