Privacy Policy

2a. From Merchants & Staff (B2B Users)

• Account data: First name, last name, email address, phone number
• Authentication data: OTP codes (6-digit, 2-minute TTL), Google OAuth sub-ID, OAuth tokens
• Business data: Entity name, store name, store slug, store address, timezone, logo (stored in Cloudflare R2)
• Calendar data: Google Calendar OAuth access token and refresh token, calendar email, linked calendar ID (stored encrypted)
• Subscription & billing data: Plan name, billing cycle, payment status, Razorpay Order ID, Razorpay Payment ID. Card/UPI details are never stored by Tailro; they are held by Razorpay
• Staff availability data: Working hours, break times, leave dates, per-store role (Owner, Manager, Staff)
• Usage logs: Feature usage metrics (appointments created, staff count, services count) used for plan enforcement

2b. From End Customers (Booking Users)

• Identity: First name, last name, email address, phone number
• Authentication data: Email OTP, Google OAuth sub-ID, Shopify Customer Account ID (if 'Login with Shopify' is used at a store's booking page)
• Booking history: Appointment date/time, service, staff, status, location, online meeting URL, notes, payment status, price paid
• Payment records: Amount paid, currency, payment method type (not card details), Razorpay transaction ID
• Store relationship: Which stores the customer has booked at

2c. From Shopify Integration

• Shop domain (e.g. my-store.myshopify.com)
• OAuth access token (permanent, stored server-side, never exposed in API responses)
• Granted OAuth scopes (e.g. write_customers, read_orders)
• Navigation menu GIDs (Shopify internal GraphQL IDs for the booking link in the merchant's store menu)
• Shopify Customer Account API credentials (client ID and client secret) for 'Login with Shopify' on the booking page
• Shopify customer records synced from/to Shopify: name, email, phone

2d. Files & Media

• Store logos uploaded by merchants, stored in Cloudflare R2
• Staff profile pictures, stored in Cloudflare R2
• Store gallery images, stored in Cloudflare R2
• Invoice documents, stored in Cloudflare R2
• All files are served via Cloudflare R2 public CDN URL

2e. AI Booking Assistant (Chat)

• Chat messages customers send to the Tailro AI booking assistant on a store booking page
• Assistant replies and related booking-help context needed to answer the request
• Tool/action results from Tailro's own APIs only (for example: services, availability slots, and booking confirmation details from Tailro)

The AI booking assistant does not read Google Calendar contents, Google Calendar OAuth tokens, or Google Workspace API responses. It only uses Tailro platform data needed to help customers book.

2f. Technical / Automatic Data

• HTTP request logs: timestamp, HTTP method, URL path, response status, latency
• IP addresses (implicit in HTTP request handling)
• Request headers including User-Agent

5a. How our AI booking assistant works

Tailro's AI booking assistant uses Anthropic's Claude models through Anthropic's commercial API. In production we currently use Claude Haiku 4.5 (claude-haiku-4-5-20251001).

The assistant helps customers on a merchant's booking page by answering service questions and guiding them through booking. To do that, it may receive chat messages and Tailro platform data such as services and available slots returned by Tailro's own APIs.

The assistant does not call Google Calendar APIs and does not receive Google Calendar event contents, calendar lists, free/busy data, or Google OAuth tokens. Google Calendar sync is handled separately by Tailro's backend scheduling system after a booking is created or updated in Tailro.

Under Anthropic's commercial API terms, API customer content is not used to train Anthropic's foundation models. Tailro does not use Google Workspace or Calendar user data to train or improve any AI models.