Privacy Policy

Version 2026-09-17-beta-1 · Effective 2026-09-17

Support and privacy: support@agendity.com

September 19 update: optional public-page analytics is available only with your permission. The analytics notice and privacy choices update the earlier analytics inventory below.

This notice explains the data flows of Agendity’s limited beta, operated by Agendity, Inc., and identifies current implementation limits. Broader production features remain subject to the checks and additional disclosures described below. Accepting service terms is not blanket consent to every use of personal data.

1. Who is responsible

Agendity, Inc., a Delaware corporation with a company address at 529 Main Street, Charlestown, MA 02129, United States, determines how account, billing, security and direct support information is used. When a business uses Agendity to run a character in its own chatbot or website, that business normally determines the purpose of its end users’ conversations; Agendity processes the instructed service data for it, as specified in the applicable data processing agreement. A provider or business may have a different role for its own independent processing.

If you interact with a character on someone else’s website, read that website’s notice and contact its operator about your conversation. We will assist our business customer with valid requests where required. We also address requests concerning data we control. Contact support@agendity.com for privacy requests, whether you use Agendity as an individual or for a business.

2. Information involved

• Account information: name, email, verification and sign-in records, account identifiers, preferences and any profile image supplied by your sign-in provider. Google sign-in does not give us your Google password or permission to read your inbox.
• Beta access information: email address, request/approval status and dates, invitation delivery records and administrative access decisions. A pending request is kept separately from authentication accounts. Necessary invitation and approval messages are not a marketing subscription. We use keyed hashes of request IP addresses for application abuse limits, rather than saving raw IP addresses in those counters; hosting providers may have their own access logs.
• Creative workspace data: descriptions, refinement messages, reference files, generated artwork and backgrounds, selected versions, approvals, persona and language instructions, voice choices and framing settings. Avoid including unnecessary personal information in a prompt.
• Processing records: job identifiers, stage events, timestamps, cancellation requests, input/output checksums, provider request identifiers, errors, token or audio usage and cost records. These support recovery, security and accurate charging.
• Conversation data, when enabled: the reply text, microphone audio, transcripts, synthesized speech and timing information needed for the selected integration. The provider route and customer configuration determine which of these reach our servers and are retained.
• Billing and support: plan and invoice references, transaction status, necessary billing details, correspondence and feedback. Hosted checkout is intended to let the payment processor collect card details directly; full payment-card numbers should not be entered into Agendity prompts.
• Technical data: session and security tokens, IP/device/browser information received during requests, basic operational logs and browser storage needed to keep work and sign-in reliable.

3. Why we process it

We use necessary information to create accounts, keep your projects available, execute instructions, authorize access, deliver requested voice and character features, support integrations, bill correctly, prevent abuse and respond to support requests. We may preserve limited records to comply with legal duties or establish and defend claims. Optional marketing or unrelated analytics requires its own assessed lawful basis and, where required, a separate choice.

Where European or UK data protection law applies, processing may rely on performing a contract or taking requested pre-contract steps, legal obligations, legitimate interests balanced against individual rights, or consent where appropriate. Legitimate interests can include securing accounts and maintaining reliable services; they are not a catch-all permission to use sensitive content for unrelated purposes. Consent can be withdrawn without making earlier lawful processing unlawful. The final legal-basis assessment must match the operator, audience and actual deployment.

4. Voice, images and integration modes

In existing-audio mode, a customer supplies a stream or audio and may also supply text. Its upstream chatbot and voice provider remain part of its own processing arrangement. Agendity processes only the payload and metadata actually routed to its components; we do not promise that every third-party stream remains entirely on-device.

In chatbot-to-voice mode, the reply text is sent through the chosen speech provider, and the Player uses the resulting audio and timing information. A full-agent or live-talk mode may also send microphone audio, transcripts, instructions, conversation context and authorized tool results to the selected conversation provider. The interface should identify the active mode and provider before a call starts. Microphone capture requires a user action and browser permission. Text-only use does not require microphone access.

A photo or voice recording can be personal data even when it is not used to identify a person. Some likeness processing, voice cloning or derived features may be regulated as biometric data depending on the process and law. The new platform does not currently implement biometric identification or custom voice cloning. Those features must not be introduced under this notice without a specific assessment, required permissions, retention controls and updated disclosures.

5. Providers and disclosures

Necessary service providers may receive the relevant data for database hosting, job execution, storage, email, payments, AI generation, speech and hosting. The Providers page distinguishes what is active in this foundation from what is planned or used in the separate character runtime. It is not yet a finalized contractual subprocessor register.

