HP Studio
LidcardClient book for iPhone

Lidcard Privacy Policy

Last updated

On this page
  1. Summary
  2. Your book
  3. Your clients’ information
  4. iCloud
  5. Camera, photos, Contacts and Face ID
  6. What Lidcard does not access
  7. Data we collect
  8. Exports and PDFs
  9. Retention and deletion
  10. Children
  11. Changes
  12. Contact

Summary

Lidcard is an iPhone app operated by Harsh Patel. It is a client book for lash, brow and nail techs. It has no accounts and does not ask for your name or email. Your book (your clients, their visits, lash maps, photos, bookings, patch tests, consent forms and signed PDFs) is stored on your iPhone and, with iCloud on, in your own private iCloud. It goes to another person only if you share a PDF or export a file yourself. We do not operate a server that stores your book, we cannot read it, and we do not sell data, show ads or track you across other companies’ apps or websites.

Your book

  • Your clients: the name, phone, email and birthday (month and day) you add or pick from Contacts, and your notes about each one, such as the allergies you note.
  • Visits: the services, the lash map (lengths by zone, curl, diameter and style), your notes, and the before and after photos you take.
  • Bookings you add by hand, and each client’s fill interval, so the Due list knows who is due.
  • Patch tests: the date, the product and the words you noted.
  • Consent: your forms, and for each signing the form text she signed, her answers, her signature and the signed PDF.
  • Your studio name, your text template and your settings.

Your book is kept in the app’s own storage on your iPhone.

Your clients’ information

The details in your book are about your clients, and you are the one who keeps them. We cannot see them and never receive them. Settings > Recently removed > Delete forever deletes a client and everything on her card from your iPhone, and iCloud removes its copy the next time the app syncs. The terms of use say more about your part.

iCloud

  • With iCloud on, Lidcard uses Apple CloudKit to keep a copy of your book in your private iCloud database under your Apple Account, so it is backed up and comes back on a new iPhone. We cannot access your private iCloud data.
  • Lidcard 1.0 has no sharing: nobody else can open your book through iCloud.
  • iCloud may send silent background pushes so your book stays in sync. Lidcard sends no notifications.

Camera, photos, Contacts and Face ID

  • The camera takes before and after photos for visits and patch tests. Photos are stored only in your book, with location and other photo data removed.
  • Contacts: Apple’s contact picker gives Lidcard only the people you pick. Lidcard does not ask for access to your contacts and never reads the rest of them.
  • Spreadsheet import: a CSV file you choose is read on your iPhone. Its file name, columns and cells never leave your iPhone.
  • Client view: after a client signs, your Face ID or iPhone passcode unlocks your book. Face ID is handled by iOS; Lidcard never receives your face data.
  • Texting a client opens Messages with your template filled in. You send it yourself; Lidcard never sends messages for you.
  • Change camera access anytime in iOS Settings.

What Lidcard does not access

Lidcard does not use your location, your calendar, health data, the rest of your contacts, or the content of your Messages or Mail. It never contacts your clients for you.

Data we collect

Lidcard has no accounts, and nothing it collects includes your name, email, phone number, studio name or Apple Account, or anything about your clients. The data below is pseudonymous, but it is linked in Apple’s sense: it is tied to random identifiers for your install, and those identifiers are joined to each other. It is not used for tracking: Lidcard has no ads, does not use the advertising identifier (IDFA), does not ask to track you, and does not share data with data brokers or advertisers.

  • Product interaction: which steps you complete in the app, from a fixed list of events, with counts, ranges and yes or no flags. Sent to PostHog. Purpose: analytics.
  • Purchase history: your subscription or Lifetime status, trials, renewals and cancellations, from Apple’s signed purchase records via RevenueCat. Purposes: app functionality, analytics.
  • User ID: a random app user ID created by RevenueCat and a random analytics ID created by PostHog, joined so purchase events appear in the product funnel, plus a random ID for your book so a restored book or a second iPhone can be matched. None of these is your name, email or Apple Account. Purposes: app functionality, analytics.
  • Device ID: the identifier for vendor (IDFV) that the RevenueCat SDK sends with its requests. It is not the advertising identifier. Purposes: app functionality, analytics.
  • Advertising data: Apple’s AdServices attribution token. Lidcard sends it to Apple, and to RevenueCat, to learn whether the install came from an Apple Search Ads campaign and, if so, which campaign, ad group and keyword. Lidcard keeps only that answer. Purpose: analytics.
  • Crash data: crash reports from Apple’s MetricKit (crash kind, exception type and code, signal and app build), sent as PostHog events. Purposes: app functionality, analytics.
  • Performance data: hang reports from MetricKit (how long the app was unresponsive and the app build), sent as PostHog events. Purposes: app functionality, analytics.

What analytics contain. Analytics come from a fixed list of events and properties; anything else is dropped before sending. They include the app version, whether a plan is active, roughly how many clients you have (in ranges) and which kind of step you completed. Screen recording, session replay and automatic tap capture are off, and PostHog’s location lookup is turned off, so analytics carry no country or city. Analytics never include client names, phone numbers, emails or birthdays, your studio name, notes, allergies, lash maps or lengths, patch test dates, products or results, consent form text, answers or signatures, booking times or visit dates, photos, spreadsheet contents, search text, or the messages you write.

Payments. Payments go through Apple In App Purchase; we never receive your payment card details. RevenueCat checks your purchases for us; its privacy policy is at revenuecat.com/privacy. PostHog’s is at posthog.com/privacy.

Exports and PDFs

Consent PDFs, client PDFs and Export everything (a zip of CSV files, consent PDFs and photos) are created on your iPhone. When you share one, iOS sends it to the destination you choose, such as Messages, Mail or Files. Lidcard does not record where you send it.

Retention and deletion

  • Your book stays on your iPhone and in your iCloud until you delete clients in the app, or delete the app and its iCloud data.
  • Exported files and purchase history are separate: delete exported copies where you saved them, and manage iCloud data and subscriptions in Apple Settings.
  • We keep analytics only as long as it is useful for improving the app. Email us to ask for deletion of analytics data. Because it is not tied to your name, tell us roughly when you installed Lidcard and your device model so we can find it.

Children

Lidcard is meant for adults running a studio and is not directed to children under 13. We do not knowingly collect personal information from children.

Changes

If our data practices change, we will update this page and the date above, and update the app’s App Store privacy details.

Contact

Questions, complaints or data requests: lash-client-book@hpstudio.app