Privacy policy
How OORTYEET VERIFY handles information submitted through its website and customer services.
Effective date: November 12, 2026.
Information we collect
We collect information you provide when contacting us or using an account, including your name, email address, organization, inquiry, support messages, and submitted case details. We may also receive account-related purchase information from our payment processor.
How we use information
We use information to respond to inquiries, deliver contracted services, operate client accounts, handle requests, provide support, prevent abuse, and maintain business records.
Service providers
We use infrastructure and payment providers to operate services, including Cloudflare for web infrastructure and Stripe for online checkout when enabled. Authentication emails may be sent using a transactional email provider. Such providers process data in accordance with their own agreements.
Payments
Card information entered through Stripe Checkout is handled by Stripe; our website does not need to collect full payment card details.
AI chat
Questions submitted to the assistant are processed to generate a response. Avoid entering passwords, financial account details, or confidential source records into chat.
Storage and retention
We retain business records as needed to provide services, meet legal obligations, handle disputes, and maintain security. You may request access or deletion where applicable, subject to lawful retention requirements.
Cookies
Account sessions use essential cookies for sign-in and security. We do not require third-party advertising cookies for core website functions.
Contact
Use the contact form for privacy questions and requests.
Project observations
When you request a DNS check, we send the domain and requested record type to a public DNS resolver. We retain the expected value, observed DNS record values, timestamp, result, and a service-signed receipt in your account. A shared receipt may reveal its domain and expected record values. Avoid entering credentials, personal records, or private access tokens into the DNS checker.
Account creation and security
New accounts may use a username, email and password. We store a password-derived verifier and salt, not the plain-text password. Confirmation and recovery codes are short-lived and used for account access. Authentication sessions use an HTTP-only secure cookie; selecting “remember me” affects the permitted duration. We retain policy-acceptance versions and dates. Network and anti-abuse data such as IP-derived rate-limit keys may be processed to protect accounts.
OORTSERV device and household information
When activated and authorized, connected robotic services may process registered device identity, declared capabilities, service region, task requests, scheduled availability, battery/charging status, location data, limited telemetry, maintenance records, supporting evidence, customer feedback, invoices and disputes. Location, photos, voice or sensor data can be sensitive. We aim to minimize what is collected, apply account-scoped access, and support revocation where feasible. Access to private homes, occupants, images or sensors must be expressly authorized and disclosed before collection. Current development simulations do not independently collect physical robot data.
OORTBOT gameplay and shared rooms
OORTBOT's local simulator may store gameplay and research data on the user's device. Where a separate online room is enabled, its server processes an authenticated participant identifier, chosen display handle, room and messages to operate shared sessions; do not submit private household information. Optional research uploads require affirmative opt-in, are labeled simulated, and cannot support physical work certification or charges. Local saved data may be lost if browser storage is cleared.
Purposes and disclosures
We use data to operate accounts and purchased services, respond to support requests, prevent abuse, maintain financial records, improve service quality and comply with applicable legal requirements. We disclose necessary data to hosting, email, identity-security, verification and payment providers under applicable agreements. We do not sell user conversation content to advertisers through this website. We do not publish private household location or raw customer evidence in public robot passports by default.
Retention, access, deletion and security
Different record classes may require different retention periods for security, billing, legal obligations and dispute handling. We seek to remove data that is no longer required and enforce appropriate access controls; no Internet service can guarantee perfect confidentiality or security. Use our contact process to request records, correction, deletion or information about applicable privacy rights. We verify identity before disclosing account information.
International use and minors
Service availability, data transfer requirements and privacy rights may differ by jurisdiction. Household robotics and account registration are initially intended for adults age 18 or older. Child-directed services and international commercial launches require additional controls and locally appropriate disclosures before activation.
Changes and contact
We may update this policy to reflect actual processing and legal requirements. Material changes will be communicated as required by law. Please use our contact page for privacy concerns and rights requests. This privacy policy must be reviewed against the actual deployed vendors, retention procedures and business locations before commercial launch.
Account registration uses a username, email address, hashed password, security session records, consent version and time. Monitoring stores user-configured public-domain targets, observations, and alerts. Customer-uploaded DMARC reports may contain mail-origin IP addresses and other sender metadata. Subscription processing is handled by Stripe; we do not ask you to enter payment-card details into our VERIFY pages. Necessary cookies provide account authentication. Optional research sharing requires a separate choice.
To request access, correction, or deletion, open a secure support ticket or contact us through the contact page. Some records may need to be retained for legal, security, billing, or evidence-integrity obligations. See Data requests and retention for the practical process.