Privacy Policy

1. Who we are and our role

MedaStaré Inc. is a United States company and, where applicable privacy law uses these terms, acts as the controller, business or personal information controller for personal data processed through the MedaStaré website, mobile applications and related services, except where another party is clearly identified as an independent controller.

Our privacy contact is support@medastare.com. Where applicable law requires a separate representative, data protection officer, local contact or additional corporate information, MedaStaré will make the required details available through the Legal Notice, a regional supplement or another legally permitted notice.

Some third parties, including Apple, Google and certain external platforms, may act as independent controllers for processing they determine themselves. Their own privacy terms apply to that independent processing.

2. Scope and how to read this Policy

This Policy applies to the MedaStaré public website, mobile application, account registration, authentication, subscriptions, MedAI and other AI features, wardrobe and style tools, social and creator features, MedArena and challenge-related product functions, customer support, creator or agency communications, partnership inquiries, and any MedaStaré feature or campaign that links to this Policy.

Some features are released gradually, may differ by country, operating system, account type or app version, and may not be available to every user. A feature-specific notice may provide additional information at the point of collection. If a feature-specific notice is more specific than this Policy, that notice applies to the relevant processing to the extent permitted by law.

This Policy does not govern independent third-party websites, apps, stores or services merely because MedaStaré links to them.

3. Personal data we process

Account, profile and authentication data

• Name, email address, date of birth or age-related information, username, account identifier and profile information you provide.
• Authentication status, internal user ID, session or token information and login/security events needed to operate and protect an account.
• Identifiers and limited profile information received when you choose Sign in with Apple, Google sign-in or another supported authentication method.
• Verification events associated with email, OTP or other authentication flows where used.

Style, wardrobe and personalization data

• Style, color, fit, sizing, silhouette, mood, occasion and preference information.
• Wardrobe items, garment descriptions, wardrobe photographs, saved outfits, favorites, notes, StyleTrack history and related organization data.
• Recommendation context and preference signals generated from prior selections or interactions where personalization is enabled.
• Personalization choices, consent state and related settings.

Photos, video and generated media

• Photos or videos you select or capture for wardrobe, outfit, appearance, body, face, beauty, nail, creator, StarDay, MedArena or other visual features.
• Reference images and AI-generated or edited images associated with your account where the feature saves them.
• Technical metadata needed to store, retrieve, secure or moderate media, such as storage paths, signed-link information, upload status and moderation results.

MedAI, prompt, chat and voice data

• Prompts, chat messages, conversation context, assistant responses, feedback and generated outputs.
• Relevant account, style, wardrobe or feature context sent with a request when needed to provide the requested AI function.
• Voice input when a voice feature is used. MedaStaré's current voice implementation does not intentionally retain raw audio as a stored account asset; transcripts may be retained under the same rules as other chat messages.

Social, creator and community data

• Public or limited-audience username, profile information, posts, StarDay content, Star Card sharing, follow relationships, blocks, reports, reactions and other social interactions where enabled.
• StaréMatch compatibility inputs and match-state information used to connect eligible users based on product-defined style or mood criteria. StaréMatch is not designed as a dating service; communication options may be limited by product design.
• Creator application information, social handles, portfolio or screenshots voluntarily submitted for review.
• MedArena entries, leaderboard or scoring data, eligibility information, moderation status, fraud or abuse signals and reward-related records where applicable.

Location and weather context

• Coarse location or city-level information used for weather-aware styling or location-dependent features where enabled.
• The current technical configuration may store an approximately one-kilometer-level location representation, city name and country code rather than a precise continuous location history.
• Weather requests may involve MET Norway Locationforecast, and city/location resolution may involve OpenStreetMap Nominatim or another disclosed provider.

Subscription, transaction and entitlement data

