How Licensure Log handles your data.
Last updated August 21, 2026.
Who operates Licensure Log
Routinely Solutions LLC, operating in California, owns and operates Licensure Log and is responsible for the product data practices described here.
Information you provide
We store the email associated with your authentication account, account and profile details, employers and projects, AXP entries and classifications, private notes, shareable summaries, goals, approved-hour snapshots, imports, reports, support requests, product feedback, and your optional marketing-email preference and consent timestamps. You choose what to enter and what report-safe material to export or share.
Information created by the service
We create authentication records, one-time Catch-Up order and payment identifiers, limited error logs, and content-free product events such as onboarding completion, export action, checkout outcome, upload size and file extension, import fallback, review, commitment, support, and refund outcomes. Spreadsheet filenames, row text, document contents, private notes, and account email addresses are excluded from product analytics.
How information is used
We use information to authenticate your account, provide daily recordkeeping and progress calculations, generate the reports you request, process imports, provide billing, respond to support and feedback, prevent abuse, diagnose errors, measure product use, and improve the product. We use the account email for necessary account and service messages. We use it for product tips, release announcements, or promotional messages only while your optional marketing preference is enabled.
Processors and service providers
Supabase provides authentication, database, and temporary import storage. Vercel hosts the application and provides public analytics. PostHog receives content-free lifecycle events for product measurement. Stripe processes the one-time Easy Catch-Up payment and refunds; Licensure Log stores billing identifiers and order state, not full card numbers. OpenAI may process only the minimum text from unresolved import rows when AI fallback is enabled. Google may process account information if you choose Google sign-in. Any future email-delivery provider will receive only the information needed to send and manage the requested messages, and this policy will be updated when that provider is selected.
Email choices
Account, security, billing, support, and material service-change messages may be necessary to operate your account. Marketing email is separate and optional. New and existing users default to not subscribed unless they affirmatively enable the preference during onboarding or in Settings. Turning it off records the change and stops future marketing sends, subject to reasonable processing time and any legally required suppression record.
AI boundaries
AI is not used for ongoing reports. During Easy Catch-Up, deterministic parsing runs first and only unresolved work text may be sent for classification. Entire files and private entry notes are not sent. AI output is optional, editable, and not an official classification or licensing decision.
Support and feedback
Support and feedback are stored with a limited safe context such as the route and whether you were signed in. Lifecycle feedback is deduplicated. Contact consent is stored with feedback; the development queue does not reveal an email as a contact path when consent was not given. Do not paste private entry notes into support or feedback unless necessary.
Retention and your controls
We retain account data while the account is active and as needed for security. Original Catch-Up uploads are deleted after processing and staged row payloads are removed after commitment. A change-of-mind refund within 14 days requires Refund and close account: Stripe is refunded first, then stored import objects and the authentication account are deleted. Minimal anonymized billing records remain for financial, dispute, and legal obligations. If the refund fails, deletion does not occur. Backups and security logs may take additional time to expire.
Security and sharing
Account data is protected by authentication, database grants, and row-level access controls. No online service can promise absolute security. We do not sell your experience record. We disclose information to service providers for the purposes above, when you direct us to share an export, or when law requires it.
NCARB boundary
Licensure Log is not affiliated with or endorsed by NCARB. My NCARB remains the official system of record for AXP submissions, approvals, and current policy decisions.
Privacy questions and requests
Use the Contact page or email support@licensurelog.com.