Privacy

Scope of this notice

This notice covers oracus.ai — the public marketing site you're reading right now. It does not cover the Oracus.ai product itself: Oracus.ai is self-hosted, so when you install it on your own infrastructure, your code, infra, tickets, tests, and chat history stay on your servers and never reach us. The product runs inside your network; this site runs on ours.

What we collect

Two forms on this site send data to us. That's it.

• Sales-contact signup. The "Contact me" forms on the homepage collect just your email address and which form you submitted it from (so we can tell what's converting). We use it to reach out about pricing, demos, and your specific stack. Stored in a Postgres table; one row per unique email.
• Contact form. The form on /contact collects whatever you choose to type in: name, work email, optionally a company name, an interest tag (e.g. "Team plan"), and your message.
• Standard request logs. Our host (Vercel) keeps short-term access logs of HTTP requests — IP address, user agent, URL, status code — the same logs any web host keeps. We use these for debugging and abuse prevention, not for tracking individuals.
• Abuse-prevention counters. When you submit a form, we hash your IP address (truncated SHA-256) and use it as a short-lived key in a rate-limit counter. The hash expires within the hour. We don't store your raw IP alongside your submission.

What we don't collect

• No analytics, advertising pixels, or third-party tracking scripts.
• No cookies set by this site for tracking purposes.
• No fingerprinting, no session replay, no behavioural profiling.

If we add a site analytics tool later (e.g. for measuring page views), we'll list it here before turning it on.

Where the data lives, and who can see it

We use a small set of infrastructure providers, all configured as sub-processors to oracus.ai:

• Vercel — hosts the site and runs the small serverless functions that receive form submissions.
• Neon (managed Postgres, provisioned through Vercel) — stores waitlist emails and contact submissions.
• Upstash (managed Redis, provisioned through Vercel) — stores the short-lived rate-limit counters keyed on hashed IP.
• Amazon Web Services (SES) — when you submit the contact form, your message is forwarded to our team inbox via Amazon SES. AWS sees the email content in transit; we don't store anything on AWS beyond what SES needs to deliver the message.

Only Oracus.ai operators can query these databases. We don't share them with anyone else, and we don't sell or rent any of this data.

Why we collect it

• Sales-contact emails. So we can follow up about pricing, a demo, or your specific deployment.
• Contact submissions. So we can answer your question.
• Logs and rate-limit counters. So we can keep the site working and block obvious abuse.

How long we keep it

• Sales-contact emails: until you ask us to delete them, or until we stop running the project.
• Contact submissions: until we've finished replying and a reasonable archive period has passed, or until you ask us to delete them.
• Rate-limit counters: automatically expire within an hour.
• Vercel access logs: retained by Vercel under their standard retention; we don't archive them separately.

Your rights

If you're in the EU, the UK, or anywhere with comparable rules, you have the right to ask us what we hold about you, to have it corrected, and to have it deleted. We'll honour those requests regardless of where you are.

To exercise any of these rights, or just to ask a question about this notice, write to hello@oracus.ai and include the email address you used. We aim to respond within one business day.

Changes to this notice

If we materially change what we collect or how we use it, we'll update the "Last updated" date at the top, and — for changes that affect anyone who's already given us an email — we'll mention it when we next reach out.