Data-use policy
What we do with your prompts, your code and your app's data: no training, provider settings, and how long we keep things.
4 min de leituraThis is our data-use policy in plain words: what happens to the prompts you write, the code AyoWizzy produces, and the data your apps hold. It applies on every plan. Where this page and the Privacy Policy differ, the Privacy Policy governs.
The short version
- We don't train AI models on your prompts, your code or your data.
- The AI providers we use are configured for no training and zero data retention where they offer it.
- We store what the product needs to work, for as long as it needs it, and we say how long below.
- Your data is yours: export it or delete it whenever you like.
No training on your content
Your prompts, the code in your projects, your apps' database contents and anything your users enter are never used to train or fine-tune AI models, ours or anyone else's. The one exception is explicit and off by default: if you turn on the training-data contribution in Settings › Privacy & data, the builds you make after that point may be used to improve AyoSpeed IDE's own models, and you can turn it off again at any time.
Separately, the platform learns from anonymous operational patterns, such as which playbooks produce clean builds and how often a build needs a fix. Those patterns contain no prompts, no code and nothing that identifies you or your project. The Privacy page explains exactly what is kept.
The AI providers we use
To build your app, AyoWizzy sends your prompt and the relevant parts of your project to third-party AI models. We use these providers under their API terms, which do not allow them to train on what we send. Where a provider offers zero data retention, our account is set to it, so a request is processed and not stored. Where a provider keeps a short abuse-monitoring window instead, that window is the limit of what it holds.
- Model routing and hosted models: OpenRouter and the model vendors behind it.
- Web research, when you ask for it: the search provider receives the search query, never your code.
- Request tracing: we keep traces to diagnose failed builds. They are internal, access-controlled and expire.
What we store, and for how long
- Your projects (code, versions, chat and build history): for as long as the project exists. Deleting a project removes them.
- Your apps' databases and uploaded files: for as long as the app exists. Deleting the app empties and deletes them.
- Logs from published apps: 7 days, and at most the newest 1,000 entries per app.
- The workspace activity log: 7 days on most plans, 90 days on Business and Scale.
- Secrets and API keys you add: encrypted at rest. Only your running app receives them; they are never shown back in full and never sent to a model.
- Billing records: as long as the law requires.
- After you ask for your account to be deleted: your content is removed within 30 days.
Who can see your data
The members of your workspace, according to their role. AyoSpeed IDE staff do not open your projects except to fix a problem you have asked us to look at, or where the law requires it, and that access is logged.
Your controls
- Export a project's code at any time from the project menu.
- Delete a project, or your whole account, from Settings › Privacy & data.
- Add, rotate and remove secrets from Connect a service; the activity log records the name of each change, never its value.
- On Business and Scale, review 90 days of workspace activity and download it as CSV.
- Decide whether your builds help train AyoSpeed IDE's own models, in Settings › Privacy & data.
Questions, or a data request? Reach us from the contact page. This article summarizes how we work; the Privacy Policy and Terms are the binding documents.