A few words.
Nerova is an API-first SaaS that lets platforms add an AI receptionist to their product through our API.
For platforms serving human medical and clinic services, salons and barbers, and beauty businesses including nail salons.
The interactive story uses motion and video. Site information is available below.
Contact
For platforms serving human clinics, salons, barbers and beauty businesses, including nail salons.
Updated 2026-09-11
A platform conversation
Nerova is an API-first SaaS that lets platforms add an AI receptionist to their product through our API.
Our first release is for platforms serving human medical and clinic services, salons and barbers, and beauty businesses including nail salons.
Use the contact form to reach us. Never include API keys, secrets, or end-customer records in your message.
The contact form requires JavaScript. Enable it and open Contact & info to send a message. The policies and API-reference link remain available without it.
Privacy policy
How Nerova handles data, and the responsibilities we share with the platforms we work with.
Updated 2026-09-11
Roles and responsibilities
Nerova is an API-first SaaS for platforms. The host platform keeps its customer relationship and its authoritative records. For end-customer data handled during a controlled operation, the host platform acts as the data controller and Nerova acts as a processor on its documented instructions. For account data belonging to platform teams with Nerova accounts, Nerova is the controller.
Data we process
The Testing environment runs against deterministic fixtures. Fixture data is synthetic; no real end-customer records are required to evaluate an integration.
- Platform account data: names, work email addresses, and authentication records for the people who operate a Nerova integration.
- Operational data: conversation context, service and availability lookups, appointment requests, and the explicit outcomes returned to the host platform.
- Diagnostic data: request logs and error records used to keep operations verifiable.
- WhatsApp channel data: when a business connects the WhatsApp Business Platform, we process WhatsApp phone numbers, message content, and delivery metadata to run receptionist conversations. The business owns its WhatsApp Business Account, and this data is exchanged with Meta Platforms under Meta's WhatsApp Business terms. End-customer messaging happens only after the end customer starts a conversation or has opted in through the business, and WhatsApp channel data follows the same use and retention rules described here.
How we use data
We use operational data to execute the capabilities a platform has declared, to return explicit outcomes, and to produce the receipts that verification depends on. We do not sell personal data, use end-customer data for advertising, or train shared models on a platform's operational records.
Retention
Operational records are retained for the period defined in the platform's operational contract, then deleted or de-identified. Account data is retained while an account remains active and removed on verified deletion requests, subject to legal holds.
Subprocessors
We use a small number of infrastructure subprocessors to run the service. A current subprocessor list, including processing locations, is available to platforms on request and is provided during Production review.
Your rights
Platform team members can access, correct, or delete their account data by contacting us. End customers should direct requests to their booking platform first, which holds the authoritative record, and we support the platform in fulfilling them within processor timelines.
Contact
For privacy questions and requests, contact us and select the privacy topic. We respond to verified requests within 30 days.
This policy summarizes our privacy posture in plain language. The executed data processing agreement between Nerova and a host platform governs where the two differ.
Terms of service
The terms that apply when your platform evaluates or uses Nerova.
Updated 2026-09-11
The agreement
These terms form the agreement between Nerova Systems and the platform or person operating a Nerova account. Creating an account or using the service means you accept them. Where a platform has an executed operational contract with us, that contract governs any conflict with these terms.
Testing access
Developer access is provided to approved platforms. Testing access and any Testing credits follow the terms communicated to your platform.
The Testing environment runs against deterministic fixtures so you can evaluate integration behavior before anything real is at stake.
- Fixture data is synthetic and must not be replaced with real end-customer records.
- Testing results demonstrate integration behavior; they do not by themselves grant Production access.
Production terms
Production access is subject to the platform's approved access, agreed commercial terms and active entitlements.
- Nerova executes only the capabilities the platform has declared and we have approved.
- Every controlled operation returns an explicit outcome; the host platform keeps the authoritative record.
- Billing follows the commercial terms agreed for your platform.
Acceptable use
You may not use the service to misrepresent who is acting in a conversation, to schedule or manage services that are unlawful in the relevant jurisdiction, to probe or overload the platform outside documented interfaces, or to resell receptionist capacity without an agreement that covers it.
Intellectual property
Nerova retains ownership of the service, its interfaces, and its documentation. The platform retains ownership of its own product, brand, and records. Feedback you choose to give us may be used to improve the service without obligation.
Liability
The Testing environment is provided as-is for evaluation. For Production, responsibility, service commitments, and remedies are set in the operational contract for that platform; we do not publish blanket guarantees here, because commitments are scoped to each reviewed integration.
Changes
We may update these terms as the service evolves. Material changes are announced to account owners in advance, with the effective date shown here. Continued use after the effective date means acceptance.
Contact us with questions about these terms or to request the full contractual documents for a review.
Security
How we protect the data and operations entrusted to Nerova.
Updated 2026-09-11
Environment boundaries
Testing and Production are separate environments with separate credentials. The Testing environment runs deterministic fixtures and can never reach a platform's real records. Production access is subject to the platform's approved access, agreed commercial terms and active entitlements.
Capability gating
Nerova can only perform operations the host platform has declared and we have approved. There is no general-purpose access: each controlled operation is checked against the platform's declared capabilities before execution and returns an explicit outcome afterward. Undeclared actions fail closed.
Encryption
Data is encrypted in transit using TLS and at rest within our infrastructure. Platform credentials are stored in a dedicated secrets system, scoped per platform, and are never exposed in logs, receipts, or outcomes.
Access control
Internal access to operational data follows least privilege, requires strong authentication, and is logged. Production support access is time-bound and reviewed. Platform-side, every team member acts under their own account; we never ask platforms to share credentials with us.
Incident response
We maintain an incident response process with defined severities and on-call ownership. If an incident affects a platform's data or operations, we notify the affected platform without undue delay and provide the facts needed for its own obligations, followed by a written post-incident summary.
Responsible disclosure
If you believe you have found a vulnerability, contact us with the details and steps to reproduce. We acknowledge reports promptly, keep you informed while we investigate, and do not pursue good-faith research conducted within this policy.
Detailed security documentation, including our current subprocessor list and data-handling specifics, is shared with platforms during Production review.
Credits
Real footage. Rendered in characters.
Updated 2026-09-11
An illustrative story
This is an illustrative booking story, not a live transaction. Voice is a preview. People in independently filmed stock footage are not presented as Nerova customers or endorsers.
The hair, healthcare and beauty montage illustrates different services, not one person's visits. Medical footage is illustrative, not evidence of any person's health or of clinical care provided by Nerova.
Footage
The selected films are used under the Mixkit Stock Video Free License.
Libraries and typography
Native video presents the films, and FullCalendar supplies the illustrative calendar. React Bits PixelSwap's original keyframes follow the story playhead.
GSAP Observer accepts one deliberate gesture per passage; ScrollTrigger directs the stage. Free scroll restores direct control.