Carbon Alliance Trust Center

We collect account data, profile fields, authentication events, public community content, reviews, votes, reports, appeals, search interactions, Agent conversations, Agent memories, scheduled Agent tasks, and service diagnostics needed to operate the platform.

Some sensitive account data, such as email addresses and credentials, is protected through application-level security controls and encrypted storage where supported by the infrastructure layer.

We use data to authenticate users, operate public community surfaces, rank and search AI tools, personalize Agent experiences, prevent abuse, support moderation, provide data export and deletion workflows, and improve reliability.

AI usage metadata such as capability name, model, token counts, latency, and estimated cost may be recorded for budget governance and operational safety.

Published posts and published or verified reviews can be visible to other users. Public profiles can appear in author bylines, search, and profile pages.

Private Agent conversations, Agent memories, account settings, export jobs, deletion requests, and authentication audit logs are treated as private account data and are not exposed through public community pages.

Certain Agent and AI capabilities may send prompts, tool context, or generated outputs to configured AI model providers through the platform AI routing layer.

We may also use providers for email delivery, object storage, observability, payments, and infrastructure operations. These integrations should be limited to the data required for the relevant service.

You can update profile fields and privacy preferences, request a synchronous JSON export, request an asynchronous export with a 7-day download link, and request permanent account deletion with a 30-day cooling-off period.

Account deletion anonymizes the user identity and disables public profile and Agent preferences while preserving records needed for integrity, audit, legal, or abuse-prevention purposes where allowed by law.

We retain data for as long as needed to provide the service, satisfy legal obligations, protect users, resolve disputes, and maintain audit trails.

Security controls include password hashing, OAuth state protection, rate limiting, session management, audit logs, role-based admin access, and event-driven operational records.

The v1 service is designed around Hong Kong-hosted primary infrastructure, Cloudflare-backed media delivery, and backups or standby systems as defined by the project infrastructure plan.

The privacy program is oriented around GDPR, CCPA, Hong Kong PDPO, and future regional compliance work before expansion into additional regulated markets.

Business requests and their files are visible only to the requester and authorized business administrators. Sensitive request content, messages and attachments are encrypted in storage. Requests are not published, indexed in public search, sent to AI models or automatically shared with suppliers. Your current verified account email is used for contact.

Active requests are retained until they end or you delete them. For completed or closed requests, private content and files are scheduled for deletion after 180 days, with an export reminder scheduled 14 days before expiry. You may delete a request earlier from its detail page. The 180-day period is a product retention policy, not a determination of legal retention duties.

Account data exports include your business request details, requester-visible correspondence and original attachments. Internal administrator notes are not included in the automatic export; requests for access to those records are handled through the existing support process. Exports containing business data are stored as encrypted snapshots.

Deleting or expiring a request, or completing account deletion, clears its private content and attachments, cancels pending notifications and invalidates existing export snapshots and download links containing that data. Files you have already downloaded to your own device cannot be remotely recalled.

Historical backups are retired under the existing backup rotation policy; deletion does not promise immediate physical erasure from every historical backup. After a restore, deletion and expiry records must be applied again before restored business data is made available.