• Subscription tier, entitlement status, expiration information, restoration status and limited store transaction identifiers needed to verify paid access.
• Refund, revocation or cancellation status made available by the applicable store.
• For Apple purchases, verified App Store transaction information. For Google Play purchases, corresponding Google Play information is processed when Google Play billing is enabled.
• MedaStaré does not receive full payment card details from Apple or Google for store-processed in-app subscriptions.

Creator payout and Stripe Connect data

• If you participate in an eligible creator, StarGift or payout program, MedaStaré may create or connect a Stripe Connect account so Stripe can support identity verification, payout onboarding, financial-account setup and transfers.
• Depending on country and Stripe requirements, Stripe may ask for legal name, date of birth, address, tax or business information, government-issued identification, identity-verification information and bank-account or eligible payout-card details.
• Creator onboarding is presented through Stripe Connect components. Sensitive payout and identity information entered into Stripe's onboarding flow is transmitted to Stripe for processing and verification.
• MedaStaré may receive or access the information reasonably necessary to operate the creator program, including a Stripe connected-account identifier, country, business or individual account status, verification requirements or status, enabled capabilities, payout status, transfer records, balance or payout information, and limited or masked financial-account metadata made available by Stripe.
• MedaStaré is designed not to store complete payment-card numbers, CVC/security codes, online-banking passwords or other full financial credentials submitted through Stripe Connect in MedaStaré's own application database. Where Stripe returns limited identifiers such as a bank or card type, institution name, last digits or account status, MedaStaré may process that limited information for payout support, reconciliation, fraud prevention and legal compliance.

Device, network, log and diagnostic data

• Device type, operating system, app version, locale, browser, network and technical request information.
• IP address, request identifiers, timestamps, server/runtime logs and security or abuse-prevention events where generated by our infrastructure.
• Feature interaction, performance, error and diagnostic data where the relevant analytics or monitoring tool is enabled.

Notifications, support and business communications

• In-app notification records and notification preferences. Push-notification tokens are processed only where a push provider and push notifications are enabled.
• Support messages, privacy requests, bug reports, feedback and information you voluntarily submit to us.
• Business, creator, agency, investor, vendor or partnership contact information and correspondence.

4. Sensitive and higher-risk data

Certain MedaStaré features can involve information that is sensitive under some laws or that deserves heightened protection because of its context.

• Face and body imagery. Photos of a face or body may reveal sensitive characteristics. The current MedaStaré service is not designed to identify or authenticate a user through biometric identity recognition. If MedaStaré ever introduces biometric identification or authentication, it will provide a separate notice and obtain any permission required by law before that use.
• Body and fit information. Measurements, proportions or body-shape styling inputs may be used to provide styling or fit-related functionality. They are not used by MedaStaré for cross-context behavioral advertising.
• Cycle context. Where the cycle feature is enabled, the current implementation may store limited day-state or feature flags rather than a full menstrual calendar. If the information qualifies as health or sensitive data under applicable law, MedaStaré relies on the legally required basis, including explicit consent where required. Cycle-related information is not used for advertising.
• Location. MedaStaré is designed to use coarse or city-level location for weather-aware functions rather than continuous precise tracking unless a feature clearly states otherwise.
• Private AI content. Prompts, chats, private photos and related outputs may contain sensitive details because users choose what to submit. Users should avoid sending information that is unnecessary for the requested feature.

MedaStaré does not ask users to upload medical records and does not provide medical diagnosis, treatment or emergency services.

5. How we obtain data

We obtain personal data from the following sources:

• Directly from you, including registration information, preferences, uploaded content, prompts, support messages and creator or business submissions.
• From your use of MedaStaré, including feature interactions, social activity, entitlement state, security events and technical logs.
• From device permissions you choose to grant, such as camera, photo, microphone, location or notification permissions.
• From Apple, Google and other enabled platform services, including authentication identifiers and store transaction or entitlement information.
• From processors and service providers that operate hosting, authentication, AI, moderation, analytics, diagnostics, weather, security or similar functions for MedaStaré.
• From public or third-party sources you direct us to use in a creator, business or product feature, subject to the feature's notice and applicable law.

