Controller and contact
Orbivell is operated by Rodix Co., Ltd., represented by Hwang Hwan-cheol. Privacy questions and rights requests can be sent to cs@rodix.ai or +82-70-4895-2890.
DATA BOUNDARY
Orbivell Privacy Policy
Orbivell separates local indexing from optional external processing and keeps the transfer decision visible.
Effective date: August 31, 2026
Data we collect
We process account email and password hash, approved-device, session and consent records, bounded usage and error metadata, support inquiries, and order, payment-state, and provider identifiers as needed. We do not store card number, CVC, payment password, original PC documents, or full local paths on the server.
How we use data
We use data for sign-in and device authorization, service and quota delivery, payment and pass administration, security and reliability, customer support, and legal obligations. Optional measurement runs only after consent.
Sharing and processors
We provide only the minimum necessary data to service providers for payment processing, email delivery, hosting, and user-approved AI processing. We do not sell personal data or provide it for third-party advertising except when legally required or separately authorized.
Retention and deletion
We retain data only as long as needed for service delivery and legal duties, then securely delete it after the purpose is met, the account is deleted, or the retention period expires. Legally required records are isolated for the required period. The account-deletion page directly explains the method and scope.
Security
We apply encryption in transit, password hashing, access controls, device authorization, bounded operational logs, and regular cleanup. Local PC source content and indexes remain separated from Web account metadata.
Stays on the PC
- Registered folder paths and source files
- The local index, document chunks, questions, answers, and saved knowledge cards
- Original file names and full local paths
Sent only after approval
- The question and selected Evidence excerpts for grounded answers
- Selected changed excerpts for an AI-enhanced folder briefing
- Bounded text batches for embeddings when that consent is enabled
Metadata the service may retain
- Account, approved device, consent, quota, request outcome, token, cost, latency, and byte-count metadata
- A non-sensitive diagnostic ID, component, and timestamp for support
- No document text, question, answer, Evidence content, file name, or local path in the usage ledger
DATA BOUNDARY
Controls you keep
You can cancel a transfer preview, withdraw AI consent, revoke an approved device, sign out, and continue using local keyword search.
Purpose and retention of Web metadata
- Account, password hash, session, and device authorization metadata provide sign-in and access control. Expired sessions and one-time tokens are removed by bounded cleanup.
- AI usage stores request ID, feature, unit counts, status, and latency for quota, cost, and reliability. It does not store request or response content.
- Optional Web measurement starts only after explicit consent and stores page category, language, edition, channel, bounded campaign codes, version, time, and a server-hashed pseudonym. It excludes document names, paths, questions, answers, inquiry text, email, and payment instruments. Declining does not limit features.
- Purchases store order and payment state, amount, pass period, and provider identifiers, but never card number, CVC, or payment password. Contact submissions store contact details and inquiry text in the database first, then track delivery to cs@rodix.ai separately.
- Support text and a user-reviewed diagnostic reference are used to handle cases. Operators cannot browse local source content.
- You can export account metadata as JSON and delete the Web account. Account deletion and PC local-data deletion are separate actions.
Access, correction, and deletion
Use account settings or the account-deletion guide below. Privacy requests can also be sent to cs@rodix.ai.