Skip to content

Placeholder legal entity — replace before launch

Values shown in [brackets] come from src/config/legal.ts and must be filled in before this page goes live.

Legal

Cookie Policy

Last updated: October 24, 2026

This policy explains how [COMPANY LEGAL NAME] [LEGAL FORM] ("Feeverso", "we", "us") uses cookies on the Feeverso website and web app (the "Service"). It is short, because we use exactly one cookie.

It should be read together with our Privacy Policy, which explains how we handle personal data more generally. If anything is unclear, write to privacy@feeverso.example.

1. Who we are

[COMPANY LEGAL NAME] [LEGAL FORM], [STREET AND NUMBER], [POSTAL CODE] [CITY], [COUNTRY], is the provider of the Service and the operator of this website. You can reach us about cookies and privacy at privacy@feeverso.example.

2. What cookies are

A cookie is a small text file that a website asks your browser to store. When you come back to the site, the browser sends the file back with your request. Cookies are how a website recognises that two requests come from the same browser, which is what makes it possible to stay signed in while you move between pages.

Three distinctions matter here:

  • First-party cookies are set by the site you are visiting. Third-party cookies are set by another company whose service is embedded in the page.
  • Session cookies are deleted when you close the browser. Persistent cookies stay for a set period, which the site defines.
  • httpOnly cookies cannot be read by JavaScript running in the page. This makes them harder to steal if something goes wrong on the page.

3. The only cookie we use

CookiePurposeDurationTypeSet byFlags
fv_sessionKeeps you signed in. It holds a random session token that identifies your logged-in session, so you do not have to enter your password on every page.30 days, or until you sign out or delete your accountStrictly necessary, first-partyFeeversohttpOnly

That is the complete list. We do not use any other first-party cookie.

The cookie contains a session identifier. We store a hash of that token on our servers, so the value in your browser cannot be used directly to read our database. The cookie does not contain your password, your email address or your payment details.

4. Why you do not see a cookie banner

EU and UK rules (Article 5(3) of the ePrivacy Directive and, in the UK, regulation 6 of PECR) require consent for storing information on your device, except where the storage is strictly necessary to provide a service you have explicitly requested.

Keeping you signed in is exactly that. Without fv_session, the Service cannot tell that you are logged in, and there is no account area to use. The cookie is therefore strictly necessary, and we do not need your consent to set it.

We still tell you about it here, in plain language, because you have the right to know what is stored on your device and how to remove it. Because we use no analytics, advertising or tracking cookies, there is nothing else to ask you about.

5. What happens if you block or delete the cookie

You are free to block or delete fv_session in your browser at any time. Be aware of the effect:

  • If you block it, you will not be able to sign in or use your account. The marketing pages of the website will still work.
  • If you delete it, you will be signed out and will need to sign in again.
  • If you clear all cookies, you will be signed out of the Service.

Blocking this cookie does not delete your account or your content. Your brand kits, conversations and generated files stay on our servers until you delete them or delete your account.

6. Stripe and checkout

Payments are processed by Stripe. When you start a checkout or open the billing portal, you leave our app and continue on stripe.com, which is operated by Stripe.

On its own pages, Stripe sets cookies that it needs to run the payment flow, remember your details and prevent fraud. Those cookies are Stripe's, not ours. We do not control them and cannot read them. Stripe's own cookie and privacy policies apply to them, and you can find them on stripe.com.

Card data is entered on Stripe's pages and never reaches our servers.

7. No analytics, advertising or tracking

We want to be direct about what we do not do:

  • no analytics tools, such as Google Analytics;
  • no advertising or retargeting cookies, and no advertising identifiers;
  • no social media pixels, share buttons or embedded videos that track you;
  • no cross-site tracking, fingerprinting or behavioural profiling;
  • no sale or sharing of personal information for cross-context behavioural advertising.

We count credit usage on our servers to bill your plan, but that is account data, not cookie-based tracking, and it is not used to follow you around the web.

8. How to control cookies in your browser

Every major browser lets you see, block and delete cookies. The menus move around between versions, so look for the privacy or cookies section in your browser settings:

  • Chrome: Settings, then Privacy and security, then Cookies and other site data.
  • Safari on macOS: Settings, then Privacy, then Manage Website Data. On iPhone and iPad: Settings, then Apps, then Safari, then Advanced, then Website Data.
  • Firefox: Settings, then Privacy and Security, then Cookies and Site Data.
  • Edge: Settings, then Cookies and site permissions, then Manage and delete cookies and site data.

You can also use a private or incognito window, which discards cookies when you close it, or a browser extension that manages cookies. Blocking all cookies may break other websites you use, not just ours.

9. Do Not Track and Global Privacy Control

Some browsers can send a Do Not Track signal, and some send a Global Privacy Control signal. We do not track you across third-party websites, so there is no cross-site behaviour for these signals to switch off. If a future version of the Service introduced anything that required honouring them, we would update this policy first.

10. Changes to this policy

If we add a cookie, we will update this page before it goes live and list the new cookie in the table above, with its purpose, duration and type. If a new cookie requires consent, we will ask for it before setting the cookie. The version that applies is the one published here, with the date at the top.

11. Contact

For any question about cookies or this policy, write to privacy@feeverso.example, or contact [COMPANY LEGAL NAME] [LEGAL FORM] at [STREET AND NUMBER], [POSTAL CODE] [CITY], [COUNTRY]. Our Privacy Policy explains how to exercise your data protection rights, including how to complain to a supervisory authority.