Installing MedaStaré alone does not give us unrestricted access to your photo library, microphone, contacts or precise location. Device-level access depends on the permission model of the operating system and the feature you choose to use.

6. Why we process data

Where we rely on consent, you may withdraw it for future processing. Withdrawal does not make earlier lawful processing unlawful. If a feature cannot function without the information that is strictly necessary to perform it, withdrawing or refusing that processing may make that feature unavailable without affecting unrelated features.

7. AI processing and automated systems

MedaStaré uses AI-assisted systems for conversational assistance, style guidance, wardrobe combinations, visual analysis, creative generation or editing, voice interaction, 3D-related functions and other features. Current or planned production providers reflected in MedaStaré's technical inventory include OpenAI, Google Gemini, Kling AI and Meshy. Provider availability can change, and the current provider list is maintained on the AI Data Processing and Subprocessors pages.

What may be sent to an AI provider

Depending on the feature, a request may include the prompt, selected image or video, selected wardrobe information, style preferences, body or beauty context, limited cycle context, prior conversation context, or other data reasonably necessary to return the requested result. MedaStaré does not intentionally send unrelated account information to an AI provider merely because it exists in your account.

Consent and controls

MedaStaré maintains consent-state records for certain personalization, body-data or AI-related choices. Where applicable law requires consent before an optional external transfer or sensitive processing, MedaStaré will present the relevant choice before that processing. Consent records may include the consent version, timestamp, provider or data-category information where implemented.

Retention and model training

MedaStaré's own current technical implementation does not apply an automatic expiration period to every stored prompt or chat thread. Unless you delete content where a deletion control is available, a shorter product rule applies, or your account is deleted, prompts and chat history may remain associated with the account. Provider-side retention and training practices depend on the provider, API plan, contract and region; MedaStaré does not represent an unverified provider setting as a guarantee. The AI Data Processing page will state the provider-specific information MedaStaré has verified.

MedaStaré does not use private account content to train a generally available MedaStaré model without a separate affirmative choice. This statement does not override the independent terms of an external provider; provider-specific contractual and technical controls must be considered separately.

Automated outputs and human judgment

• Fashion, beauty, wardrobe and conversational AI outputs are informational and may be incomplete, inaccurate, biased or unsuitable.
• MedaStaré does not rely on fashion or beauty recommendations alone to make a decision that has a legal or similarly significant effect on a user.
• Community moderation, fraud detection, eligibility checks, ranking or challenge administration may use automated signals. Where a competition or reward is involved, the applicable Official Rules explain the selection method, human review, disqualification grounds and other controlling terms.
• Google Cloud Video Intelligence or other moderation tools may assist with content review. Automated provider output does not necessarily result in automatic publication or final enforcement; human review may be used according to the feature's moderation process.

8. Social, public and competition features

Some MedaStaré features are designed for interaction with other users. Depending on the feature and your choices, your username, profile, posts, StarDay content, Star Cards, MedArena entries, leaderboard position or other submitted content may be visible to other users or the public.

• Public content is not private. Do not post information you do not want the intended audience to see.
• Copies outside MedaStaré. Other users may capture, download, quote or share content that was visible to them. MedaStaré cannot guarantee deletion of copies created outside systems we control.
• Moderation. Reports, blocks, automated safety tools and human review may be used to enforce community rules, protect users and investigate abuse.
• StaréMatch. Match creation may use style, mood and other product-defined compatibility inputs. The feature is designed for user connection around MedaStaré interests rather than dating. Product rules may restrict the form of messages available after a match.
• MedArena and challenges. Entries, scores, eligibility, ranking and winner-related records may be retained as necessary to administer a challenge, investigate fraud, resolve disputes, comply with Official Rules and meet legal or tax obligations.

Account deletion may remove, anonymize or retain limited competition, moderation or audit records depending on the nature of the record, the applicable Official Rules and legal obligations.

