Privacy Policy

Project source files, attachments, Executor deliverables, and customer-owned API keys remain on the customer computer. To continue across AI providers, Chats, restarts, and computers, Project and Chat text, project continuity data, and token usage counters are stored on the License Server. When Pisces AI Manager managed models are used, request content is relayed through our server to the selected model provider and is also subject to that provider’s privacy terms.

Data we store

• Email address, name, and password hash.
• Stripe customer, subscription, and invoice identifiers and payment status; Stripe handles complete card details.
• License-key hash and encrypted value, expiry, device fingerprint hash, device name, software version, and last validation time.
• Agreement version and content hash, acceptance time, IP address, user agent, administrator actions, resets, and security access records.
• Input, output, cached, and total token counts and call timestamps grouped by Project, Manager/Executor, Connection, and Model; prompts and response content are not stored in the token-usage table.
• Credit balance, idempotent ledger entries, usage invoices, request status, and encrypted managed-model responses retained for network retry. Administrator provider API keys are encrypted with the server application key and used only to proxy requests.

Safety incidents and human review

When a request clearly concerns scams, malware, credential theft, unauthorized attacks, destruction of data, or attacks on Pisces AI Manager databases or confidential information, the software may block it and submit an encrypted report containing the account, time, incident category, short reason, and the minimum relevant excerpt needed to assess it. The system does not ban an account solely on an AI decision. Only authorized administrators may review relevant material to the extent necessary to handle the incident; access is logged, and the administrator may dismiss, warn, suspend, or ban. Normal token-usage reports do not store prompts or responses.

Server project continuity

Pisces AI Manager sends Project metadata, project continuity data, and the necessary text and structure of Chats to the License Server over HTTPS, where they are encrypted using the server application key. Records are isolated by signed-in user account and Project ID. This is not end-to-end encryption; authorized server operations personnel can technically decrypt the data when necessary. Continuity sync does not upload attachments, media, PPT, PDF, DOC, project source, API keys, attachment paths, local Project paths, Base64, or other binary content and rejects sync requests containing them. Only when a customer explicitly sends a file to a managed model is its extracted text preview or supported image content temporarily relayed through the server to that provider for the request; it is not written to a server attachment table.

Deletion and retention

When a Chat or Project is permanently deleted, the desktop app requests deletion of the corresponding server records; a failed network request is queued for retry on the next connection, and support can also assist when needed. Deleting a Project deletes its continuity data, Chat records, and token usage records; deleting the account cascades to all project-continuity records. Records required for law, tax, payment disputes, and security are retained for the applicable period.