1. General Information
1.1. This Privacy Policy describes how the web application "enline" (the "Application"), owned by Rodion Trofimov (the "Author"), processes information when you use the Application.
1.2. By accessing or using the Application, you agree to this Privacy Policy.
2. Data the Application Can Access
2.1. The Application does not run its own backend database. Content that you open or create stays in your Google Drive™ account.
2.2. With your explicit consent, the Application may access:
- metadata of `.enline` files (name, size, modified time);
- archive contents of `.enline` files (JSON data and images) when you choose to open or edit a file;
- comments and discussions associated with `.enline` files;
- basic Google account identity data (
openid,email,profile) to authenticate you and display your signed-in account in the Application; - if you grant additional directory permissions, limited Google Workspace™ directory profile data (for example: display name, email, avatar) to suggest mentions in comments;
- access tokens issued by Google Identity Services™ to perform Drive operations. Tokens are stored only in your browser session or local storage and are never transmitted to the Author.
3. Local Storage and Temporary Data
3.1. The Application may temporarily store JSON drafts in your browser local storage to prevent data loss during editing. These drafts remain on your device.
3.2. When you delete a draft or clear browser storage, the locally cached copies are removed.
4. Optional Notification Services
4.1. If you enable notifications, the Application can interact with the following providers solely to deliver alerts that you configure:
- Firebase Cloud Messaging™ (Google LLC) — sends push notifications to your device or browser.
- Mailgun™ (Mailgun™ Technologies, Inc.) — delivers email reminders; the service receives the recipient address and message content required for delivery.
- Slack™ Technologies, LLC — posts reminders to Slack™ channels if you authorize a workspace.
4.2. These services receive only the data required to deliver each notification. The Author does not access or store notification payloads beyond what is needed for transmission.
4.3. Google user data is shared, transferred, or disclosed only in the following cases:
- Google LLC (Google APIs) — to authenticate your account and perform actions you request (for example, read/write `.enline` files in Google Drive™, access file comments, and resolve your Google profile details for sign-in).
- Firebase™ services (Google LLC) — for hosting, optional push delivery, and aggregated product analytics.
- Sentry™ (Functional Software, Inc.) — for application error monitoring (technical diagnostics only).
- Mailgun™ and Slack™ — only if you explicitly enable those integrations for notifications.
4.4. The Author does not sell Google user data, does not use Google user data for advertising, and does not transfer Google user data to data brokers.
4.5. Google user data may be disclosed if required by law, regulation, legal process, or to detect or prevent fraud, abuse, or security incidents.
4.6. The Application's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.
5. Hosting and Logs
5.1. The Application is hosted on Firebase Hosting™ (Google LLC) or an equivalent static host. Standard web server logs (IP address, user-agent, referrer, timestamps) may be collected by the hosting provider for security, abuse prevention, and performance monitoring.
5.2. The Author does not combine these logs with other data to create user profiles.
6. Analytics and Error Tracking
6.1. The Application uses Google Analytics™ for Firebase™ to collect anonymous usage data and Sentry™ (Functional Software, Inc.) to track application errors. This may include:
- Interaction events (button clicks, file opens).
- Session duration and user engagement metrics.
- Device and browser information (e.g., operating system, screen size).
- Stack traces and error details when the Application malfunctions.
6.2. This data is used solely to improve the Application's performance, stability, and user experience. It is not linked to your personal identity or Google Drive™ content.
7. User Rights and Controls
7.1. You may revoke the Application's access to Google Drive™ at any time in your Google account settings (https://myaccount.google.com/permissions).
7.2. You can clear cached drafts using the Application interface (where available) or by clearing your browser storage.
7.3. To stop receiving notifications, revoke the corresponding permissions for Firebase™, Mailgun™, or Slack™, or disable notifications in the Application.
8. Google User Data Retention and Deletion
8.1. `.enline` files and settings stored in Google Drive™ appDataFolder remain in your Google account until you delete them. The Author does not keep a separate server copy of Google Drive™ file contents.
8.2. Google OAuth access tokens used by the Application are stored in your browser (session/local storage) and can be removed by signing out, clearing browser storage, or using account deletion in the Application.
8.3. If you enable server-side account/notification features, the Application may store limited Google account data in Firestore (for example: Google account identifier sub, email, refresh token when provided, and token update timestamp) while your account is active.
8.4. You can request deletion of this server-side data at any time by using the in-app account deletion flow or by contacting support.
8.5. Revoking access in Google account permissions (https://myaccount.google.com/permissions) stops future API access, but does not delete files already stored in your Google Drive™.
9. Data Security
9.1. Communication between the Application and Google APIs occurs over HTTPS.
9.2. Notification keys (Mailgun™, Slack™, Firebase Cloud Messaging™) are stored only in your deployment environment and are not collected by the Author.
10. Children's Privacy
10.1. The Application is not directed at children under the age of 13. If you believe a child has provided personal information without parental consent, contact the Author to request deletion or revoke access.
11. Contact
For questions about this Privacy Policy or data handling practices, contact support:
Contact support