Privacy Policy

Effective 2026-10-03

Who handles your information

Abdul Zuhaib operates Zodic. Legal operator: Abdul Zuhaib. Contact: zodic0744@gmail.com. Do not include passwords or API keys in your message.

Information used by the service

Identity: Firebase Authentication processes sign-in, name, email, account identifier and verification status. Zodic uses initials for your avatar and does not use or store a Google profile photo as your Zodic profile. Google login requests basic identity, not contacts or Drive access.

Workspace: Tasks, chat messages, execution context, run history, product selections, teams and relevant settings are stored to provide and recover your workspace. Optional memory can derive useful facts and searchable projections from permitted sources. Memory management lets you review and remove memory and control whether it is enabled.

Creator packages: Source files, package metadata, review results, immutable reviewed versions and publishing records are processed to review, list and execute agents. Your public creator name and listing details are visible with published products. Account identifiers and private adoption figures are not public marketing statistics.

Payments: Hosted checkout processes payment information. Zodic stores order, product, entitlement, status and reconciliation metadata needed to manage access, refunds and disputes. Zodic does not receive raw card or UPI credentials through its purchase forms.

Personal API keys: Session keys are temporary; saved keys are encrypted in the credential store. The trusted gateway uses the selected key for actual user-task processing. Raw keys are not sent to creator runtimes or stored in semantic memory. Removing a key stops new use of that credential; it does not reverse processing already performed by a provider. Publishing/internal reviews use platform credentials.

Processing and providers

Necessary task instructions, conversation context, memory, handoffs and tool results may be sent to the configured AI provider or approved tools to produce your requested result. A selected BYOK provider processes those requests under its own terms and billing. Zodic does not promise that external providers never retain data or train on it; check the applicable provider and account settings.

Firebase Authentication and Firestore are used for identity and application data. Dodo Payments is intended to provide hosted checkout and payment processing after account approval. AI tasks may be processed by the selected AI provider or Zodic's platform provider when production processing is available. Oracle Cloud and Pinecone are planned production infrastructure and are not represented as active until their production deployment is completed.

The production operator must keep this processor disclosure accurate. Derived search data in Pinecone is separate from canonical Firestore records. Oracle hosting and package storage are the intended production setup; this description is not a claim that pending deployment controls have been verified. Provider processing can occur outside your country.

Optional product analytics

With your permission, Zodic sends selected feature clicks, product categories and trusted task/payment statuses to PostHog under a random analytics identity. We do not send your name, email, account ID, chats, outputs, memory, API keys, creator source, private team names or raw payment identifiers. We do not use session replay, heatmaps, automatic form recording or automatic error capture. We do not forward your IP address or browser URL to PostHog.

Choose Allow analytics or No thanks when asked. Change your choice using Analytics preferences in the footer or Profile. Turning analytics off stops new capture and requests deletion of previously linked analytics; account deletion does the same. Provider outages and asynchronous deletion can delay erasure. Anonymous consent expires after 90 days. Logging out or switching accounts resets the browser analytics identity. Analytics is disabled in local development, and declining it does not restrict product features.

Security, retention and deletion

Access checks, encrypted saved keys, scoped gateway capabilities and reviewed isolated runtimes are designed to protect data. Security and operational logs support diagnosis and abuse prevention; logs should not contain raw credentials. No storage or transmission method is risk-free.

Workspace information is retained while needed to provide the service and manage your account. Use Profile → Memory management to control memory and data deletion. Deletion invalidates affected runs and starts canonical/projection cleanup; disconnected providers or recovery jobs can delay completion. Backups, payment, legal or security records may have separate retention needs. We do not promise an unsupported universal deletion deadline.

Choices, rights and contact

You can update your name, remove API keys, manage memory, delete chats and use the available account deletion controls. Applicable laws may provide access, correction, deletion, objection or portability rights. Contact the operator to make a request; identity verification may be required to protect your account. Do not send secrets with the request. Material policy changes will be reflected in this page and its effective date.

Contact: zodic0744@gmail.com. Do not include passwords or API keys in your message.