chaintrace-privacy

📌 Quick links


🌐 Landing page	https://projekta2.github.io/chaintrace-landing/
🎮 Interactive demo	https://projekta2.github.io/chaintrace-landing/chaintrace-demo.html
💎 Get Premium	https://projekta2.gumroad.com/l/chaintrace-premium
📧 Contact	hello@projekta2.com
🔗 LinkedIn	Alexandre Iglesias
🐙 GitHub	@projekta2
⚖️ Terms of Service	https://projekta2.github.io/chaintrace-terms/

1. Zero data collection – this is not a metaphor

ChainTrace is designed from the ground up to never send your data anywhere unless you explicitly export it.

No telemetry – The extension does not contain any analytics, tracking pixels, or session recording.
No external servers – There is no ChainTrace server. Everything runs inside your browser.
No data transmission – Your captured data is never sent to us, nor to any third party, unless you click “Export to Google Sheets”, “Download CSV”, or “Send to API”.

2. What data is stored – and where

Data	Storage location	Purpose
Capture history (last 20 captures)	`chrome.storage.local` (your browser)	Allow you to restore previous captures
Recipes (validation rules per website)	`chrome.storage.local`	Auto‑apply rules when you revisit a portal
Export profiles (spreadsheet URL, API endpoint)	`chrome.storage.local`	Save your preferred export destinations
Google OAuth2 token (if you use Sheets)	`chrome.storage.local`	Authenticate you with Google — never accessible by us
Premium license key (if purchased)	`chrome.storage.local`	Verify your Gumroad license (fingerprinted, salted)

All this data stays on your computer. It is never transmitted to any ChainTrace‑controlled server.

3. External communications – what, why, and how often

ChainTrace makes only three types of external requests, all initiated by you or strictly necessary:

3.1 Google Sheets API (optional)

When: You click “Send to Sheets”
What: Your captured data is sent to sheets.googleapis.com using your own OAuth2 token
Why: To write the data into your chosen spreadsheet

3.2 Gumroad license verification (Premium only)

When: You enter your license key, and once every 24 hours (background check)
What: The extension calls api.gumroad.com/v2/licenses/verify with your key
Why: To confirm your Premium status. No other data is sent. Gumroad’s privacy policy applies.

3.3 Your own API endpoint (optional)

When: You configure REST API export and click “Send to API”
What: Your captured data is posted to the endpoint you provide
Why: To push data into your ERP, WMS, or custom tool

No other network requests are made. The extension does not ping any home server, does not collect crash reports, and does not check for updates behind a central server (Chrome handles updates automatically).

4. Permissions – why they are needed

Permission	Why
`activeTab`	To read data from the currently open supplier portal when you click “Capture”
`storage`	To save your Recipes, history, and export profiles locally
`scripting`	To inject the content script that extracts tables and handles manual selection
`downloads`	To generate CSV and XLSX files when you export
`identity`	To authenticate with Google for Sheets export (OAuth2)
`host_permissions` (optional)	To allow API export to your chosen endpoint – you are asked for permission per domain

5. Your rights

Because ChainTrace does not collect your data on our servers, there is no personal data to access, delete, or rectify. Your data is entirely under your control.

If you have questions, contact us at hello@projekta2.com – we will respond personally.

6. Changes to this policy

Any future changes will be documented here, with the “Last updated” date updated accordingly. Material changes will also be announced in the extension’s release notes.

7. Contact

For privacy concerns, data access requests, or any question regarding how ChainTrace handles your information:

📧 hello@projekta2.com
🌐 https://projekta2.github.io/chaintrace-landing/

_{ChainTrace is built in Girona, Spain. No tracking. No tricks. Just a tool that respects your data.}