SeuSive provides patient-intake and companion software to clinics. This page separates the data handled by this website from data a configured clinic deployment may process. Exact privacy roles, safeguards, and data flows are set for each deployment and documented before production patient data is used.
Our role
For website enquiries and account administration, SeuSive determines the purposes of the information it collects. For patient information, the legal roles are deployment- and jurisdiction-specific. A clinic will often act as controller or covered entity and SeuSive as processor, service provider, or business associate, but that model is not universal. The applicable law and executed agreement must name the parties' roles, instructions, and permitted uses before production processing begins.
Data a deployment may process
- Patient intake and companion data: depending on the clinic's configured workflow, this may include symptoms, history, medications, allergies, check-in answers, care-team messages, consent choices, uploaded files, language, and structured review data.
- Optional health and fitness integrations: a companion build may support Apple Health or Health Connect only when that integration is enabled for the deployment and the user grants permission. Device settings control revocation.
- Account & enquiry data: name, work email, organization, and the content of demo or pilot requests.
- Technical data: operational, security, and audit records defined by the selected architecture and documented logging policy.
How we use it
Permitted uses for patient data are limited by the clinic's instructions and the executed agreement. Intended uses include preparing a clinician-ready review, operating the configured service, helping a patient share relevant context with the care team, and meeting documented security and support obligations. SeuSive's deployment policy is not to sell personal data or use patient data for advertising or external-model training. For production, those restrictions and any permitted AI processing must be written into the binding agreement and verified against the selected vendors' terms.
Apple Health & Health Connect
Health and fitness permissions are optional and user-initiated when enabled in an approved companion build. The deployment agreement and platform configuration must prohibit advertising and data-broker use of this data, name any permitted processors, and explain how information a user chooses to share can be associated with the clinic record for care-team review.
Residency & hosting
SeuSive does not claim one universal production host or region. Each deployment must identify the cloud provider and services, storage region, backup location, support-access path, and any cross-border channel or AI processing. Country packs express intended market rules; they do not by themselves prove runtime residency. The selected architecture and regional controls must be configured, tested, and recorded before production patient data is enabled.
Retention
There is no single global retention period. Patient-data retention, deletion, export, and backup handling must be defined by applicable law, the clinic's policy, the binding agreement, and the verified deployment configuration. Website and enquiry data should follow a documented schedule tied to the purpose for which it was collected.
Sharing & sub-processors
Potential infrastructure, channel, support, analytics, and AI vendors depend on the deployment. Internal templates and a vendor register are not proof that a contract is signed or that a vendor is approved for every data type or market. Before production use, the clinic must receive the exact vendor list, purpose, data scope, location, transfer path, and contractual coverage for the proposed setup. Vendors that do not satisfy the deployment's requirements must remain disabled for patient data.
The PHI gate
Production patient data may be enabled only after privacy roles and agreements, tenant boundaries, hosting and residency, retention, access controls, channels, and vendors are configured and verified with the clinic. Current public demos and prospect previews use synthetic, non-production records; that demo evidence does not establish production readiness.
Your rights
Available rights and the responsible party depend on the jurisdiction and agreed privacy roles. Where a clinic is the controller of patient data, requests are normally routed through that clinic and SeuSive assists as required by the executed agreement. Other legal models may use a different process. For website or account data held directly by SeuSive, contact us so the request can be assessed under the applicable law.
Changes & contact
We'll post any material changes here and update the date above. Questions about privacy? Email [email protected]. Read more about our safeguards on the Security page.