Required for core platform functionality such as login sessions and form security.
LEGAL & POLICIES
Cookies Policy
Learn how RealNonVoIPUSNumber uses cookies and similar technologies to operate, secure and improve our services.
Cookies at a Glance
Cookies are small pieces of information stored by your browser that help websites remember sessions and protect requests. RealNonVoIPUSNumber uses cookies and similar technologies primarily to:
- Keep users securely signed in to the dashboard
- Protect forms and authenticated requests with CSRF checks
- Maintain essential platform and session functionality
- Remember limited dashboard preferences in browser storage (such as theme)
The public site does not currently ship a marketing analytics cookie suite or a cookie-consent banner for optional trackers.
Helps protect sessions, forms, and account activity through CSRF and session controls.
Clear documentation of the cookies and browser storage actually used by this application.
1. What Are Cookies?
A cookie is a small text file placed on your device by a website. Cookies can be:
- Session cookies — typically removed when the browser session ends
- Persistent cookies — remain until they expire or you delete them
- First-party cookies — set by RealNonVoIPUSNumber for our own domain
- Third-party cookies — set by other domains if you visit or are redirected to their services
2. How We Use Cookies
Based on the current Django application, we use cookies for:
- Authentication and session management after login
- CSRF protection on forms and authenticated front-end requests
- Remember-me session duration when you choose that option at login
- Server-side session data for dashboard features (for example favorites), keyed by the session cookie
Account language preference is stored on your user profile, not as a separate language cookie. Dashboard theme preference uses browser localStorage (see below).
3. Essential Cookies
Essential cookies are required for the service to work. They include the Django
session cookie (sessionid) and the CSRF cookie
(csrftoken). These are not presented as optional toggles
because disabling them breaks sign-in and protected actions.
By Django defaults used in this project, the session cookie is marked HttpOnly (enabled) and SameSite=Lax. Production deployments should also use HTTPS; Secure cookie flags depend on deployment configuration and are not hardcoded as enabled in the current settings file.
4. Functional Cookies / Preferences
We do not set a dedicated marketing or “preferences” browser cookie for language. Functional browser storage used by the dashboard includes theme preference in localStorage and temporary onboarding tour resume data in sessionStorage. Those are not HTTP cookies, but they are similar client-side technologies.
5. Analytics Cookies
The public website templates do not embed a third-party marketing analytics cookie platform. Operational logging (application logs and API request metadata) happens server-side and is described in our Privacy Policy—it is not implemented as a public-site analytics cookie.
6. Security Cookies
The CSRF cookie (csrftoken, SameSite=Lax)
helps ensure state-changing requests originate from our forms and authenticated
front-end code. Session cookies bind your browser to a server-side session used for
authentication and security-sensitive flows (including password-reset challenge
state and staff impersonation session keys when applicable).
7. Third-Party Cookies
Our first-party application cookies are limited to the essential session/CSRF pair above. If you are redirected to an external payment provider page to complete a crypto deposit, that provider may set its own cookies under its own policy. We do not invent or list unverified third-party cookie names here.
The public site may load fonts or other assets from external CDNs; those requests are not the same as our first-party session cookies.
8. Local Storage and Similar Technologies
In addition to cookies, the dashboard may use:
- localStorage key
rnv-dash-theme(and legacyrnv-theme) for light/dark theme - sessionStorage key
rnv-tour-resumeto resume an interrupted onboarding tour
Front-end scripts may read the CSRF cookie value to attach CSRF headers on AJAX calls. They do not store API secrets or passwords in cookies.
9. Cookie Preferences
Because optional marketing/analytics cookies are not loaded by the current public front-end, we do not provide an in-app cookie preference center with on/off switches for non-essential categories. Essential cookies remain required for core operation.
For account preferences such as language and notifications, use dashboard Settings. For browser storage and cookies, use your browser controls.
10. Managing Cookies in Your Browser
You can view, block, or delete cookies through browser settings in Chrome, Firefox, Safari, Edge, and similar browsers. Exact menu labels vary by browser version. Blocking essential cookies may prevent login, dashboard use, and secure form submission.
11. What Happens If Cookies Are Disabled?
- Essential cookies disabled — sign-in, session continuity, and CSRF-protected actions are likely to fail.
- Browser storage disabled — dashboard theme and tour resume helpers may not persist; core ordering can still work if cookies remain available.
- Optional marketing cookies — not applicable to the current public front-end stack.
12. Cookie Retention
- Session cookie — browser session when Remember me is off; longer-lived (about 30 days) when Remember me is on at login
- CSRF cookie — persistent under Django’s default CSRF cookie lifetime (commonly about one year)
- localStorage theme — until cleared
- sessionStorage tour resume — until the tab/session ends or is cleared
Cookie & Storage Details
Names and purposes below reflect the current RealNonVoIPUSNumber Django application.
| Cookie / Technology | Purpose | Category | Typical Duration |
|---|---|---|---|
sessionid |
Keeps you signed in, stores server-side session state for dashboard features (such as favorites and security flows), and supports “Remember me” when selected at login. | Essential | Browser session by default when Remember me is off; up to about 30 days when Remember me is selected. Otherwise follows Django’s configured session lifetime. |
csrftoken |
Protects forms and authenticated AJAX requests against cross-site request forgery (CSRF). Readable by our front-end scripts so they can send a matching CSRF header. | Essential / Security | Persistent (Django default is typically about one year). |
rnv-dash-theme (localStorage) |
Remembers light/dark theme preference on the signed-in dashboard. | Functional (browser storage) | Until cleared by you or the browser. |
rnv-tour-resume (sessionStorage) |
Temporarily helps resume an interrupted onboarding tour in the dashboard. | Functional (browser storage) | Current browser tab/session. |
sessionid
Purpose: Keeps you signed in, stores server-side session state for dashboard features (such as favorites and security flows), and supports “Remember me” when selected at login.
Category: Essential
Duration: Browser session by default when Remember me is off; up to about 30 days when Remember me is selected. Otherwise follows Django’s configured session lifetime.
csrftoken
Purpose: Protects forms and authenticated AJAX requests against cross-site request forgery (CSRF). Readable by our front-end scripts so they can send a matching CSRF header.
Category: Essential / Security
Duration: Persistent (Django default is typically about one year).
rnv-dash-theme (localStorage)
Purpose: Remembers light/dark theme preference on the signed-in dashboard.
Category: Functional (browser storage)
Duration: Until cleared by you or the browser.
rnv-tour-resume (sessionStorage)
Purpose: Temporarily helps resume an interrupted onboarding tour in the dashboard.
Category: Functional (browser storage)
Duration: Current browser tab/session.
13. Cookies and Your Privacy
Cookies and browser storage are part of the broader information practices described in our Privacy Policy.
14. Changes to This Policy
We may update this Cookies Policy when platform behavior changes. Material updates will be reflected by revising the Last Updated date (currently October 01, 2026).
15. Contact Us
Questions about cookies or similar technologies can be sent via the Contact page or email [email protected] .
Frequently Asked Questions
Answers matched to the cookies and storage used by this application.
Cookies are small pieces of data a website stores in your browser. They help keep you signed in, protect forms, and remember limited session-related information.
We use essential cookies so authentication, dashboard sessions, and CSRF protection work reliably. We do not currently use separate marketing or advertising tracking cookies on the public site.
No. The session and CSRF cookies are required for secure sign-in and form protection. Without them, login and many dashboard actions will not work correctly.
You can block or delete cookies in your browser settings. Disabling essential cookies will typically prevent signing in and using the dashboard. Optional marketing cookies are not part of the current public front-end, so there is no separate “optional cookies” toggle on this site.
Your account data remains on our servers, but you may be unable to stay signed in or submit protected forms until essential cookies are allowed again.
The public templates do not embed a third-party marketing analytics cookie suite. We do keep server-side application and API request logs for security and reliability, which are not browser cookies.
There is no in-app cookie preference center for optional categories because optional marketing cookies are not loaded. Manage cookies through your browser controls, and use dashboard settings for account preferences such as language (stored on your account, not as a language cookie).
Email [email protected] or use the Contact page. You can also review our Privacy Policy for broader information handling.
Questions about cookies?
If you have questions about how cookies or similar technologies are used on the platform, contact our support team.