1. Who operates Cariew
Cariew is operated by Tech SaaS Cloud Innovations from Bhubaneswar, Odisha, India. Privacy questions may be sent to ypritwani@gmail.com.
2. Information we process
- Account information such as name, email, phone, verification state and preferences.
- Subscription, order, payment-status and invoice metadata. Payment credentials are handled by the payment provider, not stored by Cariew.
- Device enrollment keys, installation identity, presence, platform and version.
- Managed workspace metadata and encrypted record envelopes when Managed is enabled. Client-submitted receipt assertions are distinguished from independently verified employer evidence.
- Support correspondence, security reports and audit events.
- Optional analytics and session recording are paused in this website build. No Google Analytics, Microsoft Clarity or Cloudflare analytics beacon is loaded, including after previously accepted consent. Hosting providers may retain operational access/security logs independently of website analytics.
- Fraud-prevention signals such as network and velocity indicators.
3. Data that stays local by default
Connector secrets, browser sessions, CV files, interview audio, screenshots, transcripts, detailed execution evidence and local AI prompts remain on the execution computer unless a feature clearly asks you to transmit specific data.
4. Evaluation-abuse prevention
Evaluation activation requires verified email, verified phone and signed installation ownership. Signup alone does not establish those prerequisites or issue credits. Current account identity markers use normalized SHA-256 hashes, not a claimed secret-key HMAC; hashes alone do not prevent guessing predictable email or phone values. Credit consumption and idempotency evidence are retained to prevent resets. Phone delivery, signed device verification and updated pairing are required integration gates.
5. Why we use information
We use data to provide accounts, verify identity, deliver sync, manage devices, process subscriptions, prevent abuse, support users, secure the service, meet legal obligations and improve product reliability.
6. Service providers
Hosting, communications and payment providers handle data needed for those services. Optional third-party analytics is disabled pending verified private-route isolation, masking and consent withdrawal. A future analytics change requires updated disclosure and consent; a stored preference does not enable collection in this build.
7. Retention and deletion
The corrected account-erasure flow deletes tenant product data, receipts, credit-consumption records and trial claims. An audit retains request/account/workspace UUIDs and outcome metadata; billing replay records retain event IDs and body digests. These are pseudonymous records, not a claim of full anonymity. Backup expiry, external-provider erasure and any future anti-abuse retention period require approved policy. Because trial claims are currently erased with the account, permanent repeat-trial prevention after deletion is not claimed.
8. Security
Selected local private payloads are encrypted, not the entire SQLite database. Interview company, role and link; workspace titles and references; and activity summaries may remain readable local metadata. Managed record envelopes and account/billing metadata have different protection boundaries. Signed device challenges require end-to-end verification before they are described as completed. Protect the device, accounts and connected-provider credentials.
9. Your choices and rights
You may request access, correction, export or deletion as applicable, disable managed sync, revoke devices, cancel renewal and appeal a trial decision. Contact us using the address above.
10. Children and changes
Cariew is intended for people aged 18 or older. Material policy changes will be dated and communicated through the product or verified contact channel before taking effect where required.