We may disclose relevant information to authorized personnel and advisers for support, security and legal purposes, to comply with binding legal requirements, or in a business reorganization subject to appropriate safeguards. Publishing a release makes its configured presentation available to its intended audience. Viewers can capture or copy public output. Customer-managed websites and connected tools have their own privacy practices.

The current platform foundation has no advertising pixels, cross-site advertising integration or marketing profiling. We do not sell personal information or share it for cross-context behavioral advertising in this implementation. Adding such a practice would require a new assessment, notice and applicable opt-out or consent mechanism before activation.

6. Training and service improvement

The platform saves briefs and drafts. When an operator enables the isolated generation pilot, the requested prompts, selected references and relevant character context are submitted to generation providers; paid requests and outputs have durable records. Image generation and character authoring have been exercised in staging. They are not enabled for unrestricted customer use. Agendity does not operate a general-purpose model-training pipeline. Our proposed production policy is not to use private customer content to train general-purpose models without separate explicit permission. This is a proposed policy, not an unverified promise about every external provider’s account configuration.

Before activating a model or voice route, Agendity must verify its contractual data-use terms, retention, available opt-outs and account settings. Necessary processing to generate your requested result, safety review, temporary provider retention and use of content for training are different activities and must not be described as interchangeable. Do not assume a provider retains nothing merely because an interaction is streamed.

7. Retention and deletion

Durable work deliberately persists after you leave. The platform stores saved briefs, conversations, workspace drafts and operation records in its isolated database, with generated images and authoring checkpoints in private object storage. Anonymous brief access expires after 24 hours, email sign-in links after 10 minutes, and sessions are configured for a rolling 14-day lifetime. Expiration of access does not itself delete the underlying database row. Where published terms require acceptance, the account identifier, document version, document checksum and acceptance time are recorded. No optional marketing consent is inferred from that record.

Saved projects remain until removed through a supported deletion process; archiving only hides them from the active library. Operational receipts can be necessary to prevent duplicate processing and charging. The public retention schedule for projects, recordings, transcripts, logs, financial records, deleted assets and backups is not yet finalized. Automated purge and self-service account deletion are not implemented in this foundation and must be completed before production launch.

The final schedule will explain retention by purpose, plan and integration, deletion propagation to providers, backup rotation, legal holds and exports. We will restrict rather than repurpose records retained solely for legal or security needs. Copies held by a customer or downloaded by a viewer are outside an Agendity deletion action.

8. International processing and security

Processing can occur outside your country, including where our selected providers operate. The current isolated Neon staging database is in AWS US East (Northern Virginia); that is not a commitment to a production residency region. Locations, relevant entities and transfer safeguards must be verified for each production route. Where required, transfers need an applicable adequacy decision or approved contractual safeguards and supplementary measures; this notice does not claim they are already in place.

The foundation uses server-side credentials, encrypted database connections, session validation, scoped ownership checks and row-level policies on new workspace records. Production security also requires monitored access, incident handling, tested backups, supplier review and deletion controls. No system is perfectly secure. This notice makes no certification, penetration-test, HIPAA, SOC 2 or other compliance claim. Required breach notices will follow applicable law and any signed data processing agreement, not a blanket deadline.

9. Your choices and rights

You may have rights to access, correct, delete, receive or transfer your information, restrict processing, object to certain uses, withdraw consent, or appeal a decision. The applicable rights depend on your location and our role. We will verify requests proportionately, not ask for unnecessary identity documents, and respond within applicable legal time limits. Exercising protected rights should not result in unlawful discrimination.

Where applicable, you may authorize an agent to act for you and complain to your local data protection authority, including an authority where you live or work. Contact support@agendity.com for requests or questions. In customer-hosted conversations, the customer may need to handle your request as controller. The in-product profile currently supports name and preference changes; it is not a complete privacy-request portal.

10. Children, sensitive use and updates

Account creation is intended for adults. The platform is not currently approved for child-directed deployments, biometric identification or sensitive regulated workflows. A tutor character’s theme does not itself authorize collecting children’s information. Such uses require a separate assessment and appropriate age, guardian, data-minimization and contractual controls before launch.

We will keep a versioned notice and explain material changes before newly affected processing where required. Optional consent will not be inferred from merely reading the notice or continuing to use unrelated features. Expanded production disclosures and retention controls, including for pending/declined beta requests, remain launch requirements. You can contact support@agendity.com to withdraw an access request or raise a privacy concern.