01Overview
Cookies should serve a defined purpose.
Signaturesi may use cookies, browser storage and similar technologies to maintain secure sessions, remember selected settings, protect accounts and understand product performance.
Optional technologies should remain disabled until the user provides consent where consent is required.
02What cookies are
Cookies are small pieces of browser data.
A cookie is a small text value stored by a browser when a website is visited. Cookies can remember login state, preferences, consent choices and other limited information.
Similar technologies include local storage, session storage, device identifiers and secure authentication tokens.
Small data stored by the browser and sent with relevant website requests.
Browser-based storage that may remain until it is removed.
Temporary browser storage generally removed when the tab or session ends.
A limited credential used to maintain or verify authenticated access.
03Technologies Signaturesi may use
Different technologies support different functions.
| Technology | Possible use | Typical status |
|---|---|---|
| Secure session cookie | Keep a user signed in | Essential |
| Local storage | Remember appearance or interface preferences | Functional |
| Security token | Protect account sessions and requests | Essential |
| Analytics identifier | Measure aggregate product usage | Optional |
| Consent record | Remember cookie choices | Essential or functional |
04Essential cookies and storage
Some technologies are required for core functionality.
Essential technologies may be used without optional consent where legally permitted because the service cannot operate securely without them.
Maintain a secure signed-in session.
Detect suspicious login or session behavior.
Reduce forged or unauthorized requests.
Remember the privacy choices selected by a user.
Blocking essential cookies may prevent login, account recovery, security controls or core product functions from operating correctly.
05Preference technologies
Preferences improve continuity across visits.
Functional storage may remember choices that do not require a user to sign in again or reconfigure the interface on every visit.
Light mode, dark mode or system appearance choice.
Selected website or product language.
Sidebar, panel or table-of-contents state.
Reduced motion or interface preference settings.
06Analytics
Analytics should measure products without unnecessary tracking.
Signaturesi may use optional analytics to understand page performance, feature reliability and aggregate usage patterns.
Possible analytics information
- Page visits and navigation paths.
- Browser type and general device category.
- Feature usage and interaction counts.
- Page loading and performance measurements.
- Approximate region rather than precise location.
- Error and crash events.
Analytics should avoid collecting private NEO prompts, Bean messages, uploaded files or sensitive account content.
07Advertising technologies
Signaturesi does not currently need advertising trackers.
This draft does not assume the use of targeted advertising cookies, cross-site profiling or advertising pixels.
If advertising technologies are added later, this policy, the consent interface and user controls must be updated before deployment.
08Authentication and Bean ID
Account sessions require secure handling.
Bean ID may use secure session cookies or tokens to authenticate users across supported Signaturesi products.
Credentials are verified through the authentication system.
A limited session token may be stored securely.
Protected actions require a valid authenticated session.
Tokens should expire, rotate or be revoked when needed.
Authentication tokens should not be exposed through public code, analytics logs or third-party scripts.
09Local storage and product settings
Browser storage should not become a hidden database.
Signaturesi may use local storage for lightweight interface preferences or temporary product state.
- Appearance preferences.
- Language selection.
- Collapsed or expanded interface state.
- Non-sensitive draft interface state.
- Plain-text passwords.
- Private service keys.
- Full private messages or AI memory.
- Long-lived administrative credentials.
10Third-party technologies
External services may set their own browser data.
Some features may rely on external providers for authentication, payments, embedded media, analytics or customer support.
May maintain secure sessions or account verification.
May store checkout or fraud-prevention information.
Video or social embeds may use third-party storage.
Optional measurement providers may use identifiers.
Signaturesi should avoid loading optional third-party scripts before the user has made an applicable consent choice.
11Retention periods
Browser data should not remain longer than needed.
Used to maintain authenticated access.
Used to remember selected interface options.
Used to remember privacy choices.
Must be disclosed after provider selection.
12Your cookie controls
Optional choices should remain reversible.
A production consent system should allow users to review and update optional cookie choices without deleting their account.
Required for core security and account features.
Remembers selected interface settings.
Measures aggregate usage and performance.
These controls currently demonstrate appearance only. Connect them to a real consent-management system before production use.
13Browser controls
Browsers also provide storage controls.
Most browsers allow users to view, block or delete cookies and site storage through browser settings.
- Block cookies for all sites or selected websites.
- Delete existing cookies and local storage.
- Clear data when the browser closes.
- Disable third-party cookies.
- Use private or incognito browsing modes.
Removing essential session data may sign a user out or reset product preferences.
14Consent and regional requirements
Consent requirements depend on location and technology.
Some countries require prior consent before optional analytics, advertising or similar technologies are used.
Signaturesi should display a consent interface where legally required and should avoid treating silence, inactivity or continued browsing as consent where stronger consent is required.
15Changes to this policy
This policy may change with the technology stack.
Signaturesi may update this Cookie Policy when providers, storage methods, consent tools or product features change.
The effective date and version shown at the top of this page should be updated whenever material changes occur.
16Contact
Questions about cookies and storage.
Contact Signaturesi through a verified and actively monitored privacy address.
Signaturesi Privacy
Cookies and browser storage
Draft contact
This page is a structured website draft and does not replace professional legal review.