Transport and sign-in
The website and API use HTTPS. Each device sign-in can be revoked on its own, so you can sign out any device from device management.
Where your data goes
Which model you use and where the work runs changes where your data travels, so each case is listed below. To be clear: Dibaci encrypts traffic with HTTPS, which isn't end-to-end encryption, and it doesn't hold any third-party security certification yet.
| How you use it | Who calls the model | Keys and sign-in | Sync across devices | Skills |
|---|---|---|---|---|
| Dibaci built-in models | Dibaci's servers | Managed on the server, never sent to your devices | Yes | Available |
| Your own API | The device you set it up on, directly to the provider | Stays on that device | Conversations sync, keys do not | Not available |
| Codex | Codex on your computer | Stays in Codex's sign-in storage on that computer | Progress, replies and files sync through Dibaci | Not available |
| Cloud development | An isolated cloud environment Dibaci assigns to this conversation only | You don't need to pick a specific cloud machine | Yes | Depends on the model |
Attachments and messages
Attachment files are normally kept on the server for 7 days. After that the file contents are deleted, and the conversation keeps only the name, type, size and an "expired" note. Messages are kept so your devices stay in sync.
Deleting your account
Once you submit, the account is disabled and every device is signed out. Cloud data is normally deleted within 30 days, and backups are cleared within 90 days.
Risky actions
Cloud development is kept separate from your own computer. Deleted files go to the Dibaci trash first so they can be restored, and things like permissions or account deletion always ask you to confirm.
Report a problem
If an AI reply looks wrong, tap Report next to it. To delete your account, use the public deletion page. For anything else about using Dibaci, privacy or security, email Sirintrasaelim82@gmail.com.