Your details.
Here is how we use them.

Research rights reports

Anyone can submit a licensing concern without an account. We store the selected claim and source, your explanation, optional email, submission time and reference. These reports are visible only to the site owner and hosting provider, for investigating rights concerns. We do not send them to AI models or use them for marketing. Abuse prevention stores a daily hash derived from the connection address for up to two days; the reporting feature does not store the raw address. Owner decisions and delivery receipts are retained in a private audit trail. Only a substantiated withdrawal creates a separate removal request, limited to the identified claim; reporting does not automatically remove material. The removal handoff contains claim/source identifiers and release proof, not your explanation or contact details. Reports are retained as a rights-case record; request correction or removal by submitting a follow-up with the reference.

What we store

We store a generated account identifier, your email, a securely hashed password and sign-in sessions. We also store your name, company, role, optional use case and account status. Sales Process Review stores the company context and process observations you submit, the resulting report, and your feedback and our replies. The owner can also keep a private account note. If you choose to complete a review check-in, we store its date, what you say you tried, an optional usefulness rating and any optional interest in a deeper review. We do not ask for customer names or deal records in that check-in.

How it is used

Account data is used for beta access and permission checks. Signing up does not subscribe you to marketing email, charge a payment or send your profile to an AI model. Beta report generation uses a defined diagnostic playbook and a published research snapshot; it does not make external AI calls. GTM Architect manages its own accounts. Passwords are hashed with scrypt and never stored in readable form. An email address is marked unverified until email ownership is confirmed.

Storage and access

Account records are stored separately from the research corpus in the site’s Cloudflare database. The owner can manage accounts and read submitted feedback. Reports are isolated by account; other users cannot access them. Other members cannot view your account details. Site hosting and authentication also process technical request information to operate the service.

Learning whether the beta is useful

The owner sees aggregate counts of registrations, completed profiles, report use, feedback and voluntary check-ins. These help identify where people stop and whether the review gives them a useful next step. Check-ins are self-reported observations, not verified business results. Interest in a deeper review is not a purchase, commitment or permission to send marketing email. This feature adds no advertising tracker or cross-site browsing profile.

Article and download counts

Our first-party counter records daily totals for opened article pages and clicked PDF or ZIP links. The counter stores no account or reader identifier, address or address hash, user-agent, referrer, search text or browsing profile. Each event has a separate random receipt so retries do not count twice for 48 hours; it is not reused to identify a reader. Receipts expire after 48 hours and are deleted on a following activity submission. Daily aggregate reporting covers up to 365 days, with older rows also removed on a following submission. No advertising or third-party analytics service receives these events. Normal hosting services still process technical request information to serve the site.

These totals are non-unique client reports, not people or confirmed downloads. Repeat visits and automated activity may count; direct file requests, disabled JavaScript and blocked reports are not measured. Counting failure does not stop an article or download. Only the owner sees the aggregates.

Research ratings

Voting uses a random identifier in your browser storage. We store that identifier, the claim, your vote and its update time while the rating service operates. No account or email is required. Only totals are public. Click your selected thumb again to remove your vote. Clearing browser storage loses the ability to change earlier votes and does not delete them. Daily connection hashes limit abuse and expire after two days; this feature does not store raw IP addresses. Ratings are reader opinions, not evidence approval.

Retention and removal

Account details and saved reviews are retained while your beta account is active. You can edit your profile in My account. Account removal currently has to be handled by the owner. Use the feedback form in your review to request removal; the owner handles it. Removal clears your profile, saved reviews, feedback, voluntary check-ins, request text and private notes, removes password credentials and sessions, revokes access and retains a minimal sign-in identifier and permission history to prevent unintended reactivation. Permission history contains status, dates and module assignments, not copies of your profile text.

Downloads do not require an account

Public articles remain available without an account. Registration unlocks the free Sales Process Review beta after you complete your profile. Other tools and the research workspace are not included. No card details are collected here.