Data minimization
Only the census, payroll and plan fields a workflow needs. Full Social Security numbers are not required for any website tool and should never be sent to us.
DATA PROTECTION
Participant data protection, stated plainly.
What KinetiPlan does with census, payroll and ledger data, where it lives, who can see it, and which protections are in the pilot build versus still planned.
PRINCIPLES
Collect less. Keep it in the US. Prove who touched it.
US residency
Production participant data is hosted in the US: in your AWS account in a US region, or on your servers. Development uses synthetic data only.
No standing access
Software Home engineers have no routine access to production. Support sessions are approved by you, time-limited and logged.
Customer-held keys
In customer-hosted deployments encryption keys stay in your key management service.
Retention you set
Retention and secure deletion follow your records policy; exports are available in CSV.
Human approval
Nothing is filed, posted or sent externally without a named person approving it.
DATA LIFECYCLE
Where data goes, step by step
| Stage | What happens | Status |
|---|---|---|
| Intake | Census and payroll files uploaded by staff over HTTPS and validated before anything posts. | Working in pilot build |
| Storage | Database and files inside the customer environment; encryption at rest with customer-managed keys. | To be verified |
| Processing | Deterministic rules calculate eligibility, limits and tests; exceptions go to an owned queue. | Working in pilot build |
| Access | Role-based permissions and SSO with MFA through your identity provider. | Planned |
| Logging | Exception decisions recorded with notes; full change audit log planned. | Partly in pilot |
| Export and deletion | CSV exports exist; documented secure deletion procedure per deployment. | Deletion procedure planned |
Status key: Working in pilot buildOn this websiteScoped per customerPlannedEvaluating
"Working in pilot build" means the function runs in the KinetiPlan pilot build on synthetic demo data. It does not mean generally available, certified or production-proven. "To be verified" means the engineering team has not yet confirmed it with evidence.
THIS WEBSITE
What the website collects
The website holds no participant data. The demo request form collects only what you type (name, business email, company and your answers) to reply to you. The interactive demo and calculators run in your browser and send nothing. Analytics respect Global Privacy Control. Details are in the privacy notice.
GUIDANCE
Aligned with what regulators ask
The U.S. Department of Labor’s cybersecurity guidance for plan sponsors and service providers is the checklist we design against. Alignment is a design goal, not an audit result; KinetiPlan holds no SOC 2 report today. See the enterprise readiness roadmap.
NEXT STEP
Evaluate KinetiPlan on your terms.
Choose the conversation that fits where you are. Calls run on Google Meet. Nothing on this website asks for participant data.
Schedule a product demo →A live walkthrough of the pilot build on Google Meet, on the workflow you choose.Request a technical consultation →Architecture, data model, API and testing logic with an engineer.Request a migration assessment →Bring de-identified exports; we map them and list the gaps.Request a deployment discussion →Customer-hosted AWS or on-premises: responsibilities and evidence.Download the product overview →A 4-page PDF for partners and IT reviewers.