Legal & privacy
A small, honest cookie policy.
CloudInvoice uses essential browser storage to keep a signed-in session working and remembers a display preference when you choose one. This page describes the behavior present in the application, not a generic tracking-policy template.
Summary
No advertising cookie is required to use CloudInvoice.
Last updated: August 1, 2026. Revisit this policy before enabling analytics, advertising, or any new embedded third-party tool.
What we use
Essential session support and a local theme preference
Authentication session cookie
Set by the authentication flow
Lets the application recognize a signed-in user and keep the account session available across requests.
Yes
Session configuration is set to a 14-day maximum in the application. Browser behavior can vary by security settings and sign-out activity.
Theme preference
Browser local storage, not a cookie
Stores whether you selected the light or dark interface so the dashboard can preserve that preference on your device.
Yes, for preference
Until you clear browser storage, change the theme, or use browser controls that remove it.
What happens outside CloudInvoice
Payment and browser controls
Stripe Checkout
A card-paying client may be taken to a Stripe-hosted checkout experience. Stripe can use cookies or similar technologies under its own notice and browser controls. CloudInvoice does not control Stripe’s domain-level settings.
Blocking essential storage
You can block or clear cookies in browser settings, but doing so may prevent sign-in from working or sign you out. Clearing site storage resets your saved display preference.
Future changes
New analytics, fraud prevention, chat, advertising, or embedded tools can introduce additional storage. The operator must assess consent requirements and update this page before making those tools live.
Your choices
How to manage cookies and local storage
Use your browser’s site-data controls to inspect, block, or remove CloudInvoice cookies and local storage. You can generally control cookies per site, use a private-browsing window, or clear stored data when ending a session on a shared device.
Signing out ends the active product session. For account, invoice, or privacy questions, use the contact process published by the service operator before public launch. See the Privacy Policy for the broader description of data processing and the Security overview for product-level safeguards.