Effective Date: June 1, 2026
At KISS Tracker, we follow the KISS principle (Keep It Simple, Senior) not only in our code but also in how we handle your data. Our philosophy is simple: your data is yours, and we don't want it.
1. No Backend Architecture
KISS Tracker is a serverless Chrome Extension. We do not own, operate, or maintain any external databases or servers that store your project data.
2. Data Storage and Access
Google Sheets: All your project data (tasks, statuses, comments, custom columns) is stored exclusively in your own Google Sheets. The extension acts only as a UI layer on top of a spreadsheet you already own.
Chrome Local Storage: We use Chrome's local storage only to keep track of your trial start date and basic UI preferences (active view, sort order). No project data is stored locally.
No Data Export: No project data from your Google Sheets is ever transmitted to us or any third party.
3. Google Workspace Permissions
To function, the extension requires access to:
▸ Google Sheets API — to read and write your project data directly in your spreadsheet.
▸ Google Drive API — to identify spreadsheets with [kiss-tracker] in the title and to read sharing permissions for the collaborator list.
▸ Google Identity (OAuth) — to authenticate your Google account for API access. No credentials are stored by the extension.
All data retrieved via these APIs is processed locally in your browser and is never sent to our servers.
4. Payments and Licensing
We use ExtensionPay (extensionpay.com) as our payment platform, which is backed by Stripe for payment processing.
When you subscribe, Stripe handles your payment information (card details, billing address, etc.). We do not see or store any financial data.
We only receive confirmation that your account has an active subscription. No license keys are issued or stored — access is tied to your Google account via ExtensionPay.
ExtensionPay is subject to its own Privacy Policy (extensionpay.com). Stripe is subject to Stripe's Privacy Policy (stripe.com).
5. Third-Party Services
▸ Google APIs — subject to Google's Privacy Policy (policies.google.com/privacy).
▸ ExtensionPay — subject to ExtensionPay's Privacy Policy (extensionpay.com).
▸ Stripe — subject to Stripe's Privacy Policy (stripe.com/privacy).
We do not use any analytics, advertising, or tracking services.
6. Changes to This Policy
If we ever add a backend or change how data is handled, we will notify all users via an extension update and update this policy with a new effective date.
7. Contact
If you have any questions about this privacy-by-design approach, feel free to reach out via the social links in the extension's Info Modal or through www.kissapproach.com.