Cookie Policy — DoifyNow
Read DoifyNow Cookie Policy to understand our cookie usage, analytics approach, and cookie management options.
1. Scope
This policy covers cookies and browser storage used by the DoifyNow public site, account sign-in, and account page. The site stores language, consent, and optional getting-started progress needed to provide the requested experience. Getting-started progress contains only the selected product category, preferred capability, and completed guide steps. These values stay in the browser and do not provide a DoifyNow account or authenticate a user.
2. Preference storage
DoifyNow uses localStorage to remember the selected language and, when analytics is enabled, the
analytics consent choice. These values do not authenticate a user. Analytics settings remain available in the site
footer so the choice can be changed or revoked.
3. Account and authentication storage
After successful sign-in, the browser stores the opaque AuthAPI bearer token in per-tab
sessionStorage under a DoifyNow-specific key. The current account identity and session expiry are kept
in application memory. The password is sent to the same-origin /api sign-in endpoint and is not stored
by the Angular client. Signing out, or an unauthorized, invalid, or expired session response, removes the browser
token. Temporary offline, timeout, or server failures retain the token but discard stale in-memory session data
until it can be revalidated.
Scoped AuthAPI X-Api-Key service keys are for machine clients, cannot authenticate a browser session,
and are not stored by this browser client.
4. Analytics
When runtime analytics is enabled, privacy-focused Umami analytics is loaded only after consent. Revoking consent removes the analytics script from the page and stops further site tracking by this client.
5. Product sites
Product-owned sites may use different technologies. Their cookie and privacy notices apply after you follow a product link.
6. Contact
Questions: [email protected]
Related documents: Privacy Policy, Terms of Service.
Theme, demo, and sign-in choices
The selected System, Light, or Dark theme is stored in localStorage under theme. System
follows the device preference. Language, theme, and guide preferences remain until you change them or clear site
storage. If storage is blocked, choices work in memory for the current page session.
The demo contains synthetic sample records and changes stored only in this tab's sessionStorage under
doifynow-demo-session-v1. Reset restores the samples; Exit clears demo state. Closing the tab normally
ends this storage. Demo interactions do not create an account or process payments. Avoid entering personal information
in the demo.
When social sign-in is enabled, AuthAPI uses authentication and callback cookies to complete the requested sign-in. Production cookies use Secure, HttpOnly, and SameSite=Lax attributes and are restricted to the host. Google or Apple sign-in takes you to that provider, whose own privacy and storage policies also apply. These necessary authentication cookies are separate from optional analytics consent.
You can decline optional analytics without losing site, theme, demo, or sign-in access. Consent is remembered until changed or site storage is cleared. Use Analytics settings in the footer to revisit the choice. Revocation stops subsequent tracking; it does not erase information already sent. No password or form contents are sent to site analytics.
Development stages describe the portfolio direction. Features, access, and availability vary by product; a listing does not mean every planned feature is live.