Privacy Policy
1. Scope and roles
2. Collection of personal data
| Category | Description |
|---|---|
| Account and identity | Information you provide when creating or managing an Orya account, such as your name, email address, phone number, password (stored by our authentication provider), profile photo, and role within a salon or organization. |
| Salon and business operations | Information about your salon, organization, services, staff schedules, inventory, and business configuration that you enter to operate the platform. |
| Client and booking records | Information about end clients who book or receive services through your salon, including contact details, appointment history, notes, preferences, and communication consent records. |
| Payments and billing | Payment amounts, transaction status, subscription details, gift-card purchase and refund identifiers, and limited payment-method display data (such as card brand and last four digits). Full payment credentials are processed by Stripe, not stored by Orya. |
| Gift cards | Stored-value gift card records created by salons or public purchasers, including purchaser and recipient contact details, optional personal messages, face value and balance metadata, masked code references, delivery-token balance links, redemption holds, and related Stripe Connect payment identifiers. |
| Communications | Email and SMS content, delivery metadata, and consent records for transactional messages (such as booking confirmations, gift-card delivery, and purchaser confirmations) and marketing messages where permitted. |
| Technical and usage | Device, browser, log, diagnostic, and security data collected automatically when you use the Services, including IP-derived signals used for rate limiting and fraud prevention. |
Personal data you provide to us directly
This includes information you or your team submit when registering, configuring a salon, managing clients, or communicating through the platform.
| Data category | Examples | Source | Purpose |
|---|---|---|---|
| Identity and contact | Name, email, phone number, profile photo | Account signup, profile settings, staff invitations | Authentication, account administration, support, and communications |
| Salon business profile | Salon name, address, phone, email, services, pricing, landing page content | Salon setup, page builder, service catalog | Operate booking, scheduling, public salon pages, and business workflows |
| Staff and team records | Staff role, specialties, schedules, invitation email, working hours | Salon owners and managers | Staff management, permissions, scheduling, and onboarding |
| Client and booking records | Client name, email, phone, appointment details, notes, SMS opt-in status | Salon staff, public booking flows, guest bookings | Appointment management, CRM, reminders, and service delivery |
| Gift card records | Purchaser and recipient name/email when provided, optional personal message, face value, balance and hold amounts, masked code last four digits, hashed code and delivery token, expiration snapshot, assigned client link, Stripe payment identifiers | Salon staff sell flows, public gift-card checkout, delivery and resend, redemption against bookings | Issue and activate cards, deliver codes and balance links, redeem, refund, revoke or restore stored value, and support salon reporting |
| Communication consent | Marketing or transactional SMS/email consent, legal text shown, audit timestamps | Salon staff actions and client opt-in choices | Compliance with messaging laws and consent audit trails |
| Waitlist and marketing inquiries | Full name, salon name, email, phone, referral source | Homepage waitlist or demo request forms | Product updates, onboarding outreach, and lead follow-up |
| Support communications | Name, contact details, message contents | Emails or support requests you send to us | Respond to inquiries and resolve issues |
Personal data we receive automatically from your use of the Services
When you use Orya, we and our service providers may collect certain technical information automatically, consistent with your device or browser settings.
| Data category | Examples | Source | Purpose |
|---|---|---|---|
| Device and connection | Browser type, operating system, IP address, referrer, time zone | HTTP requests, authentication sessions, security controls | Security, fraud prevention, rate limiting, and service delivery |
| Usage and logs | Pages viewed, actions taken, timestamps, error logs, performance traces | Application logs and diagnostic tooling | Operate, debug, secure, and improve the Services |
| Cookies and similar technologies | Authentication cookies, salon context, consent preferences, UI state | First-party cookies and local storage | Authentication, preferences, security, and platform functionality |
3. Uses of personal data
4. Rights and choices
5. Recipients, subprocessors, and disclosures
| Vendor | Purpose | Data shared | Location |
|---|---|---|---|
| Convex | Application backend, database hosting, realtime synchronization, and scheduled jobs | Account, salon, staff, client, booking, messaging, and operational records processed by platform features | Convex-managed infrastructure for the configured Orya deployment |
| Supabase | Authentication, database hosting, file storage, and realtime infrastructure | Account credentials and metadata, salon and client records, gift-card records when stored in the primary database, uploaded images | United States (primary hosting region per project configuration) |
| Convex | Optional application data platform for selected product domains when enabled for an environment | Gift-card issuance, ledger, holds, and related booking/payment metadata when the gift-cards Convex data provider is on | United States (Convex cloud regions per project configuration) |
| Vercel | Application hosting, serverless runtime, deployment, and AI Gateway routing | Request metadata, server logs, deployment configuration, AI feature payloads when enabled | United States and global edge locations |
| Stripe | Platform subscriptions, Stripe Connect payouts, client checkout payments, and gift-card purchase or refund flows | Billing contact details, payment amounts, transaction identifiers, Connect account status, gift-card checkout metadata | United States and jurisdictions where Stripe operates |
| Brevo | Transactional email (SMTP) and transactional or marketing SMS delivery | Recipient name, email, phone number, and message content (including gift-card delivery and purchaser confirmation emails) | European Union / United States (per Brevo processing terms) |
| reCAPTCHA v3 (waitlist, when enabled) and Maps embeds on public booking pages | IP address, browser signals, risk score, encoded salon address in embed URLs | United States and global Google infrastructure | |
| Upstash | Distributed rate limiting and abuse prevention | Hashed or derived identifiers from client IP or browser fingerprint (short TTL) | United States (Redis REST regions per configuration) |
| Sentry (self-hosted) | Error monitoring, performance tracing, and sampled session replay when enabled | Sanitized error context, stack traces, performance spans; PII redaction applied by default | United States (configured instance: sentry.aieasy.chat) |
| Vercel AI Gateway and model providers | AI Insights analytics summaries and package banner generation when features are enabled | Aggregated salon operational metrics for insights; package and salon marketing text for banners (no client names in default prompts) | United States and provider regions selected by gateway routing |
7. AI and automated processing
8. Data retention
| Data type | Retention period | Criteria |
|---|---|---|
| Account and profile data | For the life of the account plus a reasonable period thereafter | Needed to provide the Services, resolve disputes, and comply with legal obligations |
| Booking and client records | While the salon account is active, unless deleted or configured otherwise | Salon business needs, configurable retention settings where available, and legal or tax record requirements |
| Payment and subscription records | As required for billing, reconciliation, fraud prevention, and tax compliance | Contractual, accounting, and regulatory requirements |
| Gift card records and ledger | While the salon account is active and for a reasonable period thereafter for refunds, disputes, and operator reporting | Salon stored-value liability, audit trails, and applicable tax or unclaimed-property recordkeeping needs of the salon |
| Communication and consent logs | For the period needed to demonstrate consent and message delivery | Messaging compliance, dispute resolution, and audit obligations |
| Technical logs and diagnostics | Typically months, depending on system configuration | Security monitoring, troubleshooting, and service reliability |
| Waitlist signups | Until you unsubscribe, we remove the record, or it is no longer needed | Marketing outreach and product launch communications |
| Cookie consent preferences | 12 months | Document and honor your cookie choices |
9. Security
10. International transfers
11. Supplemental disclosures for California residents
| Category | Examples | Collected | Disclosed | Sold or shared |
|---|---|---|---|---|
| Identifiers | Name, email, phone, account ID, IP address, cookie identifiers | Yes | Yes | No |
| Customer records | Appointment history, client notes, salon configuration, billing contact details | Yes | Yes | No |
| Commercial information | Services purchased, subscription plan, transaction amounts, package or membership records, gift card purchase and balance records | Yes | Yes | No |
| Internet or network activity | Log data, pages viewed, diagnostic events, cookie preferences | Yes | Yes | No |
| Geolocation data | Approximate location derived from IP address; salon business address you provide | Yes | Yes | No |
| Audio, electronic, or visual information | Profile photos and uploaded salon or staff images | Yes | Yes | No |
| Professional or employment information | Staff role, specialties, schedules, organization membership | Yes | Yes | No |
| Inferences | AI-generated operational insights from aggregated salon metrics (when AI Insights is enabled) | Yes | Yes | No |
| Sensitive personal information | Account login credentials; payment-related data processed by Stripe; SMS opt-in records | Yes | Yes | No |
12. Children
13. Legal bases for processing
| Purpose | Data categories | Legal basis |
|---|---|---|
| Provide, maintain, and operate the Orya platform and your account | Identity, salon, booking, payment, and technical data | Performance of our contract with you; legitimate interests in operating a secure SaaS platform |
| Process bookings, scheduling, client management, and salon workflows | Client records, staff records, appointment data, communications | Performance of our contract; processing on behalf of salon customers where applicable |
| Facilitate payments, subscriptions, and Stripe Connect onboarding | Billing contact details, transaction data, Connect account identifiers | Performance of our contract; compliance with payment network and financial regulations |
| Issue, deliver, redeem, refund, revoke, restore, and report on salon gift cards | Purchaser and recipient contact details, personal messages, balance and hold metadata, delivery tokens, Stripe gift-card payment identifiers | Performance of our contract with the salon; processing on behalf of salon customers where applicable; legitimate interests in secure stored-value tooling |
| Send transactional email and SMS (confirmations, reminders, gift-card delivery, account notices) | Contact details, appointment details, gift-card delivery content, message content, consent records | Performance of our contract; consent where required for SMS; legitimate interests in service delivery |
| Provide optional AI features (AI Insights, package banners) when enabled | Aggregated operational metrics; package and salon marketing text | Performance of our contract; legitimate interests in product improvement with data minimization controls |
| Prevent fraud, abuse, and unauthorized access; enforce our terms | Identity, technical, usage, and security log data | Legitimate interests; legal obligations; vital interests where applicable |
| Improve reliability, debug errors, and monitor performance | Technical logs, diagnostics, sanitized error reports | Legitimate interests in maintaining a reliable and secure service |
| Comply with law, respond to lawful requests, and protect rights and safety | Any categories reasonably necessary to respond to the request or risk | Legal obligation; legitimate interests; vital interests where applicable |