Privacy Policy

1. Information TraceTray collects

TraceTray may collect the following types of information:

• account information from Clerk or a connected sign-in provider, such as your Clerk user ID, email address, name, profile image, account timestamps, and authentication status;
• account settings, including your generated TraceTray site key, website URL, selected plan, and account creation date;
• website interaction data sent through the TraceTray tracker, including cursor coordinates, cursor movement timing, pauses, clicks, taps, scrolling, page and referrer addresses without their query strings, session timing, device category, a randomly generated session identifier, and a daily visitor identifier described in section 8;
• limited information about clicked or tapped page elements, such as the element tag, ID, CSS classes, and up to 50 characters of visible element text;
• analysis data, including calculated interaction features, browsing-pattern groups, statistical results, summaries, suggestions, and historical analysis results;
• bug reports, including the category, description, dashboard section, page URL, browser user agent, account identifiers, and submission time;
• subscription status and billing identifiers if paid plans are introduced, such as Stripe customer and subscription IDs;
• basic technical information that may appear in server or hosting logs, such as IP address, request path, browser information, timestamps, errors, and security events.

2. Account information and Google sign-in

TraceTray uses Clerk for sign-in, account sessions, and account management. When you use Google or another connected sign-in method, TraceTray receives only the account information made available through Clerk for authentication and account setup, generally an account identifier, email address, name, and profile image.

Google account information is used only to provide sign-in, identify your TraceTray account, and operate account-linked features. TraceTray does not use Google account information for advertising, does not sell it, and does not request access to Gmail, Google Drive, Google Calendar, or other unrelated Google services.

3. Behavioural website analytics

TraceTray customers add a JavaScript tracker to pages they choose to analyze. The tracker records interaction events needed to describe how visitors browse those pages. This can include movement coordinates, scroll positions, pauses, clicks, taps, page transitions, and session duration.

The tracker is not designed to record keystrokes, passwords, form-field values, payment details, or full session video. However, click and tap events may include a short excerpt of visible text from the selected page element. Website owners should avoid placing sensitive personal information directly inside clickable labels or elements that they choose to track.

4. Site owner responsibilities

Website owners using TraceTray are responsible for deciding whether the tracker is appropriate for their website and for providing any privacy notice, consent mechanism, cookie banner, opt-out, or other disclosure required by the laws that apply to them and their visitors.

Do not use TraceTray on pages intended to collect highly sensitive information, and do not configure it in a way that intentionally sends passwords, payment information, health information, government identifiers, or other sensitive personal data.

5. How information is used

TraceTray uses information to:

• create and manage accounts and site keys;
• receive, organize, and display website interaction sessions;
• calculate behavioural features and group similar browsing patterns;
• produce dashboard summaries, trends, journeys, comparisons, and areas to review;
• respond to bug reports, support requests, misuse, and security issues;
• operate future subscriptions and confirm plan access;
• maintain, debug, secure, and improve TraceTray.

6. Automated summaries

TraceTray may send summarized analysis information to Anthropic's API to produce readable explanations and suggested areas to review. When you use Ask, your question, recent conversation context and relevant website analytics are also sent to Anthropic to answer it. Avoid including passwords, payment details or personal information in your questions. The prompt may include aggregate cluster statistics, click summaries, page URLs, device comparisons, and calculated behavioural patterns. TraceTray does not intentionally send raw passwords, form entries, or full account credentials to Anthropic.

Automated summaries may be incomplete or incorrect. They are intended to help interpret the measured data, not to make legal, employment, medical, financial, or other high-impact decisions about individual visitors.

7. Third-party providers

