Privacy Policy
1. Who We Are
Easy Life Tech SRL ("Aopy", "we", "us", "our") is a company incorporated in Romania, registered with the Trade Register under no. J2026033503008, fiscal identification code (CUI) 54742254, EUID ROONRC.J2026033503008, with its registered office at Șos. București-Ploiești, Nr. 15, Imobilul 2 - Spațiu Comercial, Etaj 5, Sector 1, București, Romania.
We operate the Aopy platform (the "Service"), a business-to-business (B2B) email and SMS marketing platform available at aopy.com and app.aopy.com. This Privacy Policy explains how we collect, use, disclose and protect personal data when you visit our websites, create an account, or use the Service.
Our two roles. For the personal data described in this Policy — your account data, billing data and data generated by your use of our websites — we act as a data controller. For contact data that our customers upload to the Service in order to run their own marketing campaigns ("Contact Data"), the customer is the data controller and we act as a data processor on the customer's behalf. Processing in our processor role is governed by our Data Processing Agreement, not by this Policy. If you have received an email or SMS sent through Aopy by one of our customers, that customer is responsible for the lawfulness of the communication; please direct requests to them first — we assist them in responding, as required by the Data Processing Agreement.
2. Data Controller and Contact Details
The data controller for the processing described in this Policy is Easy Life Tech SRL, Șos. București-Ploiești, Nr. 15, Imobilul 2 - Spațiu Comercial, Etaj 5, Sector 1, București, Romania.
Data protection enquiries and requests to exercise your rights are handled by our Privacy Team at privacy@aopy.com. For general support, contact support@aopy.com.
We have not designated a data protection officer; write to privacy@aopy.com.
3. What Data We Collect
a) Data you provide to us.
- Account data — when you sign up we collect your full name, company name, company website, email address and a password (managed through our authentication provider, Supabase Auth), whether you register as an agency, the versions of the Terms of Service and this Privacy Policy you accepted, and your marketing opt-in choice.
- Billing data — payments are processed by Stripe. We store only Stripe reference identifiers (customer, subscription, payment-method and invoice IDs) and a masked card reference (card brand and last four digits). We never store full card numbers.
- Public pages — when you submit a form on our public marketing site, or join the waiting list on our ROAS Calculator, we collect: your name, email address, phone number and company website; the answers you give in the on-page questionnaire and the buyer profile ("persona") derived from them; and, on the ROAS Calculator, your store address, marketing channel mix, reporting currency and interface language. We also record your marketing opt-in choice, which form you came from, and whether you have submitted one of our forms before. Collected automatically alongside these forms: the country derived from your IP address (we store the country, not the IP address itself) and your browser user-agent. Collected only with your consent, through the cookies described in our Cookie Policy: the identifiers of your visit (a session identifier and a lead-session identifier) and first-touch attribution data — the page address and campaign parameters of the visit that first brought you to us (analytics consent), and advertising click identifiers (marketing consent). The ROAS Calculator additionally generates an access token so that you can reopen your report from the link we email you.
- Who receives public-page data. Records created by these forms are also written to CMG Workflow, a customer-relationship management (CRM) system hosted in the European Union and operated by CMG FRAMEWORKS SRL, a separate Romanian company, so that we can follow up on your enquiry. CMG FRAMEWORKS SRL handles these records as our service provider.
b) Data collected automatically.
- Legal-acceptance records — when you accept our terms or policies, we record your IP address, browser user-agent and a timestamp in an append-only log, so that we can evidence what was accepted and when.
- Cookies — strictly necessary cookies are always set. On our public marketing pages (including the ROAS Calculator), analytics (Google Analytics 4) and marketing (Meta Pixel, TikTok Pixel) cookies are set only if you grant the matching category in our cookie banner, and never on the app dashboard. See our Cookie Policy for the full cookie table.
- Our own visit statistics on aopy.com — only if you grant the "Analytics" category, our own measurement script keeps a session identifier and the source of your visit in your browser tab (
aopy_mkt_sid,aopy_mkt_attr) and sends us the pages you view, the time spent on them, the referring page, the campaign parameters, the sections and prices you look at and the steps you take in our forms. From each request we derive your country and city, the type of device and browser, and a code computed from your IP address and browser that changes every day; we do not store your IP address. If you withdraw consent, the script stops and removes both items. - Technical data — our hosting and content-delivery provider processes request metadata (including IP address and user-agent) to serve the Service, and our error-monitoring provider processes error traces with partial request metadata so that we can diagnose faults.
c) Data we process on behalf of our customers (processor role). Our customers upload and generate the following data about their own contacts; the customer is the controller of this data:
- Contact Data — email addresses, phone numbers, names, demographic attributes (date of birth, gender, city/county/country), consent fields, custom fields, commerce statistics (orders, revenue, average order value) and engagement counters.
- Engagement events — per-contact email opens (timestamp, user-agent, IP address), link clicks (timestamp, URL, tags, user-agent, IP address), delivery, bounce and complaint events, and device type and display size derived from the open tracking pixel; SMS delivery receipts and inbound STOP messages.
- Storefront visitor data — when a customer installs our sign-up windows (popups) or tracking script on its own online shop: what visitors enter in those windows, the visitor-recognition cookies and pseudonymous visitor identifiers our code sets on that shop, page, product and checkout events, consent state, and, in raw intake, the visitor's IP address and user-agent. The shop decides whether and how to ask its visitors for consent; see our Data Processing Guidelines.
d) Data we receive from other sources.
- Connected accounts — when you connect your Google, Meta, TikTok, Shopify or Canva account, we receive from that provider the account identifiers and names, the access tokens, and the data the connection is used for (for example advertising performance figures, store, product and order data, or your designs), as described in Section 9.
- Meta catalog access — when a Meta Business admin approves Aopy's Meta catalog access (the approval screen says that Aopy keeps it), we keep that admin's Meta access token (encrypted) and Meta user and Business IDs. We use them only to create a Meta catalog per designed product set and share it with your connected Meta account (Art. 6(1)(b) GDPR). We never use them for ads, spending or any other data, and never share them. We delete them on Meta disconnect or ad-account change, when Meta refuses the token (the IDs within 7 days), after 90 days without use, or on request.
- Team invitations — when a member of a customer's team invites you, we receive from that person your email address and the role they give you in their organisation.
4. Legal Bases for Processing
Where we act as controller, we process personal data on the following legal bases under Regulation (EU) 2016/679 (the "GDPR") and Romanian Law no. 190/2018, which implements it:
- Performance of a contract (Art. 6(1)(b) GDPR) — creating and administering your account, providing the Service, and managing billing and subscriptions; and taking the steps you ask for before a contract, such as answering a form, waiting-list or ROAS Calculator request you send us.
- Legitimate interests (Art. 6(1)(f) GDPR) — our legitimate interests in keeping the Service secure, improving the product, preventing fraud and abuse, and evidencing acceptance of our legal terms. You may object to processing based on legitimate interests at any time (see Section 7).
- Legal obligation (Art. 6(1)(c) GDPR) — retaining invoices and fiscal records as required by Romanian tax and accounting law.
- Consent (Art. 6(1)(a) GDPR) — sending you our own marketing communications and setting non-essential cookies. You may withdraw consent at any time, without affecting the lawfulness of processing carried out before withdrawal.
Which data you must provide. To open an account you must give the details marked as required on the sign-up form (such as your name, email address and a password), because we need them to create the account and enter into the contract. To pay for a paid plan you must give billing details and a payment method; Romanian tax law requires the details we print on invoices. If you do not provide this data, we cannot open your account or take your payment. On our public forms, the fields marked as required are needed to answer your request; if you leave them out, we cannot answer it. Everything else, including marketing opt-in and non-essential cookies, is optional, and refusing it has no effect on your access to the Service.
5. How We Use Your Data
The table below maps our processing purposes to their legal bases:
| Purpose | Legal basis |
|---|---|
| Providing and operating the Service (account management, campaign sending, dashboards, support) | Contract (Art. 6(1)(b)) |
| Billing, invoicing and subscription management via Stripe | Contract (Art. 6(1)(b)); legal obligation (Art. 6(1)(c)) for fiscal records |
| Securing the Service, preventing fraud and abuse (including rate limiting and access controls) | Legitimate interests (Art. 6(1)(f)) |
| Recording your acceptance of legal terms (IP address, user-agent, timestamp) | Legitimate interests (Art. 6(1)(f)) — evidencing acceptance |
| Diagnosing errors and improving the product | Legitimate interests (Art. 6(1)(f)) |
| Answering a form you send on our public pages, the waiting list or the ROAS Calculator (including your questionnaire answers and the persona derived from them), and following up on that request | Steps at your request before a contract (Art. 6(1)(b)) for the reply; consent (Art. 6(1)(a)) for marketing follow-up, where we ask for it |
| Sending you our own marketing communications (only if you opted in) | Consent (Art. 6(1)(a)) |
Measuring visits to our public marketing pages (our own visit statistics, Google Analytics 4) and our advertising (Meta Pixel, TikTok Pixel), and recognising that you already sent us your details (aopy_lead_hint), each only for the cookie-banner category you grant | Consent (Art. 6(1)(a)) |
| Complying with legal obligations (tax, accounting, responding to lawful requests) | Legal obligation (Art. 6(1)(c)) |
The questionnaire persona. Your answers to the questionnaire on our public pages map to a persona label (the buyer profile named in Section 3), which we use to tailor our reply and our follow-up. There is no decision with legal or similarly significant effect based on it.
We do not sell personal data. We do not use your personal data for automated decision-making that produces legal effects concerning you or similarly significantly affects you.
6. Data Retention
We retain personal data for the following periods:
| Data category | Retention period |
|---|---|
| Account data | Life of the account, plus a 30-day grace period after account deletion is requested (during which the deletion can be reversed) |
| Contact Data processed on behalf of customers | Until the customer deletes it or the customer's contract ends; post-termination deletion is governed by the Data Processing Agreement |
| Marketing-form and waiting-list records collected on our public pages | 24 months from collection |
| Cookie-consent records (your choices in our cookie banner) | 24 months after the choice is recorded, then deleted (see our Cookie Policy) |
| Legal-acceptance records | For as long as we need them to demonstrate that the acceptance was validly obtained, reviewed annually. For account holders that means the life of the account. |
| Our own visit statistics on aopy.com (with your Analytics consent) | 90 days, after which we keep only daily totals that do not identify you |
| Email and SMS engagement events | 400 days on a rolling basis; per-recipient send records, including open and click times, until the contact or account is deleted. |
| Invoices and fiscal records | 10 years from the end of the financial year, as required by Romanian accounting law (Law no. 82/1991) |
| Security audit log of your account | For as long as the account exists |
| Support conversations and the messages and files in them | 24 months after the last message of a resolved or closed conversation, then deleted; open conversations are kept until they are resolved |
| Request and error logs held by our hosting and error-monitoring providers | For the retention period set in each provider's service |
When a retention period expires, we delete or irreversibly anonymise the data. For a closed account or an ended contract, we do this in a deletion run every month, within 90 days of the end. We also delete the copies our sub-processors hold under our control; other provider logs expire on the provider's schedule. You may request deletion of your data at any time via the Data Deletion Request form or by emailing privacy@aopy.com.
7. Your Rights
Under the GDPR you have the following rights in relation to personal data for which we are the controller:
- Access (Art. 15) — obtain confirmation of whether we process your data and receive a copy of it;
- Rectification (Art. 16) — have inaccurate data corrected and incomplete data completed;
- Erasure (Art. 17) — have your data deleted where there is no longer a legal ground to keep it;
- Restriction of processing (Art. 18) — limit how we use your data in certain circumstances;
- Data portability (Art. 20) — receive the data you provided to us in a structured, commonly used, machine-readable format;
- Objection (Art. 21) — object to processing based on our legitimate interests, and to direct marketing at any time;
- Withdrawal of consent — withdraw any consent you have given, at any time, with effect for the future;
- No solely automated decisions (Art. 22) — not be subject to a decision based solely on automated processing that produces legal or similarly significant effects.
How to exercise your rights. Email privacy@aopy.com or use the self-service forms at Data Deletion and Data Export. Requests are logged, your identity is verified, and we respond within one month, as required by Art. 12 GDPR.
If you received a message sent through Aopy by one of our customers: every marketing email sent through the Service carries an unsubscribe link, and marketing SMS can be stopped by replying STOP or DEZABONARE. For access, deletion or other requests concerning that data, contact the sender (the controller); we assist them in fulfilling such requests under the Data Processing Agreement.
Complaints. You 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, Romania — www.dataprotection.ro — or with the supervisory authority of your habitual residence or place of work.
8. International Data Transfers
Our primary infrastructure is located in the European Union: application data is stored with Supabase and Amazon Web Services in Ireland, and SMS messages for the Romanian market are delivered through a provider located in Romania.
Some of our sub-processors are US companies or process data in the United States — including our error-monitoring provider (a US company; our error data is stored in its EU region), our payment provider and the control plane of our hosting provider. Where personal data is transferred outside the European Economic Area, we rely on the European Commission's adequacy decision for the EU-US Data Privacy Framework (Decision (EU) 2023/1795) where the recipient is certified under it, and otherwise on the European Commission's Standard Contractual Clauses (SCCs, Implementing Decision (EU) 2021/914). We assess each transfer to a third country (a transfer impact assessment), including the law of the destination country and any additional measures needed, and we keep the assessment on file.
Analytics and advertising pixels. Only if you grant the matching category in our cookie banner, our public marketing pages load Google Analytics 4 (Google LLC), the Meta Pixel (Meta Platforms, Inc.) and the TikTok Pixel (TikTok). These vendors receive data about your visit, including your IP address, browser details and the pages you view, and may process it in the United States. Google LLC and Meta Platforms, Inc. are certified under the EU-US Data Privacy Framework; TikTok is not, so for TikTok we rely on the Standard Contractual Clauses. If you do not grant consent, none of these pixels loads. See our Cookie Policy.
You can ask for a copy of the relevant safeguards (the Standard Contractual Clauses that apply to a transfer, or the recipient's Data Privacy Framework certification) by writing to privacy@aopy.com.
AI generation features and US providers. The Service includes optional AI generation features — image generation, analysis of a brand guide you upload, and drafting of marketing copy — which use a US-based provider (OpenAI). What is sent is the prompt, product image or brand asset you supply for that feature — never Contact Data. The in-app support assistant uses the same provider to draft a first answer to a support message you send us: what is sent is the text of your message together with configuration facts about your own workspace (your sending domain and its DNS status, SMS credit balance, active modules with their price and trial state, which billing rail charges you, onboarding step and account-health warnings) — never Contact Data, never campaign or message content, and nothing about your own customers or their orders. Each customer organisation can disable this US-based AI processing entirely through an organisation-level setting; when the setting is disabled, no data is sent to that provider for any of these features. Image background removal uses a separate provider contracted in Austria and is covered by the same setting; see the Sub-Processor register.
Claude and ChatGPT connector. If you connect Aopy to Claude (Anthropic) or ChatGPT (OpenAI), you sign in with your own Aopy account, approve the connection and choose the organisation it can reach. From then on, when you ask in that chat, Aopy returns the result to the provider so it can answer you: for example campaign, segment, revenue, order and product figures. Contact email addresses and phone numbers are masked by default; an owner or admin can ask for the full email address of one contact at a time. Aopy sends nothing on its own and never your password, and a campaign is sent only after you confirm it in the chat. These providers are in the United States and handle the results under their own terms and privacy policy for your account. The organisation-level setting that disables US-based AI processing (above) also disables this connector: while that setting is disabled, no one can connect Claude or ChatGPT to that organisation and Aopy refuses every request from a connection already made, so nothing is sent to these providers through the connector. You can stop access at any time in the Aopy app (Tracking → Configuration → Advanced → Aopy in Claude and ChatGPT), after which the provider can no longer reach your data, and you can also remove the connector in Claude or ChatGPT. See the Sub-Processor register.
9. Sub-Processors and Service Providers
We use a limited set of vetted service providers (sub-processors) to operate the Service — including infrastructure, email delivery, database and authentication, hosting, payments, queueing and rate limiting, error monitoring, SMS delivery, invoicing, web-font delivery, optional AI generation features and the in-app support assistant. The complete, up-to-date register — including each provider's purpose, the data involved and its processing location — is published at Sub-Processors.
We update that page when we add or replace a sub-processor. For customers, the notice and objection mechanism for sub-processor changes is set out in the Data Processing Agreement.
Where you connect optional third-party integrations to your account (such as Meta, TikTok, Google Ads/GA4, Shopify or WooCommerce), data flows to those providers on your instruction, under their own terms and privacy policies. When you confirm it on a preview, we set your Google Ads account's tracking suffix to the UTM values you chose in Aopy, and for each Meta ad you select we create a copy of its creative (same post, with those UTM values in its URL tags) and switch the ad to that copy, and for each TikTok ad you select we put those UTM values in its landing page link. Those Meta and TikTok ads go back into the platform's review. Nothing else on those ads changes.
Google user data (Google Merchant Center and Google Ads). If you connect your Google account, Aopy's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We request two scopes. auth/content is used only to (a) read your own Merchant Center account ID, in order to confirm and store the connection, and (b) create and update product listings in your own Merchant Center account, and only when you explicitly trigger an export in Aopy. auth/adwords is used for reporting and, only on your instruction, for managing that account: at connection we call listAccessibleCustomers to identify the Google Ads account you authorised, and thereafter run read-only reports that return per-product cost, impressions, clicks, conversions and conversion value for that account, which we show back to you as per-product advertising performance. If you turn them on under Channels > Google > Automations, we also (a) create ad groups, responsive search ads and keywords, one per product, in a Search campaign you choose, written from your product catalogue (product names, descriptions, brand, category and price are sent to OpenAI to write the ad text; no personal data is sent); (b) read your campaigns' hourly spend to alert you when a campaign spends far more than usual; and (c) read the landing-page addresses of your active ads and check whether they load. We never create campaigns, change budgets or bids of existing ad groups, or spend money on your behalf beyond the ad groups you asked for. Apart from the ad groups and ads you asked for, we never create, pause or delete campaigns or ads, or change bids or budgets. The one other change we make is your account's tracking suffix (Final URL suffix), set to the UTM values you chose in Aopy, only after you confirm it on a preview. We store your Merchant Center account ID, the Google Ads customer ID, name and currency of the account you authorised, the daily per-product performance figures described above, and the OAuth access and refresh tokens, encrypted at rest with AES-256-GCM. We do not use Google user data for advertising, we do not sell it, and we do not transfer it to third parties except as needed to provide these features at your instruction or where required by law. We never access Google data belonging to any account other than the one you connect. You can revoke access at any time by disconnecting Google inside Aopy, or from your Google Account permissions page.
Canva. If you connect your Canva account, Aopy reads the list of your Canva designs (titles, thumbnails, page counts) so you can pick one, exports the pages you choose as images or as email HTML, and stores those exports in your Aopy library. When you use "Send to Canva", the image you selected is uploaded to your own Canva uploads. We store your Canva user id, team id and display name, the OAuth access and refresh tokens (encrypted at rest with AES-256-GCM), and the id and title of each design you imported. We never access designs belonging to any Canva account other than the one you connect, we do not use Canva data for advertising and we do not sell it. You can revoke access at any time by disconnecting Canva inside Aopy or from your Canva account's connected apps.
10. Security
We apply technical and organisational measures appropriate to the risk of the processing, including:
- Multi-tenant isolation — every database table is scoped to a customer organisation and protected by PostgreSQL Row-Level Security, with JWT-based access context;
- Encryption in transit — TLS on all connections (HTTPS enforced);
- Encryption at rest — at the infrastructure level; integration credentials and OAuth tokens are additionally encrypted at the application level with AES-256-GCM;
- Access controls — role-based permissions, an administrative allowlist, and signed authentication for scheduled jobs and webhooks (HMAC signature verification on inbound webhooks);
- Audit trails — append-only logs of consent and legal acceptances;
- Resilient sending architecture — message queues with no shared mutable state;
- Organisational measures — documented information-security management practices covering scope, risk treatment, supplier security and personnel security.
No system is perfectly secure; if we become aware of a personal data breach affecting your data, we will act in accordance with our GDPR obligations, including notification where required.
11. Cookies
Strictly necessary cookies are always set: a first-party cookie storing your cookie-consent choices and the authentication session cookie set by our auth provider. On our public marketing pages (including the ROAS Calculator), we also use Google Analytics 4 for analytics and the Meta Pixel and TikTok Pixel for marketing — set only once you grant the matching category ("analytics" or "marketing") in our cookie banner, and never on the app dashboard. With the "analytics" category we also run our own visit statistics on aopy.com (Section 3(b)). The "functional" category covers one cookie, aopy_lead_hint: it is set only if you grant that category, holds a masked form of the address you gave us so a page can show that we already have your details, and is removed when you withdraw that consent.
Full details, including the exact cookie table and how to manage your preferences, are in our Cookie Policy.
12. Children
The Service is a business-to-business platform and is not directed at children. We do not knowingly collect personal data from persons under the age of 16, and our customers are contractually prohibited from uploading Contact Data relating to persons under 16. If you believe a child's data has been provided to us, contact privacy@aopy.com and we will delete it.
13. Changes to This Policy
We may update this Policy from time to time. Each version of the Policy is identified by a version date, and your acceptance of it is recorded. If we make material changes, we will notify you by email or by a prominent notice in the platform, and where the changes require it, you will be asked to review and re-accept the updated Policy before continuing to use the Service. The "Last updated" date at the top of this page reflects the most recent revision.
14. Contact
For questions about this Policy or about how we handle personal data, contact our Privacy Team at privacy@aopy.com. For general support, contact support@aopy.com.
Postal address: Easy Life Tech SRL, Șos. București-Ploiești, Nr. 15, Imobilul 2 - Spațiu Comercial, Etaj 5, Sector 1, București, Romania.
15. Language
This Policy is drawn up in English and in Romanian. The English version is the canonical version: in the event of any inconsistency between the two language versions, the English version prevails.