Privacy policy

This policy covers visitors to the YeYamo website, users of its discovery services, contributors and partners. It explains processing related to browsing, accounts, contact with the team and the features you use. The information involved depends on your activity: reading a public page does not require the same information as a booking or a contribution.

In this policy, ‘personal data’ means information that identifies you directly or indirectly. Websites, app stores and partner services accessible through links have their own policies. Please read them before providing information to those services.

For questions about this policy or requests concerning your data, contact the YeYamo team at hello@yeyamo.cm with ‘Privacy’ in the subject line. Specify the service concerned and, where necessary, the email address associated with your account to help locate your information.

Never send your password, a sign-in code, a complete payment card number or an identity document without a justified request. Where verification is needed to protect your account, only information proportionate to that verification should be requested.

Account and profile information: identifier, name or username, contact details, profile image, preferences and information you choose to provide. Mandatory fields should be distinguished from optional information at collection. Profile details may be visible depending on the features and settings available.

Content and interactions: reviews, comments, photographs, stories, saved places, reports and messages to support when you use these features. Before posting, check that your content does not disclose someone else’s private information and that you have the necessary permissions.

Technical data: information needed to communicate with the server, such as IP address, browser type, session information and errors. For available booking, payment or partner processes, transaction references, contact details and information needed to handle the request may also be involved.

Information needed to deliver the service enables sign-in, requested features, preference management, responses to enquiries and follow-up on operations. Contributions enrich discovery content and community exchanges.

Technical information and reports help diagnose errors, prevent abusive access and review reported content. Access to information should meet a need related to these purposes. A materially different new use should be accompanied by appropriate information and prior agreement where required.

Depending on the processing and applicable law, using your data may be necessary to provide a service you request, comply with a legal obligation or pursue a legitimate interest such as protecting the service against fraud. Processing based on legitimate interests must take your rights and reasonable expectations into account.

Where processing relies on consent, you should be able to withdraw it for the future. Withdrawal does not affect processing already carried out on that basis. Refusing an optional use should not prevent you from reading public pages that do not require that use.

If a feature suggests nearby places, access to location depends on permission in your browser or device. You can refuse or withdraw that permission in your device settings. Features that depend on proximity may then be limited.

Photo, camera and notification permissions should correspond to the action you want to take. Review the permissions displayed by your device. Also consider location information visible in photographs and text you publish.

The session cookie ‘yeyamo_intro_seen’ records only that the introduction has been seen, so it does not replay while browsing. It contains no personal identifier, is not used for advertising tracking and has no persistent expiry date. Its removal depends on how your browser manages sessions.

The administration area uses authentication cookies to maintain a session and verify access. The access cookie expires according to the lifetime provided during authentication. Refresh and session-information cookies have a maximum lifetime of 30 days in this version of the site. Signing out requests their removal from the browser.

The public site’s language is included in the page address using the ‘lang’ parameter. This choice does not require an additional cookie. You can delete cookies in your browser; doing so may end a session and require you to sign in again.

Adding optional trackers, including advertising or audience measurement where consent is required, should include information about their purpose, provider, lifetime and how to accept or reject them.

Depending on the service used, recipients may include authorised team members, providers needed to host and operate the service, and partners involved in an operation you request. A support request may be viewed by the people responsible for resolving it.

A public contribution can be viewed, shared or copied by other people. Avoid including private contact details, official documents or sensitive information. Disclosure to authorities may be necessary where a legal obligation or legally valid request requires it.

Retention should be limited to what is necessary for the relevant purpose. Account data is related to the duration of your relationship with the service; support enquiries may need follow-up until resolved; some transaction records may be subject to legal retention requirements.

Closing an account does not necessarily mean all information is deleted immediately: some records may need to be retained for a legal obligation, a dispute or service protection. You can ask which periods or criteria apply to your situation. Any exceptions to deletion should be explained to you.

The administration area uses session and permission controls. Authentication cookies are inaccessible to page JavaScript and configured for secure transport in production. These protections contribute to access security without providing an absolute guarantee against every incident.

Use a unique password, keep your codes confidential and sign out on shared devices. If you suspect unauthorised access, contact support promptly without including secrets in your message. Incidents should be assessed and required notifications made in accordance with applicable rules.

Processing locations may depend on the technical services and partners used. Where international data transfers are involved, applicable legal requirements and necessary safeguards must be considered. You can contact the team for information about recipients and safeguards relevant to your data.

Opening an app store or external website takes you into that third party’s environment. Its handling of your information depends on its own terms and settings. This policy does not replace information supplied directly by those services.

Depending on applicable rules and the processing concerned, you may request access to your data, correction, deletion, restriction of processing or receipt of certain data in a reusable format. You may also object to certain processing and withdraw consent for the future.

Send your request to hello@yeyamo.cm, specifying the right you wish to exercise and the service concerned. Proportionate identity verification may be necessary. A response should be provided within the legally applicable period, and any restriction or refusal should be explained. You can contact the competent data protection authority if you believe your rights have not been respected.

Minors should be accompanied by a parent or legal representative when required by law or by the relevant feature. Do not publish contact details, documents or images that could endanger a child. Report content or collection you consider inappropriate to support so it can be reviewed.

A parent or legal representative can contact the team about a child’s data. Information needed to verify the request should be limited to what is useful to protect the child and prevent unjustified disclosure.

This policy may evolve with service features, providers and applicable obligations. The update date identifies the version you are reading. Significant changes to data use should be communicated appropriately and new consent obtained where necessary.

The French and English versions present the same information. If a passage seems unclear, contact the team for an explanation before providing sensitive information.