Privacy Policy
Effective November 4, 2026
Steaze Labs LLC operates Ovatello, a visitor check-in and staff notification service. This policy explains how we handle information through our website, web app, and iOS and Android apps. It covers people who create accounts, organization members and administrators, kiosk visitors, and people who contact us.
Organizations choose how to configure their kiosks, who can access their workspace, and how long to retain detailed visit records. Contact the organization you visit or work with about its own practices and records. Contact us about your Ovatello account or our handling of information using the details below.
Information we collect
- Accounts and staff profiles. Email address, display name, account and sign-in provider identifiers, authentication and security information, organization memberships, roles, and invitations. Organizations may add staff names, contact information, optional staff photos, and their logo. Staff names and photos selected for the kiosk can be visible to visitors.
- Optional work schedules and absences. Organizations can configure recurring work periods, time zones, on-site or remote work, covered locations, and dated work changes. Staff can record time away, including a sickness, paid-time-off, or other away category, with start and end dates or an open-ended absence. We store these entries to calculate availability and decide when and where to route staff alerts. The member concerned and authorized people or routing editors can see the absence category. Other authorized schedule viewers see an away label rather than the sickness or paid-time-off reason. The absence form does not request diagnoses, symptoms, or medical records.
- Optional staff CSV imports. Authorized administrators can upload a CSV file or paste CSV text to add or update staff information. On mobile, pasted text is first written to the app's cache for upload. We parse the upload without keeping the original CSV as a server file; the imported staff records are stored and managed like other staff information. An import is not limited to processing on your device.
- Check-ins. Visit number, time, organization location, kiosk identifier, selected reason, selected staff member or group, language, structured answers such as yes/no or a listed option, and the staff response to the visit. Where service tracking is enabled, records can include service steps, handoffs, and completion times. The standard anonymous check-in flow does not ask for names, contact details, photos, signatures, or free-text notes. Visit details can still be sensitive or become identifiable when combined with information an organization already knows; do not enter visitor identities or medical details in configuration fields.
- Devices and service activity. Notification tokens or browser push subscriptions when alerts are enabled, device registration and kiosk pairing information, app and device details needed to operate the service, error codes, and security and audit records. Requests to our hosting and authentication services may include IP addresses, browser or device information, and timestamps.
- Optional device class lists. Where an organization enables the native kiosk's optional class-list step, a visitor may choose to save a name in an encrypted database on that kiosk. Those names are not sent to Ovatello's servers or alert payloads. A person with the kiosk exit PIN can export or delete the list. The organization controls its retention and the recipients of any exported list; contact that organization about its device records.
- Communications. Information you send when asking for help, and delivery information for invitations, verification, recovery, and service notifications. Please do not send visitor or medical information in a support request. In-app feedback can include text, reviewed screenshots, and optional technical diagnostics that you choose to send. Feedback is private between the submitter and Ovatello support. Images and diagnostics are removed 90 days after closure, and conversation text after one year. You may delete feedback sooner; deleting your account also removes it. When email support is enabled, feedback message text is also stored in our Resend support inbox, and support replies are sent to your verified email address. Screenshots and diagnostics remain in the app behind sign-in. Deletion requests also remove the linked support conversation from the inbox; Resend retains trashed mail for 30 days. Messages already delivered to recipients cannot be recalled.
- Automatic error metadata. Signed-in member apps also send minimal error metadata automatically to help us operate the service: an approved error class and event code, route category, app version, and time. This is separate from optional feedback diagnostics. It does not include error messages, stack traces, form entries, screenshots, or session recordings. Kiosk clients do not submit member-app error events. Collected error events are retained for 30 days; inactive error groups for 90 days. Account or organization deletion removes identifying associations from these diagnostic records.
- Organization administration. Organization settings, subscription or plan status, purchase and renewal history, product and transaction identifiers, and records needed to manage the service. RevenueCat validates native App Store and Google Play purchases using an organization billing identifier. Stripe processes web billing. These providers process payment information under their own policies; Ovatello does not receive your full payment card details from native store purchases.
Google and other sign-in providers
If you choose Sign in with Google, we request basic identity permissions: your Google account identifier, email address and verification status, and basic profile information such as your name and profile picture, when supplied. Google sends authentication tokens so Firebase / Google Cloud Identity Platform can verify your identity and establish your Ovatello session. We use this information to create or access your account, secure sign-in, and associate you with organization memberships you accept.
Google sign-in does not give Ovatello access to your Gmail messages, Drive files, Calendar, or contacts. We do not receive your Google password. We do not use Google account information for advertising or sell it. Google information is handled for the purposes described here and in accordance with the Google API Services User Data Policy, including applicable Limited Use requirements.
If you use another supported identity provider, such as Microsoft, we similarly receive the identity and authentication information needed to sign you in. Your provider also processes information under its own privacy policy. You can review or remove Ovatello's Google access in your Google account connections. Removing provider access does not itself delete your Ovatello account or organization records; see deletion options below.
Where Sign in with Apple is available, Apple and Firebase process the identity and authentication information needed to access your account. Apple may supply a private relay email address instead of your usual email address. Before deleting an account linked to Apple, you confirm with Apple again so its authorization can be revoked. If that confirmation or revocation fails, deletion is not yet accepted and you can retry. Ovatello does not retain the short-lived Apple credential used for that revocation.
How we use information
We use information to authenticate users, enforce permissions, route check-ins, notify staff, display visits and reports, administer organizations and subscriptions, respond to support requests, maintain reliability, prevent abuse, and meet applicable legal obligations. We use essential browser and device storage to maintain sessions, preferences, device pairing, and temporary offline check-in queues.
Where an organization enables QR browser self-check-in, the visitor's browser requests location permission. Coordinates and their accuracy are used to check proximity to the configured site when the session starts and when the check-in is submitted. These guest location samples are not logged or retained. The organization's configured site coordinates are stored separately so the proximity check can work.
An administrator can optionally use the device's current location to configure those site coordinates, after granting location permission, or enter coordinates manually. The coordinates selected for the site are saved with the organization configuration. Ovatello does not request background location access.
Ovatello does not use advertising SDKs or cross-site advertising trackers, sell personal information, or share personal information for targeted advertising. Ovatello does not request address-book access. Camera or photo access, when requested, supports functions such as scanning a kiosk pairing code or choosing an authorized staff or organization image; it is not used to photograph visitors during check-in.
Who receives information
Authorized members of an organization can access information according to their roles. Administrators manage staff profiles, membership, routing, reports, and retention. Organizations are responsible for information they export or use outside Ovatello.
When enabled, guest status pages and lobby displays can show visit numbers and limited status information. These displays use anonymous visit numbers, such as #427, rather than visitor names. An organization chooses whether to enable these displays and should consider who can see them.
We use service providers to operate Ovatello, including Google Cloud and Firebase / Identity Platform for hosting, storage and authentication; Expo and platform push services such as Apple and Google for notifications and app delivery; and Resend for transactional email where enabled. Providers receive information needed for their services, such as device tokens for push delivery or an email address for an invitation. Identity providers process sign-in requests when you choose their sign-in method.
RevenueCat, Apple, Google and Stripe process purchases and subscription records, and RevenueCat provides purchase reporting. Twilio processes staff phone numbers and service messages when a member opts into SMS alerts. If your organization connects Microsoft Teams or Slack, the selected provider receives the linked work-account identifiers and notification content needed to deliver that integration. You and your organization control whether to enable these optional notification channels.
Support access to organization configuration can be granted for a limited time by an owner, revoked, and audited. We may also disclose information when required by law, to protect people or the service, or as part of a business transfer subject to appropriate protection of personal information. We do not provide organization records to other organizations as part of normal service operation.
Storage, security, and retention
We use encrypted connections, access controls, and cloud storage protections to safeguard information. No system can guarantee absolute security. Our production cloud infrastructure is based in the United States; our service providers may process information in other countries where they operate.
Account information is kept while needed to provide and secure your account. Detailed check-in, service history, and audit retention depends on the organization's settings and plan. Summary reports can remain after detailed check-ins are removed. Notification and delivery records, operational logs, exports, and backups have separate retention and cleanup schedules. Information needed for security, legal obligations, or resolving disputes may be retained longer.
Account deletion removes the sign-in identity, organization memberships, and registered alert devices, associated personal staff details and photos, invitations you authored, and in-app feedback. A directory identifier remains for organization history with the personal profile details removed. Organization-owned check-ins, configuration, summaries, billing records, and retained audit history have separate retention schedules. A limited deletion record, including a hashed account identifier, may remain to enforce deletion and prevent an old session from restoring access. Backup copies expire through their normal rotation rather than being erased immediately. Organization closure has a separate grace period and deletion schedule displayed to its owner.
Work schedules and absence entries are organization records. Passing an entry's end date does not delete it automatically. While a staff profile is active, the member or an authorized routing editor can remove its absence entries through the schedule controls; authorized people editors manage its work pattern. Deleting a personal account removes the profile details described above, but does not erase schedule or absence entries kept with the remaining directory identifier. These records are included when the organization's data is permanently deleted; backup copies follow their normal rotation. Contact your organization or use our privacy contact below about these records and deletion requests.
Staff photos uploaded but not assigned to a profile expire after 24 hours. Uploads are tracked before their bytes are stored, so an interrupted upload or failed profile save can still be cleaned up. A cleanup job also removes replaced or removed staff photos once no staff profile uses them. Cleanup normally runs every five minutes and retries storage failures. Assigning a photo to another staff member associates it with that member's profile rather than the administrator who uploaded it. Photos still used by another profile follow that organization's record lifecycle.
Access stops when an account deletion request is accepted. Cleanup normally starts immediately; temporary storage or identity-provider outages are retried automatically every five minutes. Feedback and its attachments are removed through a cleanup job that also runs every five minutes. Deleting an account does not cancel an App Store or Google Play subscription: manage renewal in the store account to avoid future charges. You can delete your account while a subscription is active. The account deletion guide links to store subscription management.
Your choices and requests
You can manage available account and notification settings in Ovatello and turn off notifications in your device or browser settings. Organization administrators can manage membership, staff information, retention, and exports within their permissions.
To delete your account, sign in, open My account → Delete my account, and confirm. Owners must transfer ownership or close their organizations first and complete any required closure confirmation. Read the account deletion guide for details.
You can also contact us to request access, correction, a copy, or deletion of your personal information, including if you cannot sign in. Depending on where you live, you may have additional rights to object to or restrict processing or complain to a privacy regulator. We may need to verify your identity and coordinate with your organization before acting. We will respond as required by applicable law. Do not send passwords, authentication codes, or medical information.
Children
Ovatello member accounts are intended for organization staff and administrators, not children under 13. A kiosk may be used at an organization serving families, but its standard anonymous visitor flow does not ask children or adults for their identities. If you believe a child has provided personal information to us, contact us so we can investigate and address it.
Changes to this policy
We will update this page and its effective date when our practices change. For material changes, we will provide notice through the service or another appropriate channel and obtain consent where required before using information for a new purpose.
Contact
For privacy questions or requests, contact Steaze Labs LLC, the operator of Ovatello, at help@support.ovatello.com with “Ovatello privacy” in the subject. For records controlled by an organization, include its name so we can direct your request appropriately.