Website tracking and consent

Cookie Policy

How MedaStaré uses cookies, local storage, consent technologies and optional analytics, including Contentsquare where enabled.

Effective September 21, 2026 Version 2.0 MedaStaré Inc.

Current position

MedaStaré uses technical storage that may be necessary to deliver, secure and operate the website. MedaStaré does not currently use advertising cookies to build behavioral advertising profiles from private app content.

Contentsquare has been configured by MedaStaré for Full Masking, but a Contentsquare account or configuration alone does not mean that visitors are being tracked. Contentsquare should be treated as active only after the relevant tag or SDK is actually deployed and starts collecting data.

Where applicable law requires prior consent for non-essential analytics or Session Replay, MedaStaré will not intentionally activate those technologies before the required consent choice is available.

1. Scope

This Cookie Policy applies to MedaStaré websites and web-based legal, support or account pages that link to it. It explains the browser-based technologies MedaStaré may use and how visitors can control non-essential technologies.

The MedaStaré mobile application may use SDKs, device identifiers or application storage that are technically different from browser cookies. Mobile-app processing is described primarily in the Privacy Policy, AI Data Processing Notice and Subprocessors page.

2. What cookies and similar technologies are

Cookies are small pieces of information stored by a browser or device and returned during later requests. Similar technologies can include local storage, session storage, SDK storage, pixels, tags and browser identifiers.

These technologies can be used for different purposes, including basic website delivery, security, remembering preferences, maintaining consent choices, measuring performance, understanding navigation or supporting advertising.

The fact that a technology can technically identify a browser or session does not mean that MedaStaré uses it for advertising or attempts to identify a person by name.

3. Technology categories

Category Purpose Consent approach
Strictly necessary Security, network delivery, essential preferences, consent storage, fraud prevention and other functions required to provide the website or a user-requested service. May operate without optional analytics consent where permitted by applicable law because the technology is necessary for the requested service.
Analytics / performance Measure navigation, feature usage, page performance, errors and user-experience patterns. Activated only with the consent or other lawful basis required in the visitor's jurisdiction.
Session Replay / experience analytics Understand navigation and interaction patterns through masked replay or equivalent experience tools. Where legally required, activated only after the required consent. Full Masking is used for Contentsquare under MedaStaré's current configuration.
Advertising / targeted marketing Cross-site or cross-context advertising, ad attribution or behavioral profiling. MedaStaré does not currently use private app content for this purpose. If such technologies are introduced, the Policy and consent controls will be updated before use where required.

4. Strictly necessary technologies

MedaStaré may use or rely on technical storage that is necessary to operate and protect the website. Depending on the page and deployment, this may include:

  • security or anti-abuse controls;
  • network and hosting functionality;
  • temporary session state needed for a requested interaction;
  • language or interface preferences;
  • records of a visitor's cookie or privacy choice; and
  • other technical storage strictly necessary to provide a service the visitor requested.

Necessary technologies are not used by MedaStaré as permission to create unrelated advertising profiles.

Because infrastructure can change, MedaStaré does not invent cookie names or fixed lifetimes for necessary technologies that are not actually present in production. The table in Section 8 is updated when a persistent browser identifier is confirmed in the live website.

5. Analytics and Contentsquare

MedaStaré may use Contentsquare for product analytics, performance analysis and Session Replay once the relevant tag or SDK is deployed.

If enabled, Contentsquare may process technical and interaction information such as page or screen views, clicks or taps, navigation events, URLs, browser or device information, session identifiers and performance signals. Depending on the Contentsquare product configuration, first-party cookies or local-storage items may also be created.

Contentsquare is not considered active merely because MedaStaré has a Contentsquare account or has selected a masking configuration. Data collection begins only after the tracking implementation is technically deployed and permitted to run.

MedaStaré will not intentionally configure Contentsquare to collect passwords, complete payment-card numbers, CVC/security codes, authentication credentials, private messages, private photos, AI prompts, body information or cycle information as visible Session Replay content.

6. Session Replay and Full Masking

MedaStaré's current Contentsquare configuration uses Full Masking. Full Masking is intended to prevent visible page or application content from being reproduced in readable form in Session Replay. Contentsquare's documentation explains that masked text is obscured and images are hidden or blurred depending on the applicable implementation.

Masking is a data-minimization safeguard, not a substitute for consent where consent is legally required. It also does not mean that no technical information is collected; session identifiers, navigation events, page URLs, timing or performance information can still be processed when the analytics tool is active.

MedaStaré does not intend to unmask authentication fields, payment-related information, private account areas, AI prompts or chats, uploaded photos, body or cycle information, or other content that would create unnecessary privacy risk.

If masking rules are changed later, MedaStaré will review the affected pages and data categories before intentionally allowing additional content to become visible in replay.

8. Current cookie and storage list

The table below distinguishes confirmed current/necessary categories from technologies that become active only if their implementation is deployed.

Technology Status Purpose Typical duration / note
Necessary website / consent storage May be active as required by the website or consent manager Security, essential operation and storage of privacy choices. Duration depends on the specific production technology. MedaStaré does not publish an invented cookie name or lifetime before confirming the live implementation.
Contentsquare _cs_id Conditional — only if the Contentsquare web tag is deployed Stores technical user/session information used by Contentsquare analytics. Contentsquare documents a fixed lifetime of approximately 13 months.
Contentsquare _cs_s Conditional — only if the Contentsquare web tag is deployed Stores session information and Session Replay collection state. Approximately 30 minutes, renewed with user activity according to Contentsquare documentation.
Contentsquare _cs_c Conditional — only if the Contentsquare web tag is deployed Stores Contentsquare replay-consent/masking state. Approximately 13 months, renewed when the choice is updated according to Contentsquare documentation.
Other Contentsquare product cookies or local storage Conditional Product Analytics, identity association, session context, sampling or opt-out functionality where those Contentsquare features are enabled. Names and durations depend on the Contentsquare product/configuration. MedaStaré will update this page if those items are confirmed in the live deployment.
Advertising / retargeting cookies Not currently disclosed as active Would be used for advertising, attribution or cross-context profiling if introduced. Not intentionally activated without an updated disclosure and any consent required by applicable law.

Cookie names, lifetimes and provider behavior can change through provider updates. MedaStaré will update this table when a material change is confirmed in production.

9. Third-party services

Third-party services may set or access their own browser storage only where their technology is actually implemented. MedaStaré's current public disclosures distinguish between infrastructure providers, analytics providers and independent platform services.

For provider identities, purposes, processing locations and provider roles, see the Subprocessors page. For personal-data categories and international-transfer information, see the Privacy Policy.

Opening an external provider's website or following a third-party link may cause that provider's own cookies or tracking technologies to operate under the provider's own privacy and cookie policies.

10. Changes to this Policy

MedaStaré may update this Cookie Policy when the website architecture, analytics configuration, consent system or legal requirements change.

If MedaStaré introduces a new non-essential analytics, Session Replay, advertising or attribution technology that requires consent, the consent interface and this Policy will be updated before that technology is intentionally activated where applicable law requires prior consent.

The effective date and version number at the top of this page identify the current published version.

11. Contact

Questions about cookies, analytics, consent or tracking technologies may be sent to support@medastare.com.

For privacy-rights requests, use the Privacy Choices page or review the Privacy Policy.