Legal documents

Data Processing Guidelines

Last updated: 28 October 2026

1. Purpose of This Guide

This guide is for our customers — the businesses that use Aopy to send email and SMS marketing. When you upload contact lists and send campaigns through the Service, you are the data controller for that contact data, and data-protection law places specific duties on you. This page explains those duties in practical terms and shows you how the platform's built-in tools help you meet them.

When you turn on an ad platform, Aopy sends it your visitors' page views, product views, carts, checkouts and purchases, only for visitors who allowed advertising cookies.

Two things this guide is not:

  • It is not legal advice. It is general educational material. Your obligations depend on your specific situation, and you should consult your own legal adviser for advice on your processing activities.
  • It is not a contract. The binding terms governing how Aopy processes personal data on your behalf are in the Data Processing Agreement (DPA), which forms part of our Terms of Service. If anything in this guide appears to conflict with the DPA, the DPA prevails.

2. Your Role vs. Ours

The GDPR distinguishes between the controller (who decides why and how personal data is processed) and the processor (who processes data on the controller's behalf). For the contact data you bring to the platform, you are the controller and Easy Life Tech SRL ("Aopy") is your processor.

You (the Controller) Aopy (the Processor)
Decide what contact data to collect and why Processes contact data only on your documented instructions (your platform configuration and the DPA)
Ensure you have a valid lawful basis — usually consent — before sending marketing messages Provides consent fields, opt-out handling, and suppression mechanics to help you honor your obligations
Inform your subscribers about your processing (your privacy notice) Discloses its own infrastructure and sub-processors so you can inform them accurately
Respond to your subscribers' data-protection requests Supplies self-service tools (contact export, contact deletion) and assists you as set out in the DPA
Keep your account and team access secure on your side Secures the platform: tenant isolation, encryption in transit, access controls

Aopy also acts as a controller in its own right for a narrower set of data — your account data, billing data, and our website visitors' data. That processing is described in our Privacy Policy, not here.

3. Lawful Basis — How to Choose

Every processing of personal data needs a lawful basis under Article 6 GDPR. For email and SMS marketing, the analysis in Romania is stricter than the GDPR alone, because the Romanian ePrivacy law — Law no. 506/2004 on the processing of personal data and the protection of privacy in the electronic communications sector — requires prior consent before sending commercial communications by email or SMS. In practice:

  • Consent (Art. 6(1)(a) GDPR) is the safe default for marketing email and SMS. Collect it before the first message, keep proof of it, and stop when it is withdrawn.
  • A narrow exception may apply to your existing customers: contact details obtained directly from a customer in the context of a sale may, under conditions, be used to market your own similar products or services — provided the customer was given a clear, free and simple way to refuse at the time of collection and in every subsequent message. The exact scope of this exception is a legal judgment; confirm with your adviser before relying on it.
  • Legitimate interests (Art. 6(1)(f) GDPR) may support ancillary processing of data you already lawfully hold — for example, segmenting your own customer base or analysing campaign performance. It does not override the prior-consent requirement for the sending of the marketing message itself.

Note that a work email address that identifies a person (for example, a name-based address at a company domain) is still personal data. Whatever basis you choose, document your reasoning — you must be able to demonstrate it (Art. 5(2) GDPR, accountability).

For consent to be valid under the GDPR it must be freely given, specific, informed and unambiguous — and you must be able to prove it (Art. 7 GDPR). Practical rules that keep your list clean:

  • No pre-ticked boxes. Consent requires a clear affirmative act. Silence, inactivity or a pre-checked box is not consent.
  • Keep it separate. Do not bundle marketing consent into your terms and conditions or make it a hidden condition of an unrelated service.
  • Name the channels. Say clearly that the person is signing up for marketing by email, by SMS, or both. Consent to one channel is not consent to the other.
  • Record everything. Keep who consented, when, how (which form or flow), and the exact wording they saw. On request, you must be able to produce this proof — our Acceptable Use Policy allows us to ask you for it.
  • Double opt-in is strongly recommended. A confirmation email in which the subscriber actively verifies their address gives you the strongest possible proof of consent and keeps mistyped or malicious sign-ups off your list.

Importing existing lists: only import contacts whose provenance you can document — when, where and how each contact consented (or the documented basis you rely on). Purchased, rented, harvested or "appended" lists are prohibited on Aopy — see the Acceptable Use Policy — and sending to them is both a compliance risk for you and a deliverability risk for everyone.

5. Transparency Duties

As a controller you must inform your subscribers about your processing (Arts. 13–14 GDPR). Your own privacy notice — presented at or near the point where you collect their data — should tell them at least:

  • who you are (your identity and contact details);
  • why you process their data (marketing communications) and on what legal basis (typically consent);
  • that you use a marketing-platform provider acting as your processor — you may name Aopy (Easy Life Tech SRL) or describe the category of provider, and you may link to our sub-processor register for the underlying infrastructure;
  • how long you keep their data;
  • their rights — access, rectification, erasure, restriction, portability, objection, withdrawal of consent — and how to exercise them, including the right to complain to a supervisory authority;
  • how to unsubscribe at any time.

If you turn on an audience sync, Aopy sends Meta, TikTok or Google the email address (and, for Google, the phone number) of contacts with explicit email-marketing consent, hashed with SHA-256 before upload, to show them ads or exclude them from ads; soft opt-in customers are never sent. Tell your customers this.

Keep your notice where subscribers can find it, and link it from your sign-up forms. If you materially change what you do with subscriber data, update the notice and, where needed, refresh consent.

6. Unsubscribe and Opt-Out

Every recipient has the right to opt out of your marketing at any time, and the platform enforces the mechanics for you:

  • Email: the platform automatically inserts a unique, per-send unsubscribe link into every marketing email. The link works without a login, is processed immediately, and updates the contact's status so they are excluded from future marketing sends. Never remove, hide or obscure this link — doing so violates the Acceptable Use Policy and the law.
  • SMS: recipients who reply STOP or DEZABONARE are opted out automatically. Opted-out phone numbers are normalized and stored in hashed form on a suppression list so they stay excluded even if re-imported. See our SMS Compliance page for details.

Opt-outs also arrive through other doors: a reply to your email, a message to your support team, a request in person. Honor them all. Update the contact's status in the platform, and mirror the opt-out in any other system you use — an opt-out given to you once is valid everywhere.

7. Prohibited Data

Some data must never be uploaded to the platform. Under the DPA and the Acceptable Use Policy, you must not upload or process through Aopy:

  • Special categories of personal data (Art. 9 GDPR): data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade-union membership, genetic or biometric data, health data, or data concerning a person's sex life or sexual orientation.
  • Data relating to children under 16. The Service is a business-to-business tool and marketing databases on Aopy must not contain children's data.
  • Purchased, rented, harvested or scraped contact lists, or any list whose provenance and consent you cannot document.
  • Data you have no lawful basis to process — including contacts who have previously opted out.

If you discover that prohibited data has been uploaded to your account, delete it and contact privacy@aopy.com if you need assistance.

8. Data Subject Requests

Your subscribers can exercise their GDPR rights against you, the controller — access, rectification, erasure, restriction, portability, objection, and withdrawal of consent. You generally must respond within one month (Art. 12 GDPR). The platform gives you the tools to serve most requests yourself:

  • Access / portability: export an individual contact's profile and associated data from your audience.
  • Rectification: edit the contact's fields directly in your audience.
  • Erasure: delete the contact from your audience. Deletion removes the contact from your active audience and from all further sending; residual copies are erased in accordance with the retention and deletion terms of the DPA.
  • Objection / withdrawal of consent: set the contact's status to unsubscribed (or let the automatic opt-out mechanics in section 6 do it).

If a data subject contacts Aopy directly about data on your list, we will not answer in your place: we will refer the request to you and assist you as set out in the DPA. For requests concerning data for which Aopy is itself the controller (account data, website data), our own data deletion and data export forms apply.

9. Security on Your Side

We secure the platform — tenant isolation, encryption in transit, access controls — but the security of your account is a shared responsibility. Weak account hygiene is one of the most common causes of data incidents. Follow these practices:

  • Use a strong, unique password for your Aopy account — never one reused from another service — and store it in a password manager.
  • One person, one account. Never share logins. Invite each team member individually and assign the least-privileged role that lets them do their job.
  • Off-board promptly. When someone leaves your team, remove their access the same day.
  • Treat integration credentials and API keys as secrets. Credentials for the integrations you connect (for example, your store or advertising accounts) grant access to real data — do not paste them into chats, tickets or shared documents.
  • Handle exports carefully. Exported files contain personal data. Store them securely, share them only with people who need them, and delete them when no longer needed.
  • Watch for phishing. Aopy will never ask you for your password by email.

10. When You Need a DPIA

A Data Protection Impact Assessment (DPIA) is a structured risk analysis the GDPR requires before starting processing that is likely to result in a high risk to individuals (Art. 35 GDPR). Sending routine newsletters to your own opted-in subscriber list does not normally require one. Indicators that your planned use might:

  • large-scale evaluation, scoring or profiling of individuals — for example, extensive behavioural profiling across combined data sources;
  • systematic monitoring of individuals;
  • processing of sensitive data or data of a highly personal nature;
  • processing data of vulnerable persons, including children;
  • combining or matching datasets from multiple sources in ways people would not expect;
  • using innovative technologies with uncertain privacy impact.

The Romanian supervisory authority (ANSPDCP — Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal, www.dataprotection.ro) publishes guidance on the kinds of processing operations that require a DPIA — check it when in doubt, and consult your legal adviser. Where you carry out a DPIA covering processing performed through Aopy, we will provide reasonable assistance as set out in the DPA.

11. The Aopy Sign-Up Window and Tracking Script on Your Storefront

If you install the Aopy sign-up window and tracking script on your online shop, that code runs on your website and stores information on your visitors' devices. Under Romanian Law no. 506/2004 (art. 4), which implements the ePrivacy Directive, storing information on a visitor's device — or reading information already stored there — needs that visitor's prior consent, unless the storage is strictly necessary to deliver a service they have asked for. That duty is yours as the operator of the site, not ours.

What our code stores on a visitor's device

NameWhat it isLifetime
_cdm_aidA pseudonymous visitor identifier, so that repeat visits from the same browser are recognised as the same visitor rather than counted as new ones. It is issued by the Aopy tracking SDK; where the SDK is not present on the page, the sign-up window writes it directly. On WooCommerce shops the Aopy plugin also sets it from your own server, once the visitor has granted consent for statistics, so that browsers which shorten the life of cookies written by a script keep it longer.Depends on which code writes it: ten years when the sign-up window writes it, 365 days when the tracking script writes it (some browsers shorten the life of cookies written by a script), and 400 days when the Aopy WooCommerce plugin writes it. The tracking script deletes it when a visitor withdraws consent in Strict mode. See the note below
_cdm_aidcA copy of the _cdm_aid identifier the tracking script writes, held in the browser's local storage together with the time that cookie expires. Some consent tools delete, on every page, each cookie they do not list; the script then puts the cookie back from this copy instead of counting the visitor as new. Written and used only after the visitor has granted consent on the page, and only where the tracking script writes the _cdm_aid cookie for this site alone: never in Anonymous mode, when the script runs without cookies, or when the cookie is shared across your subdomains.At most 365 days from when the tracking script first wrote the _cdm_aid cookie, never extended. It can outlast the 7 days some browsers (Safari) allow a cookie written by a script, but never the 365 days of the identifier. Removed on any refusal or withdrawal, on reset, and when site data is cleared; deleting cookies alone does not remove it, so the identifier returns while consent stands
cdm_popup_<form id>One marker per sign-up form, recording that this visitor has already seen or submitted it, so the same window is not shown again.Depends on the form's frequency rule: ten years for "show once" and after a submission, the number of days you configure for "every N days", and for "every visit" until the visitor leaves your shop and comes back (a cookie that also ends when the browser closes)
cdm_visit_tabA marker, held in the browser's session storage rather than in a cookie, that this browser tab is already on your shop, so that a page opened without a referring address is not taken for a new visit. Written only for sign-up windows set to appear on every visit, after a number of pages, or for first-time or returning visitors, and only when the window may write its cdm_popup_ cookie (see the note below on visitors who have not consented).Until the browser tab closes
cdm_vpvCounts the pages the visitor has viewed in the current visit. Written only when one of your sign-up windows is set to appear after a number of pages or for first-time or returning visitors, so that display rule can be applied.Until the visitor leaves your shop and comes back (a cookie that also ends when the browser closes)
cdm_vseenA marker that this browser has visited before, so a first visit can be told from a returning one. Written only for the same display rules as cdm_vpv.13 months
cdm_popup_<form id>_cdThe end time of a countdown timer shown in a sign-up window, so the timer does not restart on every page. Written only for windows that use a countdown that starts separately for each visitor, not one that runs to a fixed date.Until the countdown ends
cdm_teaser_<form id>A marker, held in the browser's session storage rather than in a cookie, that keeps the small reopen button of a closed sign-up window visible on the next pages. Written only for windows that use that button.Until the browser tab closes
_cdm_sidA per-visit identifier, held in the browser's session storage rather than in a cookie, used to group the events of one visit.Until the browser tab closes
_cdm_saidThe tab-only form of the visitor identifier, held in the browser's session storage rather than in a cookie. The tracking script uses it instead of the _cdm_aid cookie in Anonymous mode, or when it runs without cookies, so that nothing identifies the visitor beyond the open tab.Until the browser tab closes
_cdm_qA retry queue: the batches of tracking events that could not be delivered yet, so that they are sent on the next page instead of being lost. It holds the event data that was waiting to go out. Held in the browser's local storage, or in its session storage in Anonymous mode or when the script runs without cookies, and written only while the script is allowed to collect.Until the batch is delivered; a batch not delivered within 24 hours is discarded, and the queue is emptied when the visitor withdraws consent
_cdm_qmWritten only after a visitor's data was erased and Aopy gave the browser a new visitor identifier: it pairs the erased identifier with the new one, so that events still waiting in _cdm_q go out under the new identifier and the erased one is never sent again. Held next to _cdm_q, in the same storage and under the same consent.24 hours, like the queue; it is removed whenever the queue is emptied, including when the visitor withdraws consent
_cdm_cseqA counter, held in the browser's local storage, that numbers the visitor's consent answers one after another so that a later answer always outranks an earlier one. It holds a number only, never an identifier. It is not written for a visitor who refuses and has never been tracked.No expiry date: it stays until the visitor clears the browser's site data
_cdm_cnsA cookie that remembers that the visitor granted consent, so that later pages and visits honour that answer when the shop's own banner does not repeat it. It holds the visitor's consent choice for each purpose, where that choice came from (the shop's banner through Google Consent Mode, or the shop's own code), when the choice was made, and a unique reference for that answer, the same reference Aopy's consent records keep for it. This is a pseudonymous identifier; the cookie holds no name or email address. Written only after the visitor grants consent, and only on shops that do not use a known consent platform (Cookiebot, OneTrust, an IAB TCF platform, the WP Consent API, Gomag's banner or OpenCart's own cookie bar), which keep the answer themselves.365 days (some browsers shorten the life of cookies written by a script); deleted when the visitor refuses, when the browser sends Global Privacy Control or Do Not Track, or when Cookiebot, OneTrust or an IAB TCF platform on the shop asks the visitor again
_cdm_scnsThe tab-only form of _cdm_cns, held in the browser's session storage rather than in a cookie, used in Anonymous mode or when the script runs without cookies. It holds the same consent choice, time and pseudonymous reference, and is written and deleted on the same terms.Until the browser tab closes; deleted earlier on the same events as _cdm_cns
_cdm_attr, _cdm_utmCookies that keep the advertising click identifiers (such as gclid or fbclid) and the campaign tags (UTM) of the page the visitor arrived on, so that a later order can be credited to the click that led to it. Written only while the script is allowed to collect.90 days (some browsers shorten the life of cookies written by a script); deleted when a visitor withdraws consent in Strict mode
_cdm_idsync, _cdm_asx, _aopy_gomag_checkout, _aopy_ps_checkout, _aopy_gomag_order, _aopy_wc_order, _aopy_ga4_checkout, _aopy_ga4_ordersSmall markers held in the browser's session storage, so that the same thing is not reported twice from one tab. _cdm_idsync notes that the shop's own visitor-identity address (WooCommerce) was already asked once in this tab. _cdm_asx holds the code of the last SMS link reported from this tab, so that a page reload is not counted as a second click. _aopy_gomag_checkout, _aopy_ps_checkout and _aopy_ga4_checkout hold the time the checkout was last reported (Gomag shops, PrestaShop shops, and shops that send Google Analytics 4 e-commerce events). _aopy_gomag_order and _aopy_wc_order hold the number of the order just detected (Gomag and WooCommerce shops) and _aopy_ga4_orders the references of the last 20 orders reported. _aopy_gomag_order, _aopy_ga4_checkout and _aopy_ga4_orders are written whatever the visitor's consent answer (a time or an order number, never an identifier); _cdm_idsync, _cdm_asx, _aopy_gomag_checkout, _aopy_ps_checkout and _aopy_wc_order only while the script is allowed to collect.Until the browser tab closes
_aopy_oc_consentOpenCart shops only. A cookie that holds the visitor's answer to the shop's own OpenCart cookie bar: 1 for "Yes", 0 for "No". The Aopy extension writes it from the shop's own server, copying the answer OpenCart keeps in a cookie the tracking script cannot read; the script only reads it. On a 1 the script treats analytics, advertising and personalisation as granted, on a 0 every purpose as refused. It holds no identifier. Your cookie policy page, the one the bar links to, should name Aopy and these purposes.364 days
_aopy_wcWooCommerce shops only. One item in the browser's session storage that remembers what the visitor's cart held when it was last read (product ids, quantities and unit prices, at most 20 lines), how many times each cart change was already reported from this tab (so that a real repeat is not dropped as a duplicate), when the checkout was last reported, and how often the shop's own cart address was already asked, so that the shop's server is asked only when the cart really changes. Written only while the script is allowed to collect; nothing in it identifies the visitor.Until the browser tab closes
_aopy_checkout_consent, _aopy_checkout_consent_sentGomag shops only. When the visitor ticks the marketing-consent box that Aopy adds to the checkout (or the shop's own newsletter box, where the checkout already has one), the tick is kept in the browser's session storage together with the email address typed at checkout, until the order-confirmation page, where it is sent to Aopy with the order number; where Aopy does not receive the shop's orders, it is sent as soon as the order is placed. _aopy_checkout_consent_sent lists the last five email addresses already sent, so that the same tick is not sent twice. This is the visitor's own explicit marketing opt-in, so it is not held back by the analytics consent.Until the browser tab closes; a stored tick is ignored after 2 hours
_cdm_paOne item in the browser's local storage that lists the products for which the visitor asked for a price-drop alert from this browser: the shop's product id and the time of the request, for at most 20 products. On a later click on the same product's button, the form then reminds the visitor to look for the confirmation email. Written only after the visitor submits the price-alert form and Aopy accepts the request; it holds no email address and no visitor identifier.No expiry date: it stays until the visitor clears the browser's site data. Entries older than 7 days are ignored and removed at the next request
_aopy_qThe Shopify web pixel's retry queue, the counterpart of _cdm_q: batches of events not delivered yet, held in the browser's local storage so that they are sent on the next page. Written only once the visitor has granted analytics consent through Shopify's Customer Privacy settings.Until the batch is delivered; a batch not delivered within 24 hours is discarded, and the queue is emptied when the visitor withdraws consent
_aopy_aidThe Shopify web pixel's visitor identifier. As a cookie it carries the identifier Shopify gives the browser, so that an order can be matched to this browser (the Aopy storefront extension copies it onto the cart). When Shopify supplies none, a random identifier is held under the same name in the browser's session storage instead. Written only once the visitor has granted analytics consent; the cookie is deleted if the visitor refuses.Cookie: 365 days (SameSite=Lax). Session storage entry: until the browser tab closes
_aopy_sThe Shopify web pixel's per-visit identifier, held in the browser's session storage, used to group the events of one visit. Written only once the visitor has granted analytics consent.Until the browser tab closes; a visit also ends after 30 minutes without activity or after 24 hours
_aopy_cdThe Shopify web pixel's copy of the visitor's latest consent decision (a decision reference, its sequence number, its time, the four answers: analytics, marketing, preferences, sale of data, and whether they came from the visitor's own answer or only from the shop's default setting), held in the browser's local storage so that each page does not record the same decision again. It holds no visitor identifier and is kept after a refusal, because it records that refusal.No expiry date: it stays until the visitor clears the browser's site data
_aopy_asu, _aopy_asxHeld in the browser's session storage when a visitor arrives from an SMS link to the shop. _aopy_asu keeps the campaign tags (UTM) the link carried for the rest of the visit; _aopy_asx holds the code of the last such link reported, so that a reload is not counted as a second click. Written only once the visitor has granted analytics consent.Until the browser tab closes
_aopy_fqThe retry queue of Aopy's form capture, which listens to the sign-up forms on your own website: when a visitor submits such a form and the answer cannot be delivered to Aopy yet, the answers typed into the form, including the email address, wait in the browser's local storage and are sent from the next page that carries the form-capture code. Written only after the visitor submits a form, and only when its delivery failed.Until the answer is delivered; an answer not delivered within 24 hours is discarded, and at most 20 are kept
aopy_loy_cfg_<shop key>Loyalty programme widget only. A copy of your loyalty programme's public settings (or a note that the shop has no active programme), held in the browser's local storage so that the widget does not fetch them again on every page. It holds nothing about the visitor, and it is written on the first page the widget loads on, whatever the visitor's consent answer.No expiry date: it stays until the visitor clears the browser's site data; its content is fetched again once it is more than 5 minutes old
aopy_loy_<shop key>Loyalty programme widget only. The sign-in token of a shopper who signed in to the widget with a one-time code sent to their email address, held in the browser's local storage so that they stay signed in on later pages and visits. Written only after that sign-in.7 days from signing in; removed earlier when Aopy no longer accepts it, for example after the shopper is signed out of every device
aopy_loy_ref_<shop key>Loyalty programme widget only. The referral code carried by a link a customer shared with a friend, held in the browser's local storage so that it is still there when the visitor opens the widget on a later page. Written only when the visitor arrives through such a link.Until the invitation is claimed or dismissed; otherwise no expiry date
_aopy_push_sync, _aopy_push_declinedBrowser notifications (web push) only, held in the browser's local storage. _aopy_push_sync holds the time the browser's notification subscription was last sent to Aopy, so that it is sent again at most once every 7 days; it is written only after the visitor has allowed notifications in the browser. _aopy_push_declined holds the time the visitor postponed the notification prompt with its button for later, and the version of that prompt, so that the prompt is not shown again before the number of days you set, unless you change the prompt.No expiry date: it stays until the visitor clears the browser's site data
aopy-pushBrowser notifications only. A small database in the browser (IndexedDB) that the page shares with the Aopy notification service worker, holding your shop's public Aopy key and the public key that identifies Aopy as the sender of the notifications, so that the browser can renew its subscription when no page of your shop is open. It holds nothing about the visitor, and it is written only after the visitor has allowed notifications in the browser.No expiry date: it stays until the visitor clears the browser's site data
aopy_attribution_v1Shopify shops only, written by the Aopy storefront extension. The advertising click identifiers (such as gclid or fbclid) and the campaign tags (UTM) of the page the visitor arrived on, with the time they were captured, held in the browser's local storage so that they can be copied onto the Shopify cart and a later order credited to the click that led to it. Written only when the visitor arrives with such identifiers or tags, and not when the visitor has refused marketing through Shopify's Customer Privacy settings (or, while marketing is unanswered, refused analytics); on a theme without those settings nothing holds it back.No expiry date: it stays until the visitor clears the browser's site data; values older than 30 days are no longer used
aopy_attribution_sent_v1, aopy_aid_sent_v1Shopify shops only, written by the Aopy storefront extension in the browser's local storage, so that the same values are not copied onto the cart again on every page. aopy_attribution_sent_v1 holds the click identifiers and campaign tags last copied onto the cart, with the cart's reference. aopy_aid_sent_v1 holds the _aopy_aid visitor identifier last copied onto the cart, with the cart's reference; it is written only while the visitor's analytics consent stands (on a theme without Shopify's Customer Privacy settings, while the _aopy_aid cookie exists), and it is removed, together with the copy on the cart, once the visitor refuses analytics or the _aopy_aid cookie is gone.No expiry date: replaced on the next copy, and kept until the visitor clears the browser's site data; aopy_aid_sent_v1 is removed as described

A visitor who has not consented to cookies. For that visitor our code writes no cookie, and writes nothing at all when a sign-up window is merely shown. It keeps only the visitor's own choice — that they closed the window or signed up — as the cdm_popup_ marker in session storage, which ends with the browser tab. The countdown, reopen-button and cdm_visit_tab markers are not written. cdm_vpv and cdm_vseen are not written, so a window set to appear after a number of pages, or for first-time or returning visitors, is not shown to that visitor. Our code learns the visitor's answer in two ways: on Shopify storefronts it reads Shopify's Consent Tracking API, and writes a cookie only once the visitor has permitted analytics or preferences processing; on every other platform it follows the Aopy tracking script on the same page. On those other platforms, in Strict mode that script waits for your banner to report acceptance, so everything in this paragraph applies until then. In Anonymous and Legitimate interest modes the script does not wait for a banner: the cookie markers above are then written from the first page, unless the visitor has refused or their browser sends a Global Privacy Control or Do Not Track signal, and it is your banner and your own legal assessment that must cover them. Where neither is present — a sign-up window installed without the tracking script on a non-Shopify site — there is no consent signal for our code to read, so it writes the cookie and it is your banner that must gate it.

The three tracking consent modes. Your Aopy tracking settings decide how the events our script sends are handled on our side:

  • Strict (the default) — nothing is stored until the visitor has explicitly granted consent. This is the mode that matches the prior-consent rule above.
  • Anonymous — events are stored before consent, but with no link to an identified contact and with email, phone, name and address stripped out. This is not anonymity and it is not consent-free: the script can still set a session identifier, retry storage and an attribution cookie before the visitor chooses, and the visitor's IP address and browser details reach Aopy with each event. Use it only where your cookie banner covers this. A visitor who refuses is still counted, with the same stripped events. Once consent is granted, full events are stored.
  • Legitimate interest — events are stored unless the visitor has explicitly refused. Choosing this mode is a legal judgment you make as controller; discuss it with your adviser before relying on it, and note that it does not lift the separate consent requirement for storing the cookies above.

In all three modes, a browser-level opt-out signal (Global Privacy Control or Do Not Track) stops storage outright, and the refusal is recorded.

What you need to do. List the items above in your own cookie banner and cookie policy, in whichever category your legal adviser considers correct; make sure your banner actually blocks or defers our script when a visitor declines; and keep your Aopy tracking consent mode consistent with what your banner promises. On the ten-year figure, which applies where the sign-up window writes _cdm_aid: EU supervisory guidance commonly converges on a maximum of around 13 months for tracking identifiers. We are aligning _cdm_aid with that, and until we have, please account for the current values when you write your own policy. For reference, the anonymous browsing profile the identifier points at is deleted from our main database after 30 days; the pseudonymous journey events recorded under it are kept for up to 13 months in our analytics store (ClickHouse Cloud) and in the event lake, and are then deleted.

Aggregated statistics. Aggregated product and order statistics are kept for up to 25 months, for year-on-year comparisons, and are then deleted. They hold no person or browser identifier. The product statistics count the distinct visitors per product and per day as a summary figure that cannot be split per person. The order statistics (order_line_facts) hold order ids, so a row can be traced back to its order for as long as that order names a buyer in our main database. Cover this period in your own privacy notice.

On Shopify. The Aopy web pixel follows the answer in Shopify's Customer Privacy settings. A cookie banner that is not synced with those settings therefore cannot refuse the pixel: a refusal given in that banner does not reach it. Syncing your banner with them is a setting of your store, and it is yours to make.

12. Questions

We want compliant senders — it protects your subscribers, your brand, and the deliverability of everyone on the platform.

  • Platform questions (how to use consent fields, exports, deletion, unsubscribe settings): support@aopy.com
  • Data-protection questions (the DPA, sub-processors, data subject requests): privacy@aopy.com

Related documents: Data Processing Agreement · Privacy Policy · Sub-processors · Acceptable Use Policy · SMS Compliance · Cookie Policy

13. Language

This guide is published in English and 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?