How AI requests are processed
You choose whether to use Zipy AI Credits or your own model API key.
Zipy AI Credits
When you use Zipy AI Credits, your prompt, conversation context, and any text you choose to include from files are sent to Zipy Codes' server for processing by the managed Zipy AI service. Zipy AI selects how each request is handled based on the task. If an AI service explicitly reports it cannot solve a request, Zipy AI may make one alternative attempt; a network failure or safety refusal does not trigger an alternative. We measure usage across completed attempts and store your credit balance and usage records. Attached images are not sent for image understanding.
Optional request classification is separate from code generation. If you choose “Classify request” and confirm, only the draft text displayed for your approval is sent through our server to an external AI classification service. Chat history, project files, and attachments are not included. The resulting category is a suggestion; it is not automatically added to your draft or used to start a build. Classification does not deduct Zipy AI Credits.
By default, chats and project files remain on your device unless you choose to export, connect GitHub, or include their contents in an AI request. Only include information you are comfortable submitting for AI processing.
Optional cloud chat sync
When you turn on cloud chat sync, Zipy Codes stores your chat text, AI responses, extracted document text included in prompts, and chat titles in your account so you can search and recover them on another device. It does not sync generated project files, image attachments, or your model API keys. Chats remain in the cloud until you delete individual chats while sync is on or use “Delete all cloud chats.” Turning sync off stops new uploads but does not delete previously synced chats. Other devices must turn sync on to retrieve them.
Cloud chat content is stored in your account's database and can be accessed by the app's server. Avoid including secrets in prompts or attachments. If a chat is too large or the connection fails, it stays on your device and the app shows a sync error.
Your own API keys
If you choose a bring-your-own-key model, the key remains in this browser and the browser sends requests directly to the model service you selected. That service may apply its own data policies and charges.
Affiliate referrals and payouts
When you visit a Zipy Codes affiliate link, we set a first-party referral cookie for up to 90 days. It contains a random token, not your name or payment information. We store a hash of the token and use it to credit an affiliate if you subscribe to Pro within that period. We keep referral, invoice, and commission records to manage payouts, refunds, and disputes. Affiliates see aggregate results, not your identity or payment details.
If you join as an affiliate, Stripe Express handles bank account onboarding and bank details. Zipy Codes stores your Stripe connected-account identifier and payout status; your bank details are not stored here.