Privacy
Oqult ("we") operates oqult.com from the United States. There are two ways you can send us anything. If you email us, we receive your address and whatever you wrote. If you use the form on the contact page, we store your name, email address, organization if you give one, your message, and the page you sent it from, in a Google Firestore database in the United States. In both cases we keep it while the conversation is live and for as long afterwards as our records require, we use it only to answer you, and we do not sell it, share it, or add you to a list.
The form writes directly to that database from your browser. Nobody can read the enquiries through the website — the rules that govern the database allow a submission to be created and nothing else. The same submission is also passed to FormSubmit, a form-relay service, purely so that it reaches our inbox; it holds your message only long enough to deliver it. If either step fails the other still works, so an enquiry is not lost.
The site runs no analytics and sets no tracking cookies. Our host (Firebase Hosting) writes standard server logs — IP address, user agent, the page requested — which we use only to keep the site up. Nothing on this site profiles you, and the form is the only thing that stores anything you type.
Whatever data protection law applies where you live — a US state privacy law such as the CCPA, or the EU or UK GDPR — you can ask us what we hold, ask for it corrected, or ask us to delete it, by asking through the contact form — say what you are asking for and we will act on it. We will not charge you or treat you differently for asking. Anything you send us is processed in the United States.
Cookies
This site sets no cookies of its own and writes nothing to local storage. Fonts are served from our own domain rather than a third party, so no outside service sees your visit. Submitting the contact form sends what you typed to Google Firestore, where we store enquiries, and to FormSubmit, which delivers it to our inbox. Neither sets a cookie in your browser. Our host may set a strictly necessary cookie for security; nothing on the site can be personalized, so there is nothing to consent to and no banner to dismiss.
Terms
The content here is published for information. It is not advice on which to base a technical, financial or security decision — that is what an engagement is for, and an engagement comes with its own contract. We write carefully and correct errors when we find them, but we make no warranty that everything is current or complete.
Text, code and artwork on this site are ours. Quote us with attribution; do not republish wholesale. These terms are governed by the laws of the United States, without regard to conflict-of-law provisions.
Accessibility
We aim at WCAG 2.2 Level AA, and test against it. Every interactive
element has a visible focus ring that is never suppressed; all motion is
behind prefers-reduced-motion; content is never hidden from
readers without JavaScript; text resizes to 200% without loss; the site is
navigable by keyboard throughout. Decorative elements — the wave field,
the textures, the brand mark — are hidden from assistive technology, and
the brand lockup carries a text alternative.
If something here does not work for you, tell us through the contact form and we will fix it — we aim to reply within five business days. If we do not put it right, you can complain to the Civil Rights Division of the U.S. Department of Justice, which enforces the Americans with Disabilities Act.
Contact
Anything on this page, or a security disclosure: the contact form, which is also the channel named in security.txt.