Sign-in you can reason about
Google Sign-In is validated server-side: signature, issuer, audience, expiry, and verified email. Qozee never receives your Google password and does not request offline access.
Qozee handles identity, money, and conversations. We keep the data we need, protect it, and delete it when it is no longer needed.
Google Sign-In is validated server-side: signature, issuer, audience, expiry, and verified email. Qozee never receives your Google password and does not request offline access.
API sessions are opaque bearer tokens. Only a SHA-256 hash is stored, so a database leak does not expose usable tokens. Sessions expire after 30 days.
KYC is handled by Didit. Qozee stores the verification status, decision metadata, and a keyed hash of the NIK for duplicate checks — not the raw ID or selfie.
Payment and payout details are used to issue invoices and record transfers. Card and bank processing is handled by regulated payment providers where enabled.
Production access is limited to the people who need it, protected by strong authentication and reviewed when the team changes.
The website and API are served over TLS. Media is served from storage with access controls and signed URLs where appropriate.
Indicative retention periods. Legal obligations, active disputes, and fraud prevention can extend a period.
| Data | Typical retention |
|---|---|
| Account profile | Until you delete your account, plus a short recovery window |
| Session tokens | 30 days from issue, or until revoked |
| KYC decision | As required for verification and legal compliance; raw ID images are not stored by Qozee |
| Billing and tax records | As required by Indonesian accounting and tax law |
| Chat messages | While the rental is active, then until account deletion unless needed for a dispute |
| 3D captures and room assets | While the property is listed, then deleted or de-identified |
| Server logs | A short operational window, then rotated |
If you believe you have found a vulnerability, email security@qoz.ee with enough detail to reproduce it. Please do not access, change, or share other people’s data, and give us a reasonable window to fix the issue before public disclosure.
Responsible disclosure: we welcome good-faith research, will acknowledge reports, and will not pursue action against researchers who follow this policy.
For privacy questions, see the Privacy Policy and data deletion pages. For Google data specifically, read how Qozee uses Google user data.
Join early access and tell us what you manage. We will help you set up your first property.