Privacy notice · updated 14 November 2026

How Orvessian handles personal information.

This notice covers our website, live platform, TEST environment and support service. Public Free access is live. The public demo uses synthetic examples.

Operator and contact

Fluxora Ltd, company registration number 01010675, incorporated with the RAK Digital Assets Oasis Authority. Correspondence address: Office A, RAK DAO Business Centre, RAK BANK ROC Office, Ground Floor, Al Rifaa, Sheikh Mohammed Bin Zayed Road, Ras Al Khaimah, United Arab Emirates. Privacy and support: contact@orvessian.com.

Our role and the information we receive

We determine how account, website, security and support information is used to run Orvessian. Customers determine which structured records they submit and why. When processing those records on their behalf, we follow their instructions and applicable service and data-processing terms. This notice does not replace those terms. Contact us before submitting data that requires specific contractual or transfer safeguards.

Website and accounts

We receive information you provide when requesting access, signing up or contacting us. WorkOS handles account details, verification, sign-in and multi-factor authentication. We maintain identity links, memberships, permissions, API-key metadata and sessions. Administrators may provide your email address to invite you. Account details are needed to provide authenticated access; without them we cannot create or secure your workspace.

Customer records and evidence

Customers submit selected structured records and identifiers, which can include ordinary personal information. Keep prompts, conversations, documents, media and raw tool inputs and outputs in your own systems. Do not submit sensitive personal information. Use opaque references where possible. Records may describe decisions made by a customer's systems; Orvessian records and evaluates configured rules, rather than making the underlying business decision about an individual.

Support requests

A ticket includes your account email, project reference, category, subject and description, plus any page or diagnostic context you choose to include. We store the ticket and delivery status, email our support inbox and send you an acknowledgement. Replies arrive by email. Do not include passwords, API keys or sensitive customer records in a ticket.

Technical diagnostics

Application diagnostics record fixed error categories, request correlation IDs, operation categories, response codes and timing to investigate faults, failed sign-ins, session loading and delivery problems. Our browser diagnostic reports exclude message text, page query strings, record bodies and credentials. They do not record sessions or capture screenshots. Hosting and security providers also process technical connection information, which can include IP addresses and browser information.

Why we use information

We use account and workspace information to deliver the requested service, administer access and answer support requests. Where relevant law requires a legal basis, we rely on performance of our contract with an individual customer for those purposes, and legitimate interests in administering business-customer accounts and responding to enquiries for other contacts. We rely on legitimate interests in preventing misuse, protecting accounts and maintaining a reliable service for security and diagnostic processing, and on legal obligations when we must retain or disclose information by law. Customer-submitted records are processed to provide the requested record and evidence functions under the customer's instructions. An access or support request is not consent to marketing emails.

Providers and international processing

We use WorkOS for identity and account email; Sites and Cloudflare for the website; Contabo for the portal and API host; DigitalOcean for the managed database and its backups; Backblaze B2 for encrypted backups and retained checkpoint evidence; Purelymail for support and privacy email; and GoDaddy for domain registration and DNS. Independent timestamp services receive a cryptographic checkpoint digest, not the submitted record body. Current timestamping uses CNX. GitHub hosts our public developer documentation and SDK source; visiting it is subject to GitHub's privacy notice.

We operate from the United Arab Emirates and providers may process information in other countries. Arrangements and available safeguards depend on the provider and service. Contact us for details and copies of applicable safeguards before a transfer-sensitive deployment. We do not represent that every provider arrangement has been independently certified or every transfer is covered by an adequacy decision.

Retention and deletion

Free record detail: live receipt-body detail expires after 30 days. The Free allowance is 1,000 unique accepted receipts per UTC calendar month. Expiry of detail does not erase every related record.

Evidence: tombstones, cryptographic commitments, signed checkpoints and verification material can remain after detail expires to preserve the integrity of recorded history. Current evidence uses the database, signed checkpoints and external retention; new records do not require a public blockchain transaction. Historical Base commitments and transaction metadata are public and cannot be deleted by Orvessian.

Backups: encrypted backups may contain earlier detail after live expiry. Backblaze compliance locks impose a minimum hold, not a maximum lifetime. Our Production backup bucket currently has no automatic lifecycle deletion rule, so we cannot promise a maximum deletion period. Managed-database backups are separate. Deleting an identity account does not by itself erase historical records or backups.

Accounts, support and audit records: we retain these while needed to provide access, resolve requests, investigate incidents, establish or defend claims, or meet applicable obligations. We assess deletion requests against those purposes and explain retained categories. The 30-day record-detail period does not apply to these records or independently retained evidence. Technical logs are limited through operating retention and storage controls; provider-held logs follow the provider's arrangements.

Cookies and similar technology

Sign-in uses cookies needed for authentication and security. The current website source has no optional marketing analytics or advertising cookies. First-party fault reporting supports service reliability and does not set a tracking identifier. WorkOS and hosting infrastructure may use technical cookies for access and delivery. If we introduce non-essential tracking, we will provide a separate choice where required.

Your choices and rights

Depending on applicable law, you may request access, correction, deletion, restriction or portability of your information. You may also object to processing based on our legitimate interests. If processing relies on consent, you may withdraw it without affecting earlier lawful processing. Contact contact@orvessian.com. We verify identity and scope before acting, explain limits and coordinate with the relevant customer when a request concerns their submitted records. There is no self-service account deletion button.

You can complain to the relevant data-protection authority. In the UK, contact the Information Commissioner's Office; elsewhere, your local authority may be appropriate. We update this notice when our practices change and identify the update date above.