9. Device permissions and user controls

• Photos and camera. Requested when you select or capture media for a feature. Where supported, system pickers may be used so you can choose specific media rather than grant broad library access.
• Microphone. Requested when you start a voice feature. Raw audio is not intentionally stored by MedaStaré as a persistent account file in the current voice implementation, although audio must be transmitted to the active voice provider to process the live request. Transcripts may be stored as chat content.
• Location. Used for weather-aware or location-dependent features where enabled. The current design uses coarse location/city information rather than continuous precise tracking. You may be able to disable location or use a city-based alternative depending on the feature.
• Notifications. Requested in context where push notifications are enabled. In-app notifications may exist independently of push permissions.
• Personalization and AI choices. Relevant account settings may allow you to change or withdraw optional personalization or data-sharing choices for future processing.

Denying an optional device permission does not prevent unrelated MedaStaré features from operating.

10. Analytics, diagnostics and session replay

MedaStaré may use limited analytics, diagnostics, performance monitoring or session-experience tools to understand whether the website or application works correctly, identify errors, improve navigation and measure feature performance.

Where Contentsquare session analytics or Session Replay is enabled, MedaStaré configures masking controls intended to reduce collection of visible personal content. MedaStaré's current Contentsquare setup is configured for full masking. Contentsquare may still process technical and interaction information such as page or screen views, taps/clicks, navigation events, device/browser information, session identifiers, URLs and performance signals, subject to the configuration in effect.

MedaStaré does not intentionally use session replay to read passwords, payment-card details, private messages, private photos, prompts, body information or cycle information. Masking and suppression are safeguards, not a reason to place sensitive data in analytics. MedaStaré will configure nonessential website analytics or session capture to respect consent requirements where applicable.

Server and platform logging can exist independently of optional analytics. In the current technical environment, Vercel runtime logs have a short retention window, while Google Cloud platform and management logs may have longer provider-defined retention periods for security and administration.

11. When data may be disclosed

MedaStaré does not disclose personal data simply because another company requests it. We disclose or make data available only when reasonably necessary for the relevant purpose, subject to applicable law, contract and access controls.

Providers that act on MedaStaré's behalf are expected to process data for authorized purposes and provide protections appropriate to the service and applicable law. Some providers may act as independent controllers for specific processing. See the Subprocessors page for our maintained provider disclosures.

In a merger, acquisition, financing, reorganization, bankruptcy, sale of assets or similar transaction, relevant data may be disclosed subject to applicable law and appropriate confidentiality protections. Where legally required, we will provide notice before personal data becomes subject to materially different privacy practices.

12. No sale or cross-context advertising of private content

MedaStaré does not sell personal data for money. MedaStaré does not use or disclose private photos, wardrobe content, prompts, chats, body inputs, beauty inputs or cycle information for cross-context behavioral advertising, and does not authorize advertising networks to build advertising profiles from those categories.

If MedaStaré later introduces processing that constitutes a "sale," "sharing," targeted advertising or a similar regulated activity under applicable law, MedaStaré will update its disclosures and provide any required opt-out mechanism before that processing begins. Where legally required, recognized browser or device-based opt-out preference signals will be honored for processing to which they apply.

13. International data transfers and processing locations

MedaStaré is based in the United States and serves users internationally. Personal data may therefore be processed in the United States and other countries where MedaStaré or its service providers operate. Those countries may have data-protection rules that differ from those in your country.

Current primary technical locations

Where applicable law requires a transfer mechanism, MedaStaré will use an available lawful mechanism, such as an adequacy mechanism, approved contractual clauses, standard contractual clauses, recognized certification or another legally valid safeguard. Provider and region information can change as infrastructure changes; material changes will be reflected in our maintained disclosures.

14. Retention and deletion

MedaStaré does not apply one retention period to every category. We consider the purpose of processing, the nature and sensitivity of the data, account status, user choices, security needs, dispute and fraud risk, store and accounting requirements, applicable limitation periods and legal obligations.