TraceTray relies on third-party providers to operate the service. This currently includes Clerk for authentication, Google as an optional sign-in provider, Anthropic for automated analysis summaries, MongoDB for data storage, Discord for private staff notifications (bug report text, subscription events and error details, sent to a channel TraceTray's operator and authorized moderators can read), Amazon Web Services for sending TraceTray's emails and storing encrypted database backups, Stripe for payments and subscriptions, and hosting or server infrastructure for running the website and API.

These providers may process information under their own terms and privacy policies. TraceTray does not control their systems, availability, security practices, or independent retention requirements.

8. Cookies, local storage, and visitor identifiers

The TraceTray tracker does not set cookies or store anything on a website visitor's device. The one exception is opt-in: when someone opens a site with TraceTray's ignore link (for example the site's owner excluding their own browser), the tracker saves a single flag in that browser so it stops recording there, and removes it when the undo link is opened. To group one person's page views into a browsing journey, TraceTray's server creates a visitor identifier by hashing a random value that changes every day together with the website's key, the visitor's IP address and browser details (its version and preferred languages, which browsers send with every request). The IP address is not stored, and each day's random value is deleted once the next day begins, so identifiers from different days cannot be linked to each other or traced back to a person. Visitors are not recognized from one day to the next. Requests from the tracker are not written to TraceTray's server access logs. What TraceTray collects lists every field.

Older versions of the tracker kept a visitor identifier in the browser's local storage; the current tracker removes it. On TraceTray's own website, Clerk's sign-in cookies are only set once you sign in, and only browsers that have signed in before load Clerk on the public pages. Browser storage keeps preferences such as light or dark mode and remembers that you've signed in.

TraceTray does not currently use behavioural tracking data for advertising.

9. Data sharing

TraceTray does not sell personal information. Information may be shared with service providers when needed to operate TraceTray, comply with law, investigate misuse, protect users or the service, or complete a business transfer such as a merger or sale.

Account holders can view analytics connected to their own TraceTray site key. TraceTray does not make individual visitor sessions public.

10. Data retention

TraceTray keeps account information, website sessions, analysis results, bug reports, and operational logs for as long as they are reasonably useful for providing the service, showing account history, handling support, investigating misuse, maintaining backups, or meeting legal and security needs. Detailed movement data from website visits (cursor positions, clicks, taps and scrolling) is deleted after 90 days, and each visit's summary after 13 months; daily page totals and analysis results are kept.

After a paid subscription ends, the account's website data (visits, analyses and page history) is kept for 30 days and then deleted, with a notice sent 7 days before. The account itself is kept so it can be used again, unless you request permanent account deletion as described in section 11.

Encrypted database backups are kept for 30 days, so deleted information may remain in a backup until it expires. Other retention periods may vary by data type and may change as TraceTray develops.

11. Your choices and deletion requests

You may stop future tracking on a website by removing the TraceTray tracker from that site. Account holders may reset stored page history from the dashboard where available.

You can delete your TraceTray account on the web or choose Account, then Delete account in the Android app. This closes the account, cancels active TraceTray subscriptions and removes the sign-in, websites, visits, analyses, screenshots, settings and account-linked bug reports. The deletion process also removes matching account-linked support and billing alerts posted by TraceTray's Discord bot. Failed deletion steps retry automatically, including provider cleanup. A deletion receipt with limited account identifiers (which can include your email address, account, customer and website identifiers) and request status remains for 30 days to handle retries and prevent accidental reactivation. Backups expire within 30 days; payment providers may retain transaction records required by law. Limited operational logs may remain where needed for security, incident investigation or legal obligations.

For help with deletion, access, correction, or other data requests, contact support@tracetray.com. TraceTray may need to verify the request before changing or deleting account-linked information.

12. Children

TraceTray is not intended for children. Account holders should not knowingly use TraceTray to collect behavioural data from children where doing so would require parental consent or additional legal safeguards that have not been obtained.

If you believe a child has provided personal information to TraceTray in a way that should be reviewed or removed, contact support@tracetray.com.

13. Security

TraceTray uses service providers and reasonable technical practices to protect accounts and stored data. No online service can guarantee perfect security. Account holders are responsible for keeping their sign-in method and site key secure.

14. International processing

TraceTray and its providers may process information in countries other than the country where an account holder or website visitor is located. Those countries may have different data-protection laws.

15. Changes to this policy

TraceTray may update this policy as the service, providers, or data practices change. The latest version will be posted on this page with an updated date.

16. Contact

Questions or requests about privacy can be sent to support@tracetray.com.