Aggregate usage counts
TripDeck uses first-party counts to understand whether people can get from signup to a useful report. This page supplements the Privacy Policy; it does not mean that all application data stays only on your device or in Google Drive.
Website activity
When enabled, selected marketing pages send a page-view event and, if clicked, a signup-link event to TripDeck’s application server. These are event counts, not unique visitor counts, and are not linked to your account or followed across websites.
The counter sends the event type, an approved page path, and a random identifier for that individual event. The identifier is used briefly to reject duplicates, not stored in the analytics database, and not reused to recognize you. It sends no form contents, query strings, full referring URLs, or payment details and sets no tracking cookies or persistent browser identifier.
The server necessarily receives network request information. It uses a short-lived, in-memory keyed hash of the network address for rate limiting; that hash is not stored in analytics or linked to accounts. Hosting and security logs are separate from these counters.
Account milestones
The application counts successful account creation, first profile completion, and successful report responses. It uses an existing internal account ID and milestone timestamps to avoid double counting and calculate signup-to-profile-to-report completion. The owner dashboard returns aggregate totals, not lists of users.
The analytics tables do not contain names, email addresses, contact details, notes, images, report text, or payment data. A successful report response does not prove that a file was saved, opened, or read.
Retention and access
Daily counters and account-milestone records are retained for up to 90 UTC calendar dates and pruned during subsequent tracking or dashboard activity. Account-linked milestone records are also removed when the associated account is deleted. Earlier raw history is not backfilled.
Only explicitly configured owner accounts can retrieve the dashboard totals. There are no third-party analytics pixels, advertising profiles, fingerprinting, or session recordings in this feature.
The optional Easy-Peasy.AI website chat is separate from these counters. It loads only after you choose Start chat and follows the provider's data practices described in our chat privacy notice. Counter opt-out controls do not disable a chat you explicitly start.
Your choices
The marketing counter honors browser Do Not Track and Global Privacy Control signals where available. You can also load a page with ?td_analytics=off to suppress its marketing counters for that page load. These controls do not disable account operations or their first-party completion counts.
To ask about account-linked usage data or request access, objection, or deletion, contact [email protected]. You do not need to share report contents to make a request.