Last updated: May 30, 2026

Cookie Policy

1. Scope

This Cookie Policy explains how How I Met uses cookies, local storage, device storage, and similar technologies on the public website, web-based app surfaces, and mobile application where applicable. It should be read together with the Privacy Policy.

2. What cookies and similar technologies are

A cookie is a small file or identifier stored on your device by a website. Similar technologies include local storage, session storage, secure app storage, software identifiers, pixels, SDK storage, and cached data. These technologies can help a service remember a choice, keep a session active, protect against abuse, load content, diagnose errors, or understand technical performance.

3. Public website cookies

The public How I Met website is primarily informational. It may use cookies or similar storage that are strictly necessary to deliver pages, secure the website, remember a required choice, route traffic, prevent abuse, or measure basic technical availability. We do not currently plan to use third-party advertising cookies on the public website.

Server and security logs may record technical information such as timestamps, requested URLs, IP-derived information, user-agent strings, errors, and request identifiers. These logs are not always cookies, but they are part of the technical operation and security of the website.

4. App and web app storage

The How I Met app and any web app surfaces may use local or secure storage to keep you signed in, remember account or feature state, cache assets, store temporary files, keep drafts or playback state, support notifications, and maintain security. For example, storage may be used for authentication session data, profile or conversation cache, app preferences, audio playback state, or temporary media generated by features you use.

Some device identifiers or tokens are not cookies but work in a similar operational way. Push notification tokens, for example, are used to send notifications you enable and to clean up invalid or blocked notification tokens.

5. Strictly necessary technologies

Strictly necessary technologies are used to provide a service you request or to keep the Service secure and reliable. These may include authentication, security, fraud prevention, load balancing, consent or preference memory, content delivery, error handling, diagnostics, and app functionality. Blocking them may prevent sign-in, profile features, messaging, media playback, or other core functionality from working properly.

6. Analytics, advertising, and non-essential cookies

How I Met does not currently describe the public website as using third-party advertising cookies. If we add non-essential analytics, advertising, personalization, or cross-site tracking technologies, we will provide notice and obtain consent where required by law before using them.

Some limited audience or performance measurement may be exempt from consent under applicable rules when it is strictly limited to technical operation, security, availability, or aggregate service measurement. Where consent is required, you should be able to refuse or withdraw it without losing access to essential features.

7. Managing cookies and storage

You can limit, delete, or block cookies through your browser settings. You can also clear website data, reset app storage, revoke app permissions, disable notifications, or uninstall the app through your device settings. These controls may remove saved sessions or preferences and may require you to sign in again.

Browser and device controls vary. Some settings affect only cookies, while others affect local storage, notifications, microphone, camera, location, motion, or photo-library permissions.

8. Updates and contact

We may update this Cookie Policy if our website, app storage, analytics, security, or consent practices change. The "Last updated" date shows when the current version was posted.

For any question about cookies: contact@howimet.com.