Legal documents

Cookie Policy

Last updated: 7 November 2026

1. What Cookies Are

Cookies are small text files that a website stores on your device (computer, tablet, or phone) when you visit it. They allow the website to recognise your device, keep you signed in, and remember choices you have made. Similar technologies, such as entries in your browser's local storage, can serve the same purposes; where this policy refers to "cookies", it includes such similar technologies.

This Cookie Policy explains which cookies are set by the Aopy websites and platform (aopy.com and app.aopy.com), why they are set, and how you can control them. It supplements our Privacy Policy, which describes more broadly how Easy Life Tech SRL ("Aopy", "we", "us") processes personal data.

2. Cookies We Set

Our own cookies are first-party: we set no first-party advertising cookies anywhere, and our own visit statistics on aopy.com (the aopy_mkt_sid row below) run only once you grant the "Analytics" category. Every cookie below falls into one of two groups: cookies we set ourselves (first-party — strictly necessary, or functional or analytics where the table says so), and cookies our analytics/advertising vendors set on our marketing pages, and only once you grant the matching category in our cookie banner.

This policy covers aopy.com and app.aopy.com. If you are visiting an online shop that uses Aopy, the sign-up window and visitor-recognition cookies our software sets on that shop are described in our Data Processing Guidelines, and it is the shop that decides whether and how to ask you for consent to them.

2a. First-party cookies (set by us)