Deletion does not require removal of data that MedaStaré must retain by law, needs to maintain security or prevent abuse, needs to establish, exercise or defend legal claims, is required to administer an unresolved transaction or competition, or has been irreversibly anonymized so that it no longer identifies a person.

Where a provider retains deleted data temporarily in a recovery, soft-delete, security or legal-compliance layer, MedaStaré will not use that retained copy for ordinary product purposes and will allow it to expire or be deleted according to the applicable provider configuration and law.

15. Security and access controls

MedaStaré uses administrative, technical and organizational measures designed to protect personal data against unauthorized access, alteration, disclosure or destruction. Controls vary by system and may include encrypted connections, provider encryption at rest, private storage, time-limited media access links, server-side secrets, role-based administrative access, authentication controls, audit logs, rate limiting, moderation and abuse controls.

Administrative access is restricted by role. The current system defines separate roles such as super administrator, moderation, trust and safety, rewards, support, analyst and read-only roles so that operational access can be limited according to function.

Security is an ongoing process rather than a guarantee. No internet or storage system can be promised to be completely secure. MedaStaré may change security controls as threats, infrastructure and product architecture evolve. A description of our public security posture is available on the Security page.

Users are responsible for protecting their account credentials and should contact support promptly if they believe an account has been compromised.

16. Your privacy rights and requests

Depending on where you live, the law that applies and the nature of the processing, you may have rights to:

• receive information about personal-data processing;
• confirm whether MedaStaré processes your data and obtain access to eligible data;
• correct inaccurate or incomplete data;
• request deletion or erasure, subject to legal exceptions;
• restrict or object to certain processing;
• withdraw consent for future processing where consent is the legal basis;
• receive eligible data in a portable format where required by law;
• opt out of regulated sale, sharing or targeted advertising where applicable;
• limit certain uses of sensitive personal information where applicable;
• request information or review concerning certain automated decisions where applicable;
• appeal a denied privacy request where applicable; and
• complain to a competent regulator or supervisory authority.

How to submit a request

Account deletion can be initiated through the account settings described below. Other privacy requests may be submitted through the Privacy Choices page or by emailing support@medastare.com. MedaStaré may request information reasonably necessary to verify identity, protect the account and confirm authority to act.

Privacy requests are not all fully automated. MedaStaré may process access, portability, correction, objection or other rights requests manually through support where an in-app tool is not available.

We will respond within the period required by applicable law. If the law permits an extension because of complexity or volume, we may use it and provide the required notice. Rights are subject to exceptions that protect other users, confidential information, security, fraud prevention, legal obligations and legal claims.

Where applicable law allows an authorized agent to act for you, we may require proof of authorization and may also verify your identity directly where permitted.

MedaStaré will not unlawfully discriminate against a user for exercising a privacy right.

17. Regional information

European Economic Area and Italy

For processing subject to the GDPR, MedaStaré relies on one or more lawful bases such as performance of a contract, consent, explicit consent for special-category data where required, legitimate interests, compliance with legal obligations and establishment or defense of legal claims. Users may have rights of access, rectification, erasure, restriction, portability, objection and withdrawal of consent, and may complain to a competent supervisory authority, including the authority in the user's Member State. Where a transfer outside the EEA requires safeguards, MedaStaré will use an available lawful transfer mechanism.

Türkiye

Where Türkiye's Personal Data Protection Law No. 6698 (KVKK) applies, data subjects may have rights to learn whether personal data is processed, request information, learn the purpose of processing and recipients, request correction, request deletion or destruction where conditions are met, request notification of certain corrections or deletions to recipients, object to an adverse result produced solely through automated analysis, and claim compensation where legally available. MedaStaré may require a request to be submitted using a method that satisfies applicable KVKK procedural rules. Cross-border transfers are handled using a mechanism permitted under applicable Turkish law.

Brazil

