Trust
Last updated: 16 November 2026
How patient and clinic data is stored, who processes it, and how long it is kept.
Receptys.ai is operated by C-Vids Productions (UEN 53119647W), Singapore. Questions about security or data can be sent to support@receptys.ai.
Clinic and patient data is stored in Supabase Postgres on AWS in the Tokyo region (ap-northeast-1). The application’s server functions run on Vercel, also in Tokyo. Data is encrypted at rest and in transit.
The AI receptionist answers questions about the clinic, its treatments and prices, and books, moves and cancels appointments. It does not diagnose or recommend a treatment for a patient’s condition. Health and suitability questions are answered only from the clinic’s own FAQs; otherwise the patient is told the doctor will advise at a consultation. Possible complications after a treatment are handed to the clinic’s team straight away, and the clinic gets an email. Prices come only from the clinic’s own service list.
Clinic data, including conversations and bookings, is kept while the account is active. Resolved handoff requests are deleted automatically after 12 months; open ones are kept until the clinic’s team resolves them. After a clinic cancels, its data is kept for 30 days to allow reactivation, then business configuration, conversation logs and booking records are deleted. Billing records may be kept for up to 7 years. A clinic can ask for immediate deletion at any time.
Patient data is collected only for the clinic’s appointment purpose. The clinic is the data controller and Receptys is its data processor. Patients may request access to, or deletion of, their data through their clinic, and we act on the clinic’s instructions.
Row-level security is enabled on every database table, so a signed-in clinic can reach only its own data. Server-side jobs use a service-role key that exists only in server configuration and is never sent to a browser. Database backups are managed by Supabase.