Cookie Type Purpose Duration
aopy_consent First-party, strictly necessary Stores your cookie-consent choices for the four categories described below (necessary, functional, analytics, marketing). If you made a choice under our previous cookie name (used under our earlier brand), it was automatically carried over to this cookie so nothing was lost or reset. 12 months (SameSite=Lax; Secure)
aopy_visitor_id (stored in your browser's localStorage, not a cookie) First-party, strictly necessary A random identifier created only when you make a choice in the cookie banner. It is the key of the record we keep of that choice (see section 5, "How We Log Your Consent"), so that we can show what you chose and when. It is not used for analytics or advertising and is not sent to any other party. Until you clear your browser's site data; it is not removed when you change your choice
sb-*-auth-token (Supabase) First-party, strictly necessary Holds your authentication session (a JSON Web Token) and is managed by our authentication provider so that you stay signed in to your account. For the lifetime of your session, refreshed automatically while you remain signed in
sb-role-reval-at First-party, strictly necessary Records when your permissions were last re-checked against our database, so that a change to your role in the platform takes effect straight away instead of waiting for your session token to be renewed. 5 minutes (HttpOnly; SameSite=Lax; Secure)
aopy_lead First-party, strictly necessary Set when you submit one of our public marketing forms. It identifies that submission to our server, so the ROAS Calculator can unlock the full report you asked for without making you enter your details a second time. It is not readable by scripts on the page, and it authorises nothing beyond that unlock. 180 days (HttpOnly; SameSite=Lax; Secure)
aopy_lead_hint First-party, functional Set when you submit one of our forms, and only if you grant the "Functional" category in our cookie banner. It holds only a masked form of the address you gave us (for example a***@shop.ro), so that a marketing page can show "we already have your details" instead of asking you to fill the form again. It grants no access: every action that matters re-checks the cookie above on our server. It is not used for analytics or advertising. If you withdraw the "Functional" category, it is removed and no longer read. 180 days, or until you withdraw consent (SameSite=Lax; Secure)
aopy_mkt_sid, aopy_mkt_attr (stored in your browser's sessionStorage, not cookies) First-party, Analytics category Our own visit statistics on aopy.com, set only if you grant the "Analytics" category. aopy_mkt_sid is a random identifier of your visit; aopy_mkt_attr holds the source of your first visit (referring page and campaign parameters). While you browse, our script sends to /api/marketing/track the pages you view, a signal every 15 seconds while a page is open, the sections and prices you look at and the steps you take in our forms. From each request our server derives your country and city, your device and browser type, and a code computed from your IP address and browser that changes every day; your IP address is not stored. The records are kept for 90 days, then only as daily totals that do not identify you. They are not shared with any analytics or advertising vendor. If you withdraw the "Analytics" category, the script stops at once and removes both items. Until you close the browser tab, or until you withdraw consent
roas_access First-party, strictly necessary Holds the access token for the ROAS Calculator Pro report you requested, so that the report opens on your device and from the link we email you. 180 days (HttpOnly; SameSite=Lax; Secure)
ga4_oauth_state, gm_oauth_state, meta_oauth_state, meta_oauth_temp, shopify_oauth_state, shopify_integration_name, shopify_install_intent, tiktok_oauth_state, tiktok_oauth_temp, gm_oauth_temp, canva_oauth_state, canva_pkce_verifier, canva_return_to, canva_return_jwt First-party, strictly necessary Set only while you are connecting a third-party integration (Google Analytics 4, Google Merchant Center, Meta, Shopify, TikTok or Canva), and read once when that provider sends you back to us. They hold a single-use security token proving the return trip is yours, the matching proof key for it, the name you gave the integration, a short-lived reference to the accounts you can pick from, the Canva return token kept while you sign in, and the page to return you to. They are deleted as soon as the connection completes. 30 minutes, or until the connection completes (HttpOnly; SameSite=Lax; Secure)

2b. Third-party cookies (set only after you grant consent)

On our public marketing pages and our ROAS Calculator, the vendor cookies below are loaded only if you grant the matching category in the cookie banner. If you decline a category, or have not yet made a choice, that vendor's script never loads and none of its cookies are set. These cookies are never set on the app dashboard. Each vendor controls its own cookie lifetime, which can change on their side without our involvement; the durations below are their currently published defaults.

Cookie Type Purpose Duration
_ga, _ga_<container-id> Third-party (Google Analytics — GA4), Analytics category Distinguishes visitors and persists session state for our Google Analytics 4 measurement on the marketing pages. Set only if you grant the "Analytics" category. How Google handles this data: Google Privacy Policy. Up to 13–24 months (Google's current default; see Google's own cookie policy for the authoritative figure)
_fbp Third-party (Meta Pixel), Marketing category Used by Meta to measure ad performance and campaign attribution for our marketing pages. Set only if you grant the "Marketing" category. How Meta handles this data: Meta Privacy Policy. 90 days (Meta's current default)
_ttp, _tt_enable_cookie Third-party (TikTok Pixel), Marketing category Used by TikTok to measure ad performance and campaign attribution for our marketing pages. Set only if you grant the "Marketing" category. How TikTok handles this data: TikTok Privacy Policy. ~13 months (TikTok's current default)

We do not place any other third-party analytics, advertising, or social-media cookies beyond the ones listed above, and none of them are set unless and until you grant the matching consent category.

Our cookie banner lets you decide per category. The four categories are:

  • Necessary — required for the websites and the platform to function (for example, authentication and storing your consent choices). These cookies are always on and cannot be disabled; under applicable ePrivacy rules (in Romania, Law no. 506/2004), strictly necessary cookies do not require consent.
  • Functional — remembers optional preferences and enables enhanced features. One cookie in use: aopy_lead_hint (Section 2a), which lets a marketing page recognise that you have already given us your details and show a short confirmation instead of the form. It is set when you submit one of our forms, only if you have granted this category; it holds only a masked form of your own address, it is never used for analytics or advertising, and it is removed when you withdraw this category. We set no other functional cookies.
  • Analytics — helps us understand how our marketing pages and ROAS Calculator are used. In use on our marketing pages: granting this category loads Google Analytics 4 (GA4), which sets the _ga and _ga_<container-id> cookies described in Section 2, and starts our own visit statistics (aopy_mkt_sid and aopy_mkt_attr, Section 2a). Not used on the app dashboard.
  • Marketing — supports measuring advertising campaigns and conversions on our marketing pages. In use on our marketing pages: granting this category loads the Meta Pixel and TikTok Pixel, which set the _fbp, _ttp, and _tt_enable_cookie cookies described in Section 2. Not used on the app dashboard.

Legal basis. Under art. 4(5) of Law no. 506/2004, we store or read functional, analytics and marketing cookies (and the similar browser storage described in Section 2a) on your device only with your prior consent, which you give in our cookie banner. The personal data these cookies involve is processed under the GDPR (Art. 6(1)(a), consent) and Law no. 190/2018, which implements it in Romania.

To be clear: cookies in the "necessary" category are always set; cookies in the "analytics" and "marketing" categories are set only on our public marketing pages (including the ROAS Calculator), and only once you grant the matching category — never on the app dashboard, and never before you choose. The one functional cookie we set, aopy_lead_hint, is set only once you grant the "functional" category and is described in Section 2a and in the "functional" bullet above. If we add further functional cookies, or further analytics/marketing vendors, we will first update this policy and the cookie banner.

4. Managing Your Preferences

You can review and change your cookie choices at any time:

  • Cookie Preferences link — every page in our legal section carries a "Cookie Preferences" link in the footer that reopens the consent banner, where you can change your choices per category. Withdrawing consent is as easy as giving it.
  • Browser controls — most browsers let you block or delete cookies through their settings. If you delete the consent cookie, the banner will appear again on your next visit. Note that blocking strictly necessary cookies (such as the authentication cookie) will prevent you from signing in to the platform.

Withdrawing your consent does not affect the lawfulness of any processing carried out before the withdrawal.

When you make a choice in the cookie banner, we record that choice server-side in an append-only audit log. The record includes: a visitor or user identifier, the categories you accepted or declined, the version of the banner you were shown, your IP address in shortened form (its last part removed, so it no longer points to a single device), and your browser's user-agent string. Entries in this log are only ever added, never altered, and are deleted 24 months after they are recorded.

On pages of aopy.com served by our marketing-site script, your choice reaches this log through /api/marketing/site-client. The same address also receives that script's error reports (the error message and the part of the page that failed), which we pass to our error-monitoring provider to fix faults; it is not used for analytics or advertising.

We keep this log so that we can demonstrate, if required, that consent was validly obtained (accountability under Art. 5(2) and Art. 7(1) GDPR). For how long we retain personal data generally, and for your rights over this data, see our Privacy Policy.

6. Changes to This Policy

We may update this Cookie Policy as the platform evolves — for example, if we introduce a new cookie, add a new third-party vendor, or use the functional category for something new. When we do, we will update the table and statements above and increment the version of the cookie banner; where the change requires it, we will ask for your renewed consent before any new cookie is set.

The date of the latest revision is shown at the top of this page. We encourage you to review this policy periodically.

7. Contact

If you have questions about our use of cookies or about this policy, contact our Privacy Team at privacy@aopy.com, or write to Easy Life Tech SRL, Șos. București-Ploiești, Nr. 15, Imobilul 2 - Spațiu Comercial, Etaj 5, Sector 1, București, Romania.

You also have the right to lodge a complaint with the Romanian supervisory authority: Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPDCP), B-dul G-ral. Gheorghe Magheru 28-30, Sector 1, București, www.dataprotection.ro.

8. Language

This Cookie Policy is published in English and in Romanian. In the event of any inconsistency or difference in interpretation between the two versions, the English version prevails.

Who publishes

Easy Life Tech SRL

15 Bucharest–Ploiești Road, Building 2 — Commercial Space, 5th Floor, Sector 1, Bucharest, Romania
CUI 54742254 · Reg. Com. J2026033503008 · EUID ROONRC.J2026033503008
Questions about these documents?