Users, customers, partners, and reviewers checking how AYA handles privacy.
Provide a crawlable entry point for privacy information.
Information AYA processes
AYA may process account details, contact information, workspace settings, research briefs, uploaded stimulus, product usage events, support messages, billing metadata, and technical logs needed to operate, secure, and improve the service.
How information is used
Information is used to provide research workflows, authenticate users, manage billing, maintain security, respond to support requests, improve reliability, and communicate about the service. Customer research content is handled as customer-controlled input for the requested workflow.
Sharing and subprocessors
AYA uses service providers for hosting, database infrastructure, payments, analytics, email, and support operations. These providers are expected to process information for service delivery rather than independent advertising use.
User rights and requests
Visitors and customers can contact AYA about access, correction, deletion, portability, objection, restriction, cookie choices, and privacy questions. Requests should include the account email, jurisdiction, and the specific right or record involved.
Related compliance pages
People reviewing privacy should also read AYA terms, GDPR information, cookie policy, methodology, and contact pages before procurement or deployment.
Operational scope
This public policy page is intended to help visitors, customers, procurement teams, and AI agents understand AYA governance at a high level. Contract-specific commitments, data processing terms, and security reviews should be confirmed directly with AYA before purchase or deployment.
Related review path
Review this page alongside the privacy, GDPR, cookie, terms, methodology, and contact pages. Together they explain how AYA should be evaluated as a public website, commercial service, and AI-native research platform.
Procurement note
Legal and compliance readers usually need to understand data categories, account responsibilities, acceptable use, retention expectations, cookie choices, customer content handling, payment terms, and how AI-generated research outputs should be interpreted. These public pages provide crawlable orientation for those questions, while the final contract, data processing agreement, and security review should control any customer-specific commitments.