Privacy & data handling
Your data stays in your environment. Here is what that means in detail.
The short version: systems run on your infrastructure under your accounts, there is no OPSPHI platform in the middle, and nothing of yours is held after transfer except what you ask us to hold.
01Where systems run
- Client-hosted by defaultSystems are deployed in your environment, on your infrastructure, under accounts in your name. We do not operate a multi-tenant platform, and your data is not pooled with anyone else's.
- What leaves your networkNothing by design. Where a third-party model or API is part of a system, it is called from your account under your contract with that provider, and the boundary — which fields go, which do not — is written down and agreed before we build.
- What we see during a buildOnly what the work requires, and only for as long as it requires it. Where a sample of real data is needed to encode a rule, we say so, we say what we need, and we use the smallest sample that answers the question.
- Logs and replayEvery input, decision and output is logged and replayable, in your environment, so any past number can be reconstructed exactly. The log belongs to you along with everything else.
02Access, retention and sub-processors
- Access is by named individualThe people who will touch your systems are named and disclosed before the engagement starts. Access is removed at handover — or, if we operate the system for you, when we stop — and the removal is something you can verify in your own account logs rather than take on trust.
- RetentionWe hold nothing of yours after transfer other than what you ask us to hold for maintenance, and what we hold is written into the engagement.
- Sub-processorsListed with what each one sees, and no sub-processor is added to a running system without telling you first.
- Model providersWhere a system calls a model, it is your account and your provider terms. We do not send your data through ours, and we do not use your data to train anything.
03Data handling on the diagnostic
The audit and the diagnostic are the first place your data is touched, so they have their own rules.
A paid, bounded first step is still an engagement, and it runs against your real data rather than a questionnaire. That is the point of it, and it is also the reason these rules exist before the build does.
- What we ask forThe narrowest extract that answers the question — a list, a period of files, a sample of documents. Not a systems-wide export, and not credentials to your production environment.
- Where it is processedIn your environment where that is possible. Where an extract has to come to us, it is agreed in writing first, held for the duration of the diagnostic, and deleted on delivery of the teardown.
- What is in the deliverableThe written teardown cites your own data back to you. It is yours, it is not reused, and it does not become an example in anyone else's proposal.
04This site
- What this site collectsWhat you type into the contact form, so that we can reply to it, and the usage data described below. The form is relayed to hello@opsphi.com by Web3Forms, which handles the message in transit. Nothing you send is added to a list or a sequence.
- Analytics and trackingWe use Google Analytics to count visits and see which pages are read, and Microsoft Clarity to see how pages are used — scrolling, clicks, heatmaps and session recordings. What you type into the contact form is masked and never recorded. Both set cookies and receive your IP address, and the site's host, Lovable, counts visits too. There are no advertising pixels and no cross-site tracking. Typefaces are served from this domain, so no font request leaves it.
- Asking us about your dataWrite to hello@opsphi.com and a principal will answer, not a ticket queue.
- Job applicationsIf you apply for a role, we use what you send, your name, contact details, résumé and answers, only to consider your application. Applications come by email to careers@opsphi.com. We keep them for 12 months and then delete them, unless you ask us to delete yours sooner or to keep you on file for future roles. They are never shared with a recruiter or added to a list. Write to careers@opsphi.com to see, correct or delete what we hold.
- Grievance officerAnkush Goyal, Founder, OPSPHI: hello@opsphi.com. We resolve complaints within one month of receiving them.
- Changes to this pageMaterial changes to how client data is handled are a contract matter and are agreed with you, not published here and deemed accepted.