Where the LGPD applies, users may have rights to confirmation of processing, access, correction, anonymization/blocking/deletion of unnecessary or unlawful data, portability where regulated, information about data sharing, withdrawal of consent, deletion of consent-based data subject to legal exceptions, objection where applicable, and review or information regarding certain automated decisions. Complaints may be made to the ANPD after using the controller's request channel as required by applicable procedure.

United Arab Emirates

Where the UAE Federal Personal Data Protection Law applies, users may have applicable rights concerning information, access, correction, restriction or stopping of processing, portability, objection to certain automated processing and withdrawal of consent, subject to statutory conditions and exceptions. Cross-border processing will be handled according to applicable UAE requirements.

Singapore

Where Singapore's PDPA applies, MedaStaré provides notice of purposes, applies protection and retention controls, and supports applicable rights such as access and correction. A user may withdraw consent subject to reasonable notice and lawful consequences. Cross-border transfers are handled subject to the transfer-limitation requirements that apply to the relevant processing.

Philippines

Where the Philippine Data Privacy Act applies, users may have rights to be informed, object, access, correct or rectify, request erasure or blocking, obtain data portability where applicable, claim damages where legally available and lodge a complaint with the National Privacy Commission, subject to lawful limitations.

United States

Residents of certain U.S. states may have rights to know/access, correct, delete, obtain a portable copy, opt out of certain sale, sharing, targeted advertising or profiling, limit certain sensitive-data processing, use an authorized agent and appeal certain request decisions. Rights and business obligations vary by state and statutory threshold.

For California residents, where the CCPA applies, the categories described in Sections 3 and 4 are the categories of personal information MedaStaré may collect; Sections 5 and 6 describe sources and purposes; Section 11 identifies recipient categories; Section 12 describes our current sale/sharing position; and Section 14 describes retention periods or criteria. MedaStaré does not use private app content for cross-context behavioral advertising.

18. Age requirement and minors

MedaStaré is intended for users who are at least 18 years old. The current account flow relies on a user-provided date of birth or age declaration and does not use a third-party identity or age-verification service as the default age gate.

If MedaStaré reasonably learns that an account belongs to a person under the permitted age, MedaStaré may suspend access, request age-related verification where lawful, restrict features, delete the account or take another action required by law. A parent or legal guardian who believes a minor has provided personal data may contact support@medastare.com.

MedaStaré does not knowingly sell or share minors' personal data for cross-context behavioral advertising.

19. Account deletion

A user with an account can initiate account deletion through Settings > Account > Delete Account or another deletion control made available in the applicable app version.

The account-deletion workflow is designed to remove active account database records and user media covered by the workflow. Under the current storage configuration, deleted Cloud Storage media may remain recoverable in provider soft-delete for up to approximately 7 days before final provider-level expiration. Certain transaction, audit, moderation, competition, fraud, legal or compliance records may be retained or de-identified where reasonably necessary and legally permitted.

Deletion of a MedaStaré account cannot delete copies that other users independently created outside MedaStaré or information controlled by independent third parties. Provider-side deletion is also subject to the provider's applicable terms, technical capability and legal retention requirements.

If you have a Stripe Connect creator account, deleting your MedaStaré account does not necessarily cause immediate deletion of information Stripe is required or permitted to retain for identity verification, anti-fraud, anti-money-laundering, tax, payment, payout or other legal and compliance purposes. MedaStaré may request or initiate appropriate connected-account closure or de-linking where supported, but Stripe's retention of Stripe-controlled records is governed by Stripe's own legal obligations and privacy terms.

More information is available on the Account and Data Deletion page.

20. Store subscriptions and privacy

MedaStaré uses limited store transaction and entitlement information to determine paid access, restore eligible purchases, respond to entitlement problems, prevent fraud and process store status changes such as expiration, revocation or refund.

