Privacy Policy
Last updated October 15, 2026.
Scope and contact
This Privacy Policy covers NailWage public pages, authenticated app pages, technician token pages, imports, exports, scans, billing, analytics, emails, and support. For privacy or security questions, contact nailwage@gmail.com.
Information we collect
We may collect account information, salon information, technician names and phone numbers, daily work entries, tips, commissions, closeout records, pay-policy records, technician-summary records, card-fee check inputs and results, uploaded or pasted files for import or OCR processing, billing identifiers, support messages, audit logs, device/browser data, and product-usage events.
Sources of information
We collect information from salon owners and authorized users, from technicians when they open or mark scoped links received, from files or scans users choose to upload, from payment and infrastructure providers, and automatically from cookies, logs, analytics, and security tools.
How we use information
We use information to authenticate users, operate accounts, calculate and display records, create exports, process billing, send service emails, run OCR or import features, secure and monitor the service, troubleshoot errors, prevent abuse, improve the product, respond to support requests, and comply with legal obligations.
How information is shared
We do not sell salon data. We share information with service providers that help run NailWage; with the salon owner and authorized account users; with technicians through scoped links the salon owner creates; with payment processors for billing; with advisors or authorities when needed to comply with law, protect rights, prevent fraud, or address security issues; and in connection with a merger, financing, sale, or transfer of the business.
Service providers and analytics
NailWage uses Supabase for data and authentication, Stripe for subscription billing, Resend for email, Sentry for error monitoring, hosting providers, and OCR providers for scan features. Google Analytics loads only on reviewed public pages when configured and after you allow analytics. OCR uploads are processed to extract text or numbers; saved fee-check history stores reviewed numbers and results, not original merchant-statement files.
Cookies and tracking
Cookies and browser storage support login, security and your preferences. Public article views, action clicks and tool usage measurement remain off until you choose Allow. You can change that choice at the bottom of public pages; declining does not restrict features. We honor Global Privacy Control and Do Not Track. If allowed, NailWage receives counts by day, topic, language and usage stage; its count table contains no account or session IDs. A signed-in account is checked transiently to exclude known test accounts and administrators. Google Analytics, when enabled, may use its own cookies; we send only reviewed public paths and events, not names, emails, salon IDs, tokens, dollar amounts, entered content or private-record paths. We do not join Google search queries to individual accounts. Records you choose to save to use the application still need to be processed; aggregate operational counts from those records are separate from your public analytics choice. For referral links with an approved fixed label, counts may also include the campaign and issued-link source, such as an exam article or a salon-for-sale category. Forwarded links retain the old label; it does not identify the referrer or reader. The label is held only in tab memory while you allow analytics and cleared after withdrawal or private-page navigation; it is not joined to accounts, and raw query strings or referrers are not forwarded.
Technician links
Technician summaries, My Earnings pages, and pay-policy receipt pages use scoped bearer links. The links are designed to be hard to guess, marked noindex and no-referrer, and revocable or rotatable by the salon owner. Anyone with a valid link may view the scoped information, so links should be shared carefully.
Retention and deletion
We keep records as reasonably needed to provide the service, maintain account history, preserve finalized closeouts, meet legal obligations, resolve disputes, maintain backups and protect security. Some records may remain in backups or audit logs after deletion or account closure; legal holds may delay deletion. For public article and tool counts, the dashboard reads at most 90 days and older counts are removed when the next measurement is received. These counts have no user ID for tracing an individual event. Google Analytics follows its separately configured service retention. The test-account exclusion list is kept in administration data and deleted with the corresponding account profile.
Security
We use reasonable administrative, technical, and organizational safeguards such as HTTPS, role-based database policies, token scoping, noindex/no-referrer token pages, no-store headers on money-file downloads, audit logging, monitoring, and restricted service-role usage. No internet service is perfectly secure, and users are responsible for protecting passwords, devices, exports, and shared links.
Privacy rights
Depending on your location and applicable law, you may have rights to access, correct, delete, or receive a copy of certain personal information, or to object to certain processing. NailWage does not sell personal information or share it for cross-context behavioral advertising. California privacy laws, including the CCPA, apply only to businesses that meet legal thresholds; even when a law does not require it, we will try to respond to reasonable privacy requests sent to nailwage@gmail.com.
Children, changes, and questions
NailWage is not directed to children and should not be used by anyone under 18. We may update this Privacy Policy as the product, providers, or laws change. Continued use after an update means the updated policy applies. Questions can be sent to nailwage@gmail.com.