Restricted platform administration
Where platform administration is configured, explicitly authorized platform administrators can review necessary account identifiers, email-verification status, display names, associated businesses, public-profile content and referenced portfolio images. It also shows separate subscription and appointment-payment summaries. It does not expose passwords, authentication tokens, bank details, full card credentials or private customer-business message contents.
Administrative invitations use the configured authentication/email providers and require the recipient to securely claim an ordinary account. Administrative role assignments are maintained separately from self-editable profiles and business ownership. Admin actions require fresh authenticator verification; actions such as suspensions and complimentary grants record the actor, target, required reason, timestamps and safe before/after fields in an audit history that ordinary admins cannot edit or delete. Infrastructure operators remain responsible for controlled access, recovery, retention and legal-request handling; no fixed retention period or moderation-response promise is asserted.
Administrative access requires explicit role assignment and fresh authenticator verification; it is separate from business ownership and ordinary signup. A suspended listing can be excluded from new discovery, bookings and conversations while records needed for existing appointments, cancellations, refunds, history and billing remain available. Complimentary access is separate from moderation and cannot bypass a suspension or silently cancel billing.
1. Who this policy covers
Zaylo provides a public product website, a demonstration marketplace and shared user accounts. This policy applies when you browse the website, use its search, sign in, edit your display name or contact Zaylo. You can browse the public marketplace without creating an account.
The main marketplace displays owner-published business profiles when its database is configured. Fictional businesses and reviews are confined to the labeled demo; product-calendar examples are concepts. Business onboarding collects profile information. Configured published businesses can offer appointment scheduling. A separately gated Preview can support Stripe sandbox payments after setup and owner approval; real online payments are unavailable. Configured accounts can exchange text messages with business owners as described below. Live subscriptions and native mobile apps remain deferred; an isolated Preview can test Solo business billing.
2. Information processed
Account information: email address, a Supabase account identifier, authentication method, verification status, and account creation or update information. A private profile stores your account identifier, display name and creation/update timestamps. The account system also holds access defaults; creating an account does not grant business or administrator privileges.
Credentials: email/password signup and login send the credentials to Supabase over HTTPS. A password-reset submission passes through Zaylo's server to Supabase after a recovery token is verified. Application code does not log passwords or store them in profile records, localStorage or sessionStorage. Supabase handles password authentication and its credential storage; do not send a password by email or through a marketplace search.
Optional identity information: Google sign-in can provide basic account identity information as described below. Phone sign-in has been removed from the website interface. Existing provider configuration may remain, but this website does not request SMS login codes. Unconfigured available sign-in options are disabled in the interface.
Search and technical information: search terms, typed location, category and sorting are included in the page URL. Requests to the website and authentication services can include IP address, browser/device information, requested URLs, timestamps and security events. If you email Zaylo, the receiving mailbox processes your email address, message and any attachments you choose to send.
3. Why information is used
Information is used to create and authenticate accounts, verify email ownership, deliver confirmation and recovery messages, maintain signed-in sessions, display and update your private profile, respond to support/privacy requests, and detect or investigate misuse. When scheduling is configured, verified account identity is used to associate appointments with their customer. No live online payment is collected; a configured Preview can use clearly labeled Stripe sandbox transactions.
Search information is used to match and sort published profiles or the separately labeled fictional demo. The site does not request your device's precise location. Current application code has no advertising, marketing-email, data-brokerage or application-analytics integration.
Business profiles and uploaded media
Owners can save a business name, public slug, category, description, location type, address or service area, timezone, currency, weekly hours, service descriptions, durations, prices and optional logo, cover and portfolio images. Membership records associate a verified account with the business and remain private. Draft business records and files are accessible only to their authorized owners through application permissions, in addition to authorized service administration.
Publishing makes the business profile, physical address or service area, opening hours, active services and selected media publicly accessible. Email and phone contacts are included publicly only when their display controls are selected. Private account email and hidden business contacts are not included in the public profile interface. Do not place private customer, employee or sensitive personal information in descriptions or uploaded images.
Supabase Storage holds uploaded business images in a private bucket. The application issues short-lived signed links only for owner access or referenced images on a published profile. Unpublishing stops new public access; previously issued links may remain usable for up to 60 seconds and previously downloaded copies cannot be recalled. Replacement attempts to remove the old file; interrupted uploads or cleanup failures may leave private unused files requiring owner/operator removal. Website hosting processes image uploads through the server; no real appointments, customer histories or payment information are collected by this feature.
Appointment information and access
When scheduling is configured, Zaylo stores the customer account identifier and display-name snapshot, business and service references/names, UTC start/end instants, business timezone, service duration/buffers, price/currency, saved change rules, status, request key, revision and timestamps. Owners see appointments for businesses they own and the customer display-name snapshot; the scheduling interface does not expose customer account email or phone. Customers see their own saved appointments. Public availability returns times, not customer identities or appointment records.
Appointment records support confirmation, customer and owner management, conflict prevention and a saved history. Cancellation releases the time but does not delete the record. Rescheduling updates the saved time atomically; original service/price/change-policy snapshots remain. Owners can add private block labels and date overrides. Database access rules restrict these records, while authorized infrastructure/service administration can still access them for operation and support.
Current confirmations and status information appear in the website. Production appointment email sending remains disabled. A separately configured Preview can send transactional confirmation, cancellation, rescheduling and reminder emails, as described below. SMS reminders are not sent, and the feature does not request Google Calendar or additional Google scopes. A short-lived zaylo-return cookie can preserve an internal booking destination during same-browser email signup verification; it is removed after confirmation and expires after one hour. Booking selections/request keys can appear in private page URLs and technical logs; do not share private appointment links. Retention, deletion handling and broader launch disclosures still require owner review.
Appointment emails and preferences
A separately configured test Preview supports appointment confirmation, cancellation and rescheduling emails to the affected customer and authorized owner account, optional customer reminders and optional owner new-booking notifications. It uses verified account email addresses, not a business public-contact field. Pending unpaid reservations do not produce confirmation emails. Production sending remains disabled pending separate launch approval. SMS, marketing and push notifications remain deferred.
When enabled, Supabase stores durable notification jobs, preference choices, exact provider-request content for retry safety, delivery identifiers, attempts and safe status/error categories. Resend processes the recipient address, business/service name, appointment reference, saved time/timezone and location, message content, and authenticated management links. Private notes and message contents are excluded. Links require normal sign-in and do not perform cancellation or refunds. Open/click tracking is not implemented by this feature; provider-domain tracking settings must also be reviewed before activation.
Customers can disable optional reminders and owners can disable optional new-booking messages in Account > Email preferences. Essential appointment-change emails cannot be disabled through these optional settings. Verified provider bounce, suppression and complaint signals can prevent further delivery; email acceptance is not proof of delivery, reading or a completed booking/payment. Queued work is rechecked against current state, but a message already handed to a provider cannot be recalled and delivery can be delayed or fail. Do not rely on an email as the only source of appointment status; check the authenticated appointment page.
Authorized admins can inspect limited delivery-health fields and audit eligible retries without reading full bodies, recipient addresses or raw provider payloads through the admin panel. Infrastructure operators and the provider can access delivery data to operate the service. Retention for jobs, frozen request bodies, suppression records, logs and provider receipts; deletion/export handling; processor terms; lawful bases and international transfer arrangements remain owner-review decisions. No fixed retention, delivery guarantee or legal certification is asserted.
4. Google sign-in and Google user data
Choosing Continue with Google, when configured, sends you to Google and Supabase for authentication. Zaylo requests only the basic identity scopes openid, email and profile. Google can return an account identifier, email address and verification status, name and profile-image URL. Supabase can store returned identity information in authentication/identity records; the current Zaylo account screen uses your account identity and separately editable display name, rather than a public Google profile.
Google identity information is used to identify, create or sign into your Zaylo account and support that account's security. Zaylo does not request access to Gmail messages, Google Drive files, contacts or Google Calendar through this sign-in flow. It does not use Google user data for advertising, sale, data brokerage or training AI models. No Google API feature beyond basic sign-in is implemented.
Google and Supabase process the authorization and identity exchange. Session and provider tokens returned during authentication are handled by the authentication integration and may be present in session storage cookies; they are not displayed as profile fields. The current application does not use a Google token to read unrelated Google services. Infrastructure providers can process technical requests needed to serve and secure the account flow.
Google data follows the same account-storage, restricted-access and manual deletion-request practices described in this policy. You can decline Google sign-in and use another configured method. You can also review or revoke Zaylo's connection in your Google Account's third-party connections settings. Revoking Google access does not itself delete information already stored in your Zaylo account, and a separate sign-in method is not automatically guaranteed. Contact Zaylo to request account deletion or help with access.
5. Service providers and disclosures
When an owner starts Stripe business onboarding, the server can supply the owner's verified account email as the connected account contact. Stripe's hosted flow collects the remaining required business/identity information. The account is created through Stripe's Accounts v2 API; compatible account status and payment events are processed by the server. A test account or onboarding return does not establish live eligibility.
Stripe sandbox preparation: when explicitly configured on a test Preview, Stripe hosts business onboarding and Checkout. Zaylo sends the selected service/business description, trusted amount/currency and internal payment/hold references to Stripe. Supabase stores the connected-account mapping, readiness requirements, appointment/service/policy snapshot, payment/refund/dispute states and provider identifiers. Access is limited by customer/business permissions and trusted server operations. App code does not store card numbers or bank credentials. Stripe receives the information entered on its hosted forms and processes technical information under its own privacy practices. Do not enter real payment credentials into a test flow. No actual sandbox transaction is implied by installing this integration.
Vercel serves the website, application routes and locally bundled assets. Supabase provides authentication and the account/profile database. Resend is configured as the SMTP sender for account-confirmation and password-reset emails; it processes delivery addresses, message content containing the verification link, and delivery/security information needed for that service. Google processes Google sign-in when you select it and the provider has been enabled. The published contact mailbox uses Google's Gmail service.
Phone authentication and SMS delivery require a configured SMS provider; the documented setup example uses Twilio, but the phone option remains unavailable until that setup is complete. Cloudflare Turnstile is used for bot checks only when its widget and Supabase CAPTCHA settings are configured. It can process device/network and challenge information, with a challenge token passed to Supabase. This description of a planned integration does not mean it is already active.
These providers process information under their own service arrangements and privacy practices, and their infrastructure may operate in countries different from yours. The owner must confirm actual processing regions and any required transfer arrangements; this policy does not claim that data remains in a particular country or assert an unverified certification.
The application has no feature for selling account or Google identity data or publishing private profiles to sample businesses. Access through provider administration tools may be available to the service operator for account support, security and operation. Legal or regulatory disclosure obligations, if any, depend on the actual operator and applicable law; no fictional legal entity or jurisdiction is assumed here.
7. Storage and retention
Account, identity and profile records are stored in the configured Supabase project. Application code does not currently implement an automatic account-retention or inactivity-deletion schedule. Records remain until removed through an administrative process; a display-name edit or logout does not delete the account.
Authentication logs, hosting logs, email delivery records, support messages, and provider backups can have separate retention settings. A deletion request may require review of those systems rather than removal of a single profile row. A fixed retention period, immediate backup erasure or universal deletion deadline has not been established and is not promised in this review copy. The owner must finalize those operational decisions before public launch.
8. Access, correction and deletion requests
You can update your display name in Your account and use the password-recovery flow for an email/password account. There is no self-service account deletion or export button in the current website.
Email zaylobooks@gmail.com to request access to, correction of, export of or deletion of your account information, including Google identity information held for your Zaylo account. Describe the request and the account email or phone number involved. Do not include passwords, SMS codes, session tokens or recovery links. Zaylo needs to verify that a requester controls the relevant account before disclosing or changing private information.
These requests require manual handling. The exact scope of a request, any lawful exceptions and the rights available to you depend on the applicable circumstances and law; this policy does not claim rights or response deadlines for an invented jurisdiction. Where you have a right to contact a privacy authority or withdraw consent, using this website does not remove it. The owner must maintain a monitored request channel and complete the applicable operational procedures.
Business subscription sandbox
A separately configured isolated Preview can test a Solo business subscription: $9.99 USD per month, with one eligible 14-day introductory trial and a card required. Customer accounts remain free. Team is planned at $19.99 USD per month and cannot be purchased until staff functionality exists. No live subscriptions are sold by this integration.
Stripe collects payment methods through hosted subscription Checkout, handles automatic renewal attempts and provides invoices and cancellation through its Customer Portal. Zaylo stores business/owner associations, provider identifiers, verified status and access dates, trial-use records and operational event identifiers. Zaylo does not store full card numbers. Subscription billing is separate from appointment payments and Stripe processing fees.
Cancel before the trial ends to avoid its first charge. Trial access is retained through the trial end; paid cancellation stops renewal and preserves the paid access period. The actual dates and status are shown in Plan & billing. Expired access restricts discovery and new bookings/conversations while retaining existing appointments, messages, cancellation/refund operations and billing access. A complimentary-access override does not cancel a subscription or waive processing fees.
Live refund terms, tax treatment, operator details, retention, ownership-transfer handling and other commercial decisions still require owner review before any live launch. No subscription-refund entitlement, legal jurisdiction, tax exemption or compliance certification is established by this draft.
Customer-business messages
When messaging updates are configured, Zaylo stores recipient delivery and read-through positions. Sent means the server saved the message; Delivered means a recipient app acknowledged loading it; Read reflects viewing through that message, not understanding or a promise of response. Temporary typing metadata records a conversation, user and expiry time, never the unsent draft text. Active typing expires after twelve seconds without a heartbeat. Signals may lag or be unavailable during connection problems. Business owners can disable new customer messages while retaining conversation history and the ability to reply.
When messaging is configured, Zaylo stores conversation participants, business identifiers, message text, sender identifiers, timestamps, optional validated appointment references, delivery retry identifiers, read positions and business pause settings. Customer profile display names are shown to the business in its protected inbox. Messages are not public. The customer and current authorized business owners can access their conversation through application permissions. Global administrator status does not grant access to message contents through the application. Infrastructure/service administration may access stored data as necessary to operate the service; this is not end-to-end encrypted messaging.
The service uses this data to deliver conversation history, calculate unread counts, recover missed updates, prevent duplicate sends, enforce rate limits and allow a business to pause new customer messages. Polling occurs while the inbox is visible; there are no email, SMS or push message notifications. Drafts remain in the open browser tab and are not persisted by Zaylo before sending. A message is shown as sent only after database confirmation; a network error may leave delivery uncertain until refreshed or retried with the same key.
Sent messages cannot be edited or deleted through the current application. The owner has not finalized message retention, account deletion treatment, business ownership-transfer access or moderation procedures. No retention deadline, automatic erasure, moderation team or encryption promise is made. Account/business deletion can be restricted by retained conversation references. Contact the published privacy address about data requests; do not send passwords or payment details in chat.
Customer reviews
After an appointment is marked completed and its end time has passed, its authenticated customer can submit or edit one star rating and an optional written review. Business owners cannot review their own businesses. Zaylo stores the review with the appointment, customer and business identifiers to enforce these rules. Ratings, review text and publication date are public on a published business profile; account email, phone number and customer identifiers are not included in the public review response. Do not include sensitive information in a review. Contact the published support address for review-related privacy or content concerns.
9. Security and information in links
The application uses HTTPS, verifies authentication sessions on protected account routes, and applies database row-level permissions so members can read their own profile and update only their own display name. Signup metadata cannot grant role or paid-access privileges. These controls reduce risk but are not a promise that any online system is risk-free or a certification of compliance.
Search values can appear in browser history, copied links and request logs. Confirmation and recovery links contain temporary authentication material until used. Keep them private. Zaylo's account/auth routes use private, no-store and no-referrer response headers, but external hosting or email systems may still process request metadata. Report suspected unauthorized account access to the published contact; never forward credentials as proof.
10. Eligibility and future features
The website is a product and account demonstration, not a child-directed service. The operator has not finalized a jurisdiction-specific age or eligibility policy. Do not create an account for another person or submit a child's information through support or search. The owner must resolve eligibility requirements before a broader launch.
Configured appointments and the gated sandbox payment preparation are described above. Live online payments, external messages, subscriptions and native apps remain deferred. Before activating new uses, Zaylo must update its disclosures and implement the appropriate permissions and user choices; the current sign-in permission is not permission to access additional Google services later.
11. Changes and questions
The last-updated date identifies changes to this page. Review it before providing information. Material new purposes or additional Google permissions require updated disclosures and any authorization required for that change; a future roadmap item is not an existing consent. Email zaylobooks@gmail.com with questions about this policy or the current account features.
Contact and operator information
Zaylo is the public-facing service name. No registered company identity, governing jurisdiction or postal address is asserted by this document. Additional operator disclosures must be supplied where required before public launch.
- Service
- Zaylo
- Contact
- zaylobooks@gmail.com