Privacy Policy
Effective date: March 13, 2026. This notice explains what Autonomy Gradient collects, where it is sent, and how you can control analytics and contact us about privacy.
What we collect
We collect standard request metadata needed to operate the site, including IP-derived client identifiers for abuse prevention and CloudFront viewer location headers for country, region, city, and time zone. We also collect the content you actively submit through assessments and the contact form.
Assessment submissions
Assessment submissions are stored in our application database together with the submitted answers, selected scope size, generated mode and narrative output, request timestamp, and viewer location fields described above. We use this data to generate your result, produce aggregate benchmarks, analyze trend lines, and maintain service integrity. Do not submit personal, regulated, confidential, or customer-specific data.
Contact requests
If you use the contact form, we collect your name, email address, and request text so we can respond. Contact requests are delivered through communication providers for operational triage and may also be logged in application logs for error handling, abuse prevention, and support follow-up. Do not include confidential or sensitive information in contact submissions.
Analytics and cookies
If you explicitly opt in, we load Google Analytics and allow first-party analytics storage to measure site usage. If you decline, Google Analytics stays disabled. We store your analytics choice in a first-party consent cookie and matching local browser storage so the site can remember your preference.
Benchmarking and research use
By using the assessment tool, you grant Autonomy Gradient a non-exclusive, worldwide, royalty-free license to use submitted assessment data in anonymized, aggregated, and de-identified form for benchmarking, whitepapers, trend analysis, and product improvement. We do not sell your specific company identity or disclose raw assessment submissions to third parties without explicit consent.
Processors and sharing
We use third-party providers to run the service, including AWS for hosting, Google for analytics when consented, communication providers for contact request delivery, and GitHub for public repository collaboration. These providers may process data outside your country. We do not sell personal data.
Retention
Assessment submissions and derived analytics are retained while they remain useful for benchmarking, research, product improvement, fraud prevention, and service operations. Contact requests and operational logs are retained for support, security, and audit purposes. We are still formalizing fixed deletion windows, so some records may remain until manually cleared or superseded.
Your choices and rights
You can decline analytics from the consent prompt or reopen analytics settings from the site shell at any time. Depending on your location, you may also have rights to request access, correction, deletion, or objection to certain processing. For privacy questions or requests, use the contact page, state that your inquiry is privacy-related, and include enough context for us to locate the record. We aim to respond within 30 days. We can usually verify and act on identifiable contact-form submissions. Assessment submissions are intentionally non-account-based, so we may only be able to locate or delete them when you provide enough matching context, such as the approximate submission date, assessment mode, and result context.
Community contributions
If you submit model-language edits or blog drafts through our public GitHub workflow, your submission content, commit metadata, and public account information may be processed and retained as part of repository history and editorial review. Submit only information you are comfortable sharing publicly.
Policy updates
We may update this policy as the platform evolves. Updated versions are effective when posted on this page. If changes materially affect how we use personal data, we will update this effective date and publish the revised notice here.