Privacy & data handling
OORTYEET VERIFY is pilot-stage software. This page describes the actual software processing, not a certification or a signed contract. A responsible legal entity and verified business privacy contact must be published before public commercial launch.
Information collected
When you submit a pilot inquiry, we request your name, business email, organization, selected workflow, and description. We record consent time and encrypted inquiry content. Form abuse protection may process network metadata such as IP address and browser challenge token through Cloudflare Turnstile when enabled.
Purpose & consent
We use inquiry information to verify that you control the email mailbox, answer business inquiries, evaluate pilots, and prevent abuse. Our email-confirmation system is not a guarantee that a person represents the named organization.
Security
Inquiry payloads are encrypted at the application layer. Production uses a configured managed database and separate managed signing credentials. Encryption protects stored bytes but does not eliminate all risk. Never submit passwords, payment card numbers, patients' records, private customer datasets or trade secrets through the public contact form.
Other processors
Depending on configuration: managed hosting and PostgreSQL provider, email-delivery service Resend, identity provider, managed signing-key provider AWS KMS, and Cloudflare Turnstile. Third-party providers process information under their own terms. No service or geographic data residency is claimed until documented in a signed agreement.
Retention & deletion
We intend to delete unconfirmed pilot inquiries within 30 days and ordinary confirmed inquiries within 12 months unless needed for an active contract or legal obligation. These are target schedules, not yet implemented automated deletion guarantees. Data deletion requests require an independently confirmed operator contact channel.
Verification evidence
Experimental invoice evidence can include customer names, amounts, references and external system identifiers. Sandbox information should not contain real sensitive customer data. Real production pilots require a data-processing agreement, retention controls, incident notification terms, and an independent security review.
Contact
Use the pilot inquiry form. Before public launch, a verified business contact email, controller identity, and applicable legal notices must be published here.