These pages preview the pilot draft prepared November 17, 2026. Some details remain to be confirmed, shown in square brackets. No effective date has been set. Reading this page does not record agreement or consent.
Free practice pilot. Pretend bookings only. No real service visits or payments.
Who operates Hepzenta
Hepzenta is a service discovery and booking platform operated by Oluseyi Asaolu. Contact [email protected] about privacy, account access, or support. This notice covers the Hepzenta pilot for Canada and the United States. Bookings and conversations are practice tests only: do not arrange real service visits or payments. Use fictional service details, worker names, and booking notes, and mark each request TEST ONLY. Account email, authentication and device information can still be real personal information even in a simulated pilot.
Information used by the pilot
Depending on the features you use, Hepzenta handles:
• Account details: name, email, sign-in credentials handled by the authentication service, account identifiers, and account type.
• Provider details: business name, service category, phone number, city, description, and approval/review information.
• Appointment details: participating accounts, requested dates and times, duration, status, notes, and worker assignment.
• Worker details entered by providers: display names, active status, working hours, timezone, and days off. Providers must have authority to supply another person's information and explain its use to them.
• Booking conversation messages, favourites, in-app alerts, and notification read status.
• When phone notifications are enabled: notification token, device platform, and account/session association needed to deliver updates.
• Sandbox subscription identifiers, checkout attempts, trial dates, and cancellation status. Email supplied at checkout is also handled by Stripe.
• Support correspondence and operational records generated by our hosting, authentication, and notification services. [Confirm the exact log fields and retention settings before publication.]
City information is supplied through profiles and search. Do not describe this pilot as collecting precise GPS location unless that feature is actually added and disclosed.
Why information is used
Hepzenta uses account and profile information to provide sign-in, show service listings, and route customers and providers to their workspaces. Appointment information and messages support booking requests, scheduling, cancellations, and conversations. Worker schedules help check appointment availability. Alerts and optional phone notifications communicate booking and message updates. Approval records support provider review. Operational records help investigate failures and protect account access. Sandbox information is used to test subscriptions and cancellations without real platform charges.
We will identify any materially new purpose before using personal information for that purpose and obtain consent where required. [Confirm and document the lawful basis for each purpose, including applicable Canadian and U.S. federal/state requirements. Do not treat agreement to terms as blanket consent.]
Who receives information
Provider listing fields intended for publication are shown to people browsing service providers. Customers and the relevant provider receive the booking and conversation details needed to arrange a service. Authorized administrators can review provider applications and handle support issues. [Verify the exact profile fields visible to browsing users and worker access permissions before publication.]
Current technical services include Supabase for authentication and application data, Expo and Firebase/Google for Android notification delivery, and Stripe for sandbox checkout. Their services process the information needed for their respective roles. Support messages sent to our Yahoo address are also handled by the email service. We may disclose information when required by applicable law or to handle a lawful request.
International processing
The pilot serves two countries and uses external technology providers. Information may be processed outside the country where you live. Foreign laws may permit access by courts or authorities. [Confirm and disclose the actual database, backup, support and subprocessor locations; document appropriate transfer arrangements and safeguards for Canadian and U.S. users before publication. A general statement or checkbox alone does not establish a lawful transfer mechanism.]
Choices and requests
You can edit your profile name and manage available provider profile settings in the app. Phone notifications are optional and can be managed through the app and device settings. Disabling notifications does not itself delete your account.
Contact [email protected] to request access, correction, account deletion assistance, or to raise a privacy complaint. Depending on applicable law and the circumstances, you may also request consent withdrawal, restriction, objection, or portability. We may verify identity in a proportionate way; do not send your password or payment card details. Some requests have lawful exceptions, which we will explain where applicable. You may also contact the relevant Canadian privacy regulator or the relevant U.S. federal or state privacy/consumer-protection authority.
Account deletion and retained records
Use Profile → Delete My Account, then follow the password and confirmation steps. Providers can reach their account profile through Manage My Account. You can also email support for assistance. [Publish and test a public account-deletion request page before store release.]
The current deletion flow removes the authentication account, owned uploaded files, and linked push registrations; closes the linked Stripe sandbox customer and its test subscriptions; removes or scrubs profile information; and clears message text and service notes in affected booking conversations, including text written by other participants. Pending and future accepted bookings are cancelled. Limited booking history may remain with the deleted account link removed and provider/worker details replaced with generic labels. Remaining dates, identifiers and relationships may still be personal information in context; we do not promise irreversible anonymity. Other participants may have independently retained copies. Stripe may retain payment or invoice history under its own practices.
Deletion may take more than one attempt if an external service fails. Some cleanup may already be permanent, and access may be restricted while cleanup is pending. The last active administrator account cannot be deleted through self-service until another confirmed administrator exists. Accounts with verified multi-factor authentication or a large volume of uploaded files currently require an expanded/support-assisted process.
[Before publication, adopt specific retention periods and purposes for active/inactive accounts, remaining booking records, approval logs, support messages, operational/security logs, erasure audit records, and backups. Document expiry and restore handling so deleted data is not reintroduced. Do not promise immediate deletion from backups or complete erasure of every record.]
Security and sensitive information
Hepzenta uses authentication and database access controls. No system can eliminate all risk. Do not send passwords, payment card numbers, government identifiers, medical records, or unnecessary information about children or other people through booking notes or messages. Service categories involving care do not make Hepzenta a medical record system or emergency service.
[Confirm a minimum account age, establish the required age controls, and review handling of children's and sensitive information before admitting pilot users. Do not publish an age restriction as an implemented safeguard until it exists.]
Changes
The published notice will show an effective date and explain material changes. Additional notice and consent will be provided where required.
Built-in Help Assistant
The Help Assistant uses preset local answers. Its search text is not sent to an AI provider by this implementation. Searches stay in screen/widget memory and can be cleared; backgrounding the app alone does not necessarily clear them. Existing authentication, hosting and notification processing is separate.