Privacy Policy
This policy explains how Agivo handles information when you visit the service, create an account, or publish a project. Websites published by users may have their own data practices; this policy does not describe those users' independent collection.
Information the service processes
- Account information: your email address, a password hash rather than your plaintext password, account identifiers, and email verification status.
- Authentication information: session cookies and server-side session records, hashed API credentials with names and usage metadata, and verification or password-reset records.
- Hosting information: uploaded files, project names, deployment history, ownership, access settings, and storage usage. Files may contain information you or your agents provide.
- Operational information: request details such as IP addresses, requested URLs, browser information, timestamps, errors, rate-limit activity, and aggregate daily project view counts.
- Account email information: recipient address, verification or reset message content during delivery, and delivery status records.
How information is used
Agivo uses this information to authenticate users, host projects, manage deployments and quotas, send requested account emails, prevent abuse, diagnose failures, and protect the service. Session and security cookies support login and form protection. Logging out ends the current session; it does not delete the account.
Cloudflare and other recipients
Protected account forms use Cloudflare Turnstile. Your browser connects to Cloudflare, which processes technical signals to assess automated traffic; Agivo sends the challenge response and the requesting IP address for validation. See Cloudflare's Privacy Policy for its practices.
Infrastructure used to run Agivo processes service data. Account emails pass through mail systems, including your email provider. Publicly hosted files are delivered to visitors and can be copied or indexed. Information may also be disclosed when required by law or necessary to investigate abuse and protect the service or others. Do not treat public hosting as private storage.
Retention and deletion
Account records, project files, deployment history, and operational records can remain stored after you stop visiting. Temporary projects have an expiry and cleanup process; claiming a project removes its temporary expiry. Expiration is not a promise that every related record or backup is immediately erased. Email delivery processing clears completed message payloads, but delivery metadata, database history, and backups may remain.
The current dashboard does not offer account deletion or a general data-erasure request form. This policy does not promise a fixed retention period or automatic account deletion. Revoking an API token prevents its future use but does not delete project files or all credential metadata.
Your available controls
Use the dashboard to review projects and revoke API tokens. You can log out, use password recovery, and review email verification. Your browser lets you clear stored cookies; doing so signs you out but does not erase server-side information. Keep private claim links and credentials out of public uploads.
Policy updates
Changes to this policy will be published on this page. Review it when deciding what information to provide or publish.