Cookies Policy

1. What cookies are

A cookie is a small file a website stores in your browser, which the browser sends back to that website on your next visits. Similar technologies, such as your browser's local storage, keep information on your device in the same way. Some are needed for a site to work at all; others remember your choices; others, which pleny.com does not use, measure audiences or show advertising.

2. The cookies pleny.com sets

Every cookie pleny.com sets is needed for the website to work or to remember a choice you made:

• locale: the language you chose or your browser asked for, kept for one year.
• pleny_at and pleny_rt: your session, if you sign in on the website. They hold the tokens Pleny's servers sign you in with, cannot be read by the page's scripts, and are removed when you sign out, or seven days after you last used the website.
• pleny_device_id: an identifier of this browser, sent when you sign in or out, in the way the apps identify a phone. It lasts up to 400 days.
• pleny_last_login: the name, email address, picture and sign-in method of the account last signed in on this browser, so that it can offer to continue with that account. It stays after you sign out, for up to 400 days, until you clear it.
• pleny_oauth: a sign-in with Google or Facebook while it is under way, for up to 10 minutes.
• pleny_anon_id: a random identifier that remembers the reactions you gave to blog posts without an account, for one year.
• portal_session: the session of Pleny's own staff in the blog editor, for seven days. Visitors never receive it.

3. Other storage on your device

The support chat on pleny.com keeps an identifier of your browser and the conversation you have open in your browser's local storage, so that your conversation is still there when you come back, and whether the chat window is open in session storage, which ends when you close the tab. Clearing your browser's site data removes them, and with them the way back to your past conversations from that browser.

4. Cookies of other companies

Cloudflare, which delivers pleny.com and protects it from attacks, may set cookies needed to tell people from automated traffic.

If you choose to sign in with Google or Facebook, you sign in on their sites, which may set their own cookies under their own policies.

Blog posts may include videos from YouTube or Vimeo, or animations from Tenor. Those companies may set cookies when the post is shown or the video is played, under their own policies.

Links to the App Store, Google Play or Pleny's social media pages take you to those companies' sites, which have their own cookies.

5. In the apps

The apps do not use browser cookies. They keep your session and settings on your device, and include software from other companies that stores and reads information on your device:

• Google AdMob and Klipy, which show ads in the free version and may use your device's advertising identifier where you allow it;
• the Facebook SDK, for Facebook sign-in and sharing, which can send Meta information about how the app is used;
• Firebase Crashlytics, Sentry and Datadog, which report crashes, errors and logs;
• PostHog, which runs on our own servers and records how the app is used, so that we can improve it;
• RevenueCat, which manages Pleny Pro subscriptions.

The privacy policy, at pleny.com/privacy-policy, explains what these services receive.

6. Your choices

You can block or delete cookies in your browser's settings, and pleny.com still works, but you will be signed out, and the website will forget your language and the reactions you gave. On your phone, you can reset your advertising identifier or limit ad tracking in its settings, and Pleny Pro removes the ads.

7. Changes to this policy

We may update this policy when the cookies or technologies we use change. The date above shows when the current version took effect. This policy is published in English, Arabic, French and German; if the versions differ, the English version prevails.