Apple processes App Store payments under Apple's own terms and privacy practices. Google processes Google Play payments under Google's own terms and privacy practices when Google Play billing is enabled. MedaStaré does not receive full payment-card details for store-processed subscriptions.

Subscription cancellation and account deletion are separate. See the Subscription Terms for billing, renewal, cancellation and refund information.

21. Creator payouts and Stripe Connect

MedaStaré uses Stripe Connect for eligible creator payout functions, including creator onboarding, verification, financial-account setup, transfers and payouts. Stripe is a separate financial-technology provider and processes information under its own privacy terms in addition to any processing it performs for or in connection with MedaStaré's Stripe Connect integration.

What creators may be asked to provide

Depending on the creator's country, legal status and Stripe requirements, the Stripe Connect onboarding flow may request personal or business identity information, address, date of birth, tax information, government identification, verification documents and a bank account or eligible payout card. The exact fields are determined by Stripe's requirements for the connected account and available payout capabilities.

What happens to bank or card information

Stripe may provide MedaStaré with limited or masked financial-account information and account status needed to operate payouts, such as the connected-account ID, payout method type, institution or bank name where available, country, last digits, verification status, capability status, payout status, transfer and balance information, and other operational metadata. MedaStaré may use that information to send creator earnings, reconcile transfers, answer payout-support questions, prevent fraud and meet legal or accounting obligations.

Identity verification and compliance

Stripe Connect can collect and validate identity, business and verification information, including document uploads where required. MedaStaré may receive verification requirements, status or other information available through Stripe's APIs that is reasonably necessary to administer the creator relationship, comply with applicable legal obligations, investigate fraud or support the creator. MedaStaré does not represent that Stripe will immediately delete verification, transaction or financial records when a creator leaves MedaStaré because Stripe may have independent legal and regulatory retention obligations.

Creator payouts are different from user subscriptions

Stripe Connect is used for creator payout infrastructure and is not the payment processor for ordinary MedaStaré mobile subscription purchases made through the Apple App Store or Google Play. App Store and Google Play subscription billing remains subject to the applicable store's billing and refund system.

Creators should never send complete bank-account credentials, payment-card numbers, CVC codes, online-banking passwords or identity documents to MedaStaré by ordinary email or chat unless MedaStaré provides a specifically designated secure channel for that purpose.

22. Website cookies and similar technologies

The MedaStaré website uses technologies necessary for security, delivery, preferences and basic operation. Where optional analytics, session replay or marketing technologies are enabled, MedaStaré will use a consent mechanism where applicable law requires one.

Contentsquare may be used for website experience analytics and Session Replay where enabled. MedaStaré has selected a full-masking configuration intended to prevent visible page content from being reproduced in replay. Technical interaction and device/session information may still be collected as described in Section 10. Masking choices do not replace consent where consent is legally required.

MedaStaré does not intentionally activate advertising cookies to collect private app content. If marketing or attribution technologies are introduced, the Cookie Policy and consent controls will be updated before use where required.

See the Cookie Policy for current website technology categories and available choices.

23. Changes to this Policy

MedaStaré may update this Policy to reflect product, provider, legal, security or operational changes. The effective date and version will be updated when a new version is published.

For material changes, MedaStaré will provide additional notice where required, which may include an in-app notice, email, website notice or renewed consent for processing that legally requires a new consent. A change to this Policy does not retroactively make previously unlawful processing lawful and does not remove mandatory rights.

Historical versions may be retained internally for compliance, dispute resolution and audit purposes.

24. Contact and complaints

Questions, privacy requests and complaints may be submitted through the Privacy Choices page or sent to support@medastare.com.

Please do not email passwords, Apple or Google account credentials, complete payment-card information, authentication tokens, intimate images, medical records or other information that is not necessary to identify and process your request.

You may have the right to complain to a data-protection authority or other regulator in your jurisdiction. MedaStaré may ask you to use our request channel first where applicable procedure permits or requires it, but nothing in this Policy limits a right to contact a regulator where the law gives you that right.