LEGAL
Privacy Policy
1. Who we are
Aplon Ltd ("we", "us", "our") is the data controller responsible for your personal data. We are incorporated in Cyprus. Our address is: Agiou Andronikou 21, 5350 Frenaros, Cyprus.
This Privacy Policy applies to all personal data collected through our platform at app.aplon.io, our marketing website at aplon.io, and any related services. For all privacy enquiries, contact us at contact@aplon.io.
We act in two different roles, and it matters which. For data about you — your account, your billing, how you use Aplon — we are the controller and this policy explains what we do with it. For data about your customers, which reaches us from your Shopify store and your connected tools, you are the controller and we are your processor: we handle it only to produce your analytics, on your instructions. Sections 2.2 and 4 set out what that means in practice, and our Data Processing Agreement is the GDPR Article 28 contract that governs it. It is already in force — it forms part of our Terms of Service, so there is nothing for you to sign.
2. Data we collect and how we collect it
2.1 Account data
Your email address and, if you provide it, your name — collected when you create an account or sign in. We store your account creation date, last login, plan status, and notification preferences.
You can sign in with a one-time passcode sent to your email, or set a password. If you set one, we store it only as a salted PBKDF2 hash — we never store or have access to the password itself, and we cannot recover it for you. If you turn on two-factor authentication, we store the secret your authenticator app uses, and your recovery codes as hashes. We also record the devices with active sessions on your account so you can sign them out individually.
If you open Aplon inside your Shopify admin for the first time as the store owner and stop before agreeing to our Terms, or at the step that asks for a code sent to your email address, we keep a short record: your store's myshopify.com address, the number Shopify uses for you, the step you stopped at, whether Shopify had confirmed your email address, and when we first and last saw you. It holds no email address and no name. We use it to find and fix the places where setting up Aplon goes wrong. If you later agree, we add when you agreed and link the record to your new account. If you never agree, we delete it 90 days after we last saw you.
2.2 Shopify store data
When you connect a Shopify store, we request OAuth access and receive a Shopify access token. We use this token to read your store's order history, product catalogue, customer information, and revenue data via the Shopify Admin API. We store your store domain, shop name, and the encrypted access token. We do not store payment card numbers or Shopify customer passwords. If you use Aplon inside your Shopify admin, we also keep the number Shopify uses for the store's owner, so we can tell the owner from the store's staff.
To keep your analytics fast, we maintain a copy of your store's order and product data in our database, refreshed automatically. This includes personal data about your customers — name, email address, location (country, region, city), order history, and visit or attribution data (such as referring source and landing page) — which we process solely on your behalf to generate your analytics (for example, customer lifetime value, repeat-purchase, and sales-by-region insights). For this customer personal data, you are the data controller and Aplon is your data processor. We do not sell it or use it for our own marketing. It is encrypted, access is restricted and logged, and it is deleted when you delete your account, when you uninstall the app, or on a valid deletion request — including a deletion request Shopify forwards to us on a shopper's behalf.
2.3 Storefront analytics pixel
When you connect a store, Aplon installs a first-party analytics pixel on your Shopify storefront so we can give you traffic, funnel, and marketing-attribution analytics. This pixel collects, from visitors to your storefront: page views and page URLs, referrer, UTM parameters (source, medium, campaign, content, term), device type, approximate location (the country, region and city, and that city's map coordinates, worked out from the IP address, which is not itself stored), and completed-purchase events (the Shopify order ID). It also records the advertising click identifiers an ad platform adds to a link (for example fbclid or gclid), so you can see which ad an order came from, and, when a shopper is logged in to your store, their Shopify customer ID, so their visits on different devices can be joined up. To tell one visitor's visits apart from another's it uses the random browser identifier that Shopify's own analytics already assign, and a session identifier kept only in memory; it writes nothing to the visitor's browser storage itself (section 3.5). The pixel does not collect names, email addresses or payment details. It is used for traffic, funnel and ad-attribution analytics for you; it is not used for retargeting or audience building, and the data is never sold or shared with advertising platforms.
The pixel is installed and collects on every plan, including a plan that shows only some of its figures, or none of them. On such a plan we keep what it collects on the same terms and for the same period (section 7), so the history is already there if you move to a plan that shows it. Nothing about what the pixel collects, or the consent it waits for, depends on your plan.
How the location is worked out. Our servers see the visitor's IP address, as any web server does, and use it only to work out an approximate location. We do not store the IP address. Usually the country comes from a header our hosting or CDN provider already adds. Where it does not, we send the IP address to a geolocation provider (ipinfo.io, or ipapi.co as a fallback) to resolve it, and cache the answer briefly. Those providers are listed in section 5 and receive nothing else. The region, city and coordinates come from a geolocation database we keep on our own servers, so working them out sends the address nowhere. The coordinates are the city's, the same for everyone in it, not the visitor's own position.
The pixel respects shopper consent. Where you (the merchant) have enabled consent collection on your storefront, the pixel integrates with Shopify's Customer Privacy API and does not read or store any identifier, or send any event, until the shopper has given the consent Shopify asks for on our behalf, which covers analytics and marketing; if a shopper later grants consent, tracking begins from that point. The data collected belongs to you as the merchant and is used solely to produce analytics within your Aplon account, now or after you move to a plan that shows them.
2.4 Meta Ads integration data
If you choose to connect a Meta Ads account, you will be directed to authenticate via Meta's OAuth flow and will be asked to grant Aplon permission to read and, on plans that include ad management, change your ad account data. Upon connection, we receive and securely store an access token issued by Meta.
Using this token, we access the following data from Meta's Marketing API on your behalf:
- Ad account names and IDs
- Campaign, ad set, and ad names and IDs
- Ad performance metrics: spend, impressions, clicks, reach, frequency, CPM, CPC, CTR, ROAS, and conversions
- Attribution data associated with your ad campaigns
We do not access your personal Facebook profile, private messages, friends list, or any data outside of your connected ad accounts. You can disconnect your Meta Ads account at any time from the Settings page, which will revoke our access and delete your stored token. You can also revoke access directly from your Meta Business Settings.
Meta ad data accessed through our integration is used solely to provide you with advertising performance analytics within the Aplon platform. It is not sold, is shared only with the sub-processors in section 5 that run the service, and is not used for any purpose other than delivering the service to you.
Changes we make when you ask us to. On plans that include ad management, Aplon can act on your connected ad accounts at your instruction: pausing or resuming ads, changing budgets, and adding tracking parameters to ad destination URLs. These are writes to the live platform, not analytics. We record who made each change and when, in a log you can read in the Ads view. Aplon never changes an ad on its own initiative.
2.5 Google Ads integration data
If you choose to connect a Google Ads account, you will authenticate via Google's OAuth flow and grant Aplon access to your Google Ads account data. We access campaign performance metrics (spend, impressions, clicks, conversions, ROAS) to provide analytics within the Aplon platform, and — on plans that include ad management, and only at your instruction — make the same kinds of changes described above for Meta. The same access, storage, and deletion principles apply. You can disconnect at any time from Settings or directly from your Google account permissions.
2.6 Snapchat Ads integration data
If you connect a Snapchat Ads account, we store an access token issued by Snapchat and use it to read campaign, ad set, and ad performance metrics for advertising analytics. The same access, storage, and deletion principles apply. You can disconnect at any time from Settings.
2.7 Klaviyo integration data
If you connect Klaviyo, you give us a Klaviyo private API key, which we store encrypted at rest. We use it to read your account, campaign, flow and metric data — including aggregate engagement data about your subscribers, such as opens, clicks and revenue attributed to a campaign — in order to produce your email marketing analytics. Where you enable a feature that requires it, we may also write events back to your Klaviyo account. As with your Shopify customer data, you are the controller of this data and we are your processor. You can disconnect at any time from Settings, which deletes the stored key, and you can revoke the key from within Klaviyo.
2.8 Billing data
If you subscribed through our website, payments are processed by Stripe and we store your Stripe customer ID, subscription plan, billing status, and transaction history. If you installed Aplon from the Shopify App Store, your subscription is billed by Shopify and we store the Shopify charge identifier and your plan status instead. In neither case do we store payment card numbers, CVV codes, or bank account details — those are held by Stripe or by Shopify under their own PCI DSS compliance programmes.
2.9 Usage data
We collect data about how you interact with the Aplon platform, including pages visited, features used, Aplo AI chat messages and responses, Aplo request counts, error logs, and session metadata (browser type, device type, IP address, timestamps). This data is used to operate, maintain, and improve the service.
2.10 Push notifications and communications
If you enable push notifications, we store your browser push subscription endpoint and encryption keys to deliver notifications to your device. If you subscribe to email digests or AI insights, we store your email preferences. You can withdraw consent for both at any time from the Account page.
If you ask to be told when a plan opens, we keep your email address and what you asked for, and use it for that alone. You can ask us to remove it at any time (section 14).
Product news and offers. If you enter your email address on our website, or tick the box when you accept a demo invite, we send you an email asking you to confirm, and we add you to our list only after you press the button in it. If you sign up for an account, you can tick the box on the signup form, or on the first screen if you open Aplon inside Shopify, and you can change your choice in Settings at any time. We keep your address, when you agreed and the words you agreed to. Every email has a link to unsubscribe. If you unsubscribe, an email bounces, or you report one as spam, we keep your address so that we do not email you again, unless you sign up again. Our emails come from hello@news.aplon.io, and a reply reaches our support team (section 2.14).
If your paid plan ends, we may email you an offer to come back, about ten days later. We do not send it if you have turned off marketing emails or left the box unticked when you signed up.
2.11 Measuring our own marketing
We measure how our marketing website (aplon.io) performs in three ways. The first is our own first-party analytics, described in section 3.3: it records page visits, whether a visit was an engaged one (see below), and how far a visit got through signing up. On our blog posts it also records how far down a post you scrolled (a quarter, half, three quarters, the end) and whether the post was still open in front of you after 30 seconds, 1, 2 and 5 minutes. That data goes to our own servers, and none of it is sent to Meta or Google. With each of these, our server also notes the country your visit comes from, the kind of device, and the details your browser gives about itself (its name, version and language), but never your IP address. The browser details are kept only in our server logs, for up to 90 days (section 7), so that we can tell visits by people from visits by automated programs and leave the second out of our figures.
The second is the Meta pixel. We advertise Aplon on Facebook and Instagram, and the pixel is what tells us whether those ads work. If you allow it, a small script from Meta runs on aplon.io and reports four kinds of event to Meta: that you viewed a page, that you spent time on one and interacted with it, that you started a free trial, and that you asked to connect your Shopify store. The second of those is sent once you have been on a page for fifteen seconds and scrolled, clicked or typed — it tells us whether an ad brought someone who read the page rather than someone who bounced. Meta may connect those events to your Facebook or Instagram account, use them to measure and improve the ads we run, and use them to show you our ads again elsewhere on their platforms. Meta acts as an independent controller for that data under its own terms, which is why it appears in the table in section 5 as a recipient rather than as one of our sub-processors.
When the pixel is allowed to run, our own server also sends Meta those same events directly, through Meta's Conversions API, so that an ad blocker which stops Meta's script does not hide whether our ads work. With each one, Meta receives the event and the time it happened, the address of the page, your IP address and the details your browser gives about itself, and the Meta cookie identifiers described in section 3.4 if your browser holds them. No name or email address is sent this way. The pixel and our server give each event the same identifier, so Meta counts it once, and Meta uses these events in the same ways as the pixel's. When the pixel is not allowed to run, our server sends Meta nothing.
The third is Google Analytics. If you allow it, a script from Google runs on aplon.io and reports four kinds of event to Google — the same four as the Meta pixel: that you viewed a page, that you spent time on one and interacted with it, that you started a free trial, and that you asked to connect your Shopify store. With each, Google receives the address of the page, details of your browser and device, and an approximate location it works out from your IP address. Google produces our website's visitor statistics from it. It is also set up for Google's advertising features: Google may connect those events to your Google account, and use them to measure the ads we run with Google and to show you our ads again on Google's services. For the statistics Google processes the data for us; where it uses the data for its own advertising purposes it acts as an independent controller under its own terms, which is why it appears in the table in section 5 as a recipient rather than as one of our sub-processors.
When they run. In the EU and the UK — or if we cannot tell where you are — the Meta and Google scripts are not loaded, and no Meta or Google cookie is written, until you choose "Accept all" in our cookie banner. Elsewhere they start when you arrive, the same rule section 3.3 sets out for analytics, and our banner lets you switch them off. Choosing "Essential only" at any time stops both, withdraws consent with Meta and with Google, and deletes their cookies from your browser. We also honour Global Privacy Control (section 10.4): with it on, the scripts do not load unless you choose "Accept all".
We do not use any other third-party advertising or analytics technology on aplon.io. There is no advertising technology of any kind on app.aplon.io, and Google Analytics does not run there — the scripts described here run on the public marketing site, never inside the product. The first-party storefront pixel described in section 2.3 is a separate tool installed on merchant storefronts. It measures which of the merchant's own ads and campaigns led to orders; it is not used to show ads to anyone, and its data is never sent to advertising platforms.
We measure our listing on the Shopify App Store with the same Google Analytics account and Meta pixel. We give Shopify their identifiers, and Shopify's page reports to Google and Meta that you viewed the listing, clicked to install Aplon and finished installing it. Shopify runs that page, so our cookie banner does not appear there, and Shopify's own privacy policy applies to it.
2.12 Connecting your own AI assistant (Mialōn)
If you choose to, you can connect Aplon to an AI assistant you use yourself, such as Claude or ChatGPT. You start this from the assistant, and you agree to it on an Aplon page that shows exactly what the assistant will be able to read. Once connected, it can read the analytics Aplon shows you for the stores you pick: sales, profit and loss, orders, products and costs, inventory, customers, reviews, email and ad performance. It cannot change anything in Aplon, in Shopify or in your ad accounts. Customer names and email addresses are withheld unless you tick the box to share them for that store.
What the assistant reads is sent to the company that provides it, because you have asked us to. That company is not one of our sub-processors: it handles the data under its own terms and your settings with it, including whether your chats may be used to train its models.
We never receive your conversation with the assistant, only its requests for data. We do not keep those requests, apart from a short-lived list of which screens it read and for which dates, held in memory to show you on the Mialōn screen. We do keep a record of each connection: who agreed, to which stores and to what wording, when and from where, and when it was last used. We keep that record after you disconnect, as proof of what was agreed. You can disconnect an assistant, or stop it reading one store, at any time from Mialōn in Aplon, and it stops on its next request.
2.13 Aplon Lens (Chrome extension)
Aplon Lens is an optional Chrome extension. It shows your Aplon figures (such as sales, revenue, return on ad spend, cost per sale, profit, and first-click and last-click purchases) next to each campaign, ad set and ad in Meta Ads Manager, and next to each campaign in Google Ads. It is read-only: it never changes anything in Aplon, in Meta or in Google. It is not made, endorsed or reviewed by Meta or by Google.
What it reads. Nothing until you press Connect in the extension's menu. After that, on app.aplon.io it reads the sign-in session the Aplon app already keeps in your browser, so that it can ask Aplon for your store's figures. On Meta Ads Manager and Google Ads pages it reads, from the page you are looking at: the ad account number, the date range you have chosen, the ID and name of each campaign, ad set and ad on screen, and where the table sits on the screen. It uses these inside your browser only, to put each Aplon figure on the right row.
What it sends, and where. Only to Aplon (api.aplon.io), over an encrypted connection: the date range, together with your Aplon session, to fetch the figures Aplon already holds for your store. It does not send the ad account number, the names, the numbers or any other content of Meta's or Google's pages anywhere, and it makes no request to any other server. It contains no analytics and no advertising.
Problem reports. If you press Not working? Copy a report, the extension copies a short technical description to your clipboard: its version, which page of Ads Manager or Google Ads you were on, the ad account number and dates, your Aplon store's name, your column choices, how many rows it found, and the layout of the table with numbers masked and no campaign names. It is not sent anywhere; it reaches us only if you paste it to us yourself.
What it keeps. Your Aplon session, the fact that you pressed Connect, and a list of which ad accounts showed figures last time are stored in the extension's local storage in your browser. Your choices of columns, of first-click or last-click, and whether the columns are hidden are stored in Chrome's sync storage, which Google copies between your own browsers if you have Chrome sync turned on. Pressing Disconnect deletes the session, the Connect choice and the account list; removing the extension deletes what it stored on that computer.
Aplon's use of information received through the Aplon Lens extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
2.14 Support requests and live chat
When you contact us — through the form or the live chat on our website, by email, or from Support in the app — we keep what you send us and our replies: your email address, your name if you give it, your messages and any files you attach. We use them to help you, and to keep a record of what we said.
In live chat, Aplo, our AI assistant, answers first, from our help articles. To do that, your messages are sent to Anthropic, which provides the AI model (section 5). If you ask for a person, someone from the team replies in the chat if they are free, or by email if not — on our website we ask you for the address — and the conversation becomes a support request. We keep live chats for 30 days, so that we can see what Aplo could not answer and improve our help articles (section 7).
2.15 Reviews of Aplon
If you leave us a review, we keep your star rating and the words you wrote, your name and your store's name if you chose to give them, an email address if you gave one, and a record of the exact consent wording you agreed to and when.
You can give your consent on our form, or by replying to an email in which we ask for it. If you left a review of Aplon on the Shopify App Store, we may email you to ask whether we can show it on aplon.io, and we only show it if you agree. If you agree by email, we keep a copy of your reply as the record of what you agreed to.
If you pay for Aplon, we may email you once, about three days after your first payment, to ask for a review. We do not send it if you have turned off marketing emails or left the box unticked when you signed up, and we do not ask again.
We show your review on aplon.io only if you agreed to it. Your stars count towards the rating shown there from the moment you agree, whether or not we quote your words, and your name appears only if we quote you. We leave a review out of the rating only if it is spam, abusive or not about Aplon.
We keep all of it while your review counts towards that rating or is quoted on aplon.io, and for three years after that. If a review never counts and is never quoted, we delete it three years after you send it, or three years after we copied it from the Shopify App Store. A daily job does the deleting, including any copy of your email reply.
Our legal basis for using your review on aplon.io is your consent. For the one email asking you for a review, it is our legitimate interest in hearing from the people who pay for Aplon, and you can turn that email off at any time. You can withdraw your consent at any time, using the "Take my review down" link in your review email or by writing to support@aplon.io. Your review then stops counting towards the rating and comes off the page.
2.16 Case studies
If we ask you to take part in a case study and you agree, we keep the name, store name and figures you agreed we could use, the draft we sent you and your approval of it, an email address so we can reach you, and a record of the consent wording you agreed to. We publish nothing until you have read the draft and said yes. You can have a case study taken down at any time by writing to support@aplon.io. If it goes up, we delete our record three years after it comes down. If it never goes up, we delete it three years after our last contact with you about it.
2.17 Demo invites
If someone at Aplon invites you to look at our demo, we keep your name and email address, the name and email we typed when we made your invite, the exact words you agreed to and when, when your 30 minutes started and ended, and when you were last active during the visit. We also keep whether you ticked the box for news.
For 90 days after your visit we also keep your IP address, the name of your browser and how many questions you asked Aplo, so that we can tell a real visit from misuse of a link. We do not record which pages of the demo you opened. To answer a question you ask Aplo, the question is sent to Anthropic, which provides the AI model (section 5), and we do not keep the question or the answer. The demo shop and its figures are invented; nothing in it is about real people.
We keep this so we can show who agreed to what, and so that we can enforce that agreement. Our legal basis is the agreement you made with us, and our legitimate interest in being able to prove it and in stopping misuse. We delete it five years after your visit. If you never use your invite, we delete it 30 days after we made it. You can ask us about it, or to delete it, at any time (sections 9 and 14). If we still need it to enforce the agreement, we will tell you.
If you tick the box for news and offers, section 2.10 applies.
2.18 Stores we contact first
Someone on our team may write to a store that does not use Aplon, to offer it Aplon. We write only to stores that we can see advertising on Meta, from Meta's public Ad Library, and only to a business email address that the store shows on its own website. We do not buy lists of addresses, we do not guess addresses, and we do not use a program to collect them. Each email is written and sent by a named person on our team, from an address at aplon.io or useaplon.com, and says who we are, where we found the address and how to stop.
We keep the store's name and web address, the country it is in, the email address we wrote to, the name of the person it belongs to if the address or the store's website shows it, the page where we found the address, the date, and a picture of that page to show where we found it. For a store in the United Kingdom we also keep its company number. We keep the emails we send and any reply.
Our legal basis is our legitimate interest in offering a tool for running a store to businesses that already advertise online. We send one email, and at most one more if there is no reply.
If you do not want to hear from us, reply "stop" to any of our emails, or write to contact@aplon.io. We will not write to you again. You can object at any time, for any reason (section 9). So that we never write to you again, we keep the email address and the store's web address on a list of people not to email, and we delete everything else about you. If you do not reply, we delete what we keep six months after our last email. Our email, and the record of who we wrote to, is held by Google (section 5).
4. How we use your data and our lawful bases
Under the EU General Data Protection Regulation (GDPR), we must have a lawful basis for each way we use your personal data. The table below sets out our processing activities and the lawful basis for each:
| Purpose | Lawful basis |
|---|---|
| Providing the analytics dashboard and Aplo AI assistant | Contract performance |
| Processing subscription payments via Stripe | Contract performance |
| Sending transactional emails (receipts, alerts, account notifications) | Contract performance |
| Fetching and displaying data from the ad and marketing accounts you have connected | Contract performance |
| Carrying out ad changes you instruct — pausing ads, changing budgets, tagging destination URLs | Contract performance |
| Diagnosing bugs, monitoring performance, improving the service | Legitimate interest |
| Authorised staff accessing your account to operate, support, and improve the service | Legitimate interest |
| Answering your support requests and live chats, and keeping a record of what we said (section 2.14) | Legitimate interest |
| Asking customers who pay for Aplon, once, by email, to review Aplon (section 2.15) | Legitimate interest |
| Giving you a demo you were invited to, keeping a record of what you agreed to, and stopping misuse of demo links (section 2.17) | Contract performance, and legitimate interest in being able to prove and enforce the agreement and in stopping misuse |
| Measuring how our own website performs, using first-party analytics | Consent in the EU and UK; legitimate interest elsewhere, which you can turn off |
| Measuring our Meta ads and showing them to you again, using the Meta pixel (section 2.11) | Consent in the EU and UK; elsewhere it runs unless you turn it off |
| Showing reviews of Aplon on our website, and writing case studies | Your consent, which you can withdraw at any time (section 2.15) |
| Measuring our website and our Google ads, and showing our ads to you again, using Google Analytics (section 2.11) | Consent in the EU and UK; elsewhere it runs unless you turn it off |
| Sending weekly digests, Aplo AI insights, and push notifications | Consent |
| Sending product news and offers to people who agreed (section 2.10) | Consent |
| Emailing a customer whose paid plan has ended with an offer to come back (section 2.10) | Legitimate interest |
| Sending one email to confirm an address entered on our website, or ticked inside Shopify where the address is not yet confirmed, and keeping that address for up to 30 days (section 2.10) | Legitimate interest |
| Keeping the address of someone who unsubscribed, or whose email bounced or was reported as spam, so that we do not email them again (sections 2.10 and 2.18) | Legitimate interest |
| Writing to a store that does not use Aplon, at a business address it shows on its own website, to offer it Aplon (section 2.18) | Legitimate interest |
| Keeping a short record when a store owner stops before agreeing to our Terms inside Shopify, to find and fix where setting up Aplon goes wrong (section 2.1) | Legitimate interest |
| Complying with legal obligations (tax, accounting records) | Legal obligation |
Staff access to your account. To operate, support, troubleshoot, and improve the service, a limited number of authorised Aplon personnel may access your account and view the data in it — including your store analytics and the personal data described above — for example to reproduce a problem or check that a new feature displays your data correctly. Such access is read-only, restricted to authorised personnel, and recorded in an internal access log. We rely on our legitimate interest in providing and improving a reliable service, balanced against your rights. We do not use this access to alter your data.
We do not sell your personal data to third parties. We do not use your store data, ad account data, or Aplo chat history to train AI models.
5. Sub-processors and data sharing
We share data with the following sub-processors solely to operate the service. Each operates under its own privacy policy and, where required, a Data Processing Agreement with us. This table is the single maintained list, and our Data Processing Agreement commits us to 30 days' notice before it changes.
| Sub-processor | Purpose | Location |
|---|---|---|
| Supabase | Database and authentication hosting | EU |
| Anthropic | AI model behind Aplo and the features built on it: chat, the weekly digest, Store Audit, review themes and suggested replies to reviews, a suggested first answer to support requests, drafting a first reply to a support request for our staff to send, and Aplo's answers in live chat on our website and in the app; drafts of our status page's updates when our checks record an outage; and an internal assistant our own staff use to answer questions about accounts and how the service is used. Store data (including figures from ad accounts you connect), chat and support messages, and the text of reviews from review apps you connect, with the reviewer's name, are sent to Anthropic's API. When our staff ask Aplo to draft a reply to a support request, it is also sent your first name, our staff's own notes on that request, which are never shown to you, and your saved context when you opened it; and, only while the request is open, your store's address, plan and whether it is billed monthly or yearly, whether Stripe or Shopify bills you, billing status, trial end date, cancellation date, when you last used Aplon, and your order sync's state, the date it last synced your orders and whether it had an error. Any other person's email address or phone number in the conversation becomes [email] or [phone] first. For a status-page draft it is sent the times our checks recorded and the error messages our systems logged during the outage, with email addresses, Shopify store addresses, account IDs, IP addresses and keys removed first; a person at Aplon approves every draft before it is published. When our staff ask that internal assistant about your account, it is sent the records about you that those staff can see in our admin console, including: your account details (name, email, plan and billing status, when you signed up and were last active, how you found us, and whether two-factor sign-in is on); your stores' names, web addresses and countries; the email addresses of people you invite to your team, and the teams you belong to; your sign-in history (each signed-in device's browser details and IP address, and when it was last used); how you use the service (which tools you open and for how long, how much you use Aplo, how far you are through setting up, and error messages our systems recorded); your billing and account history, including actions our staff have taken on your account and, if you closed it, the reason and any note you gave; and your store's figures. Your customers' names, emails, phone numbers and addresses are never sent: they are removed first. If you are an affiliate partner, it can also be sent your name, email, website, country, referrals (including the email addresses of the merchants you referred), commissions and payouts, but never your bank details or tax number. Our free Competitor Ads tool also sends it the public text of other brands' ads from Meta's Ad Library, to group them by message, and nothing about the person using the tool | USA |
| Stripe | Subscription billing and payment processing | USA / EU |
| Shopify | Store data, and subscription billing for App Store installs | Canada / USA |
| Render | Backend application hosting | EU |
| Vercel | Frontend hosting and edge delivery | Global CDN |
| Resend | Sending email: sign-in codes, digests, receipts, support replies and marketing emails. For marketing emails, it also holds your address on our list and whether you have unsubscribed | USA |
| Sentry | Error monitoring. Payloads are scrubbed of personal data before they are sent | USA |
| ipinfo.io / ipapi.co | Resolving an IP address to a country when our CDN has not already done so (section 2.3). They receive the IP address and nothing else | USA |
| Meta (Facebook) | Ad data access for Meta Ads accounts you choose to connect | USA |
| Ad data access for Google Ads accounts you choose to connect | USA / EU | |
| Snapchat | Ad data access for Snapchat Ads accounts you choose to connect | USA |
| Klaviyo | Email marketing data for Klaviyo accounts you choose to connect | USA |
| Meta (Facebook) | Advertising pixel on our marketing site aplon.io, under the consent rule in section 2.11, and on our Shopify App Store listing, as section 2.11 describes, and the same events sent from our server through Meta's Conversions API under the same rule. Receives the four kinds of event listed in section 2.11 — that list is the maintained one, so this row deliberately does not restate it. Acts as an independent controller, not our sub-processor. No merchant store data, ad account data or Aplo chat data is ever sent to it. Separately, our free Competitor Ads tool sends Meta's Ad Library the brand name or web address you search for, which it needs to find that brand's ads | USA / EU |
| Google Analytics on our marketing site aplon.io, under the consent rule in section 2.11, and on our Shopify App Store listing, as section 2.11 describes. Receives the four kinds of event listed in section 2.11, with the page address, browser and device details, and an approximate location worked out from the IP address. Processes the statistics for us, and acts as an independent controller where it uses the data for its own advertising purposes; not our sub-processor. No merchant store data, ad account data or Aplo chat data is ever sent to it | USA / EU | |
| Email for our team, including the emails we send to stores we contact first and the record of who we wrote to (section 2.18) | USA and other countries |
We do not share your personal data with any other third parties except where you ask us to, as when you connect your own AI assistant (section 2.12), where required by law, or to protect our legal rights.
6. International data transfers
Some sub-processors listed above are located outside the European Economic Area (EEA), including the United States. When your data is transferred outside the EEA, we ensure that appropriate safeguards are in place in accordance with GDPR Chapter V, including:
- Standard Contractual Clauses (SCCs) approved by the European Commission
- Reliance on an EU adequacy decision where applicable
- Sub-processor participation in recognised frameworks such as the EU-US Data Privacy Framework
You may request a copy of the relevant transfer mechanisms by contacting contact@aplon.io.
7. Data retention
We retain your personal data for as long as your account is active and as needed to provide the service. Specific retention periods:
- Account and store data: retained for the life of your account, and deleted immediately when you delete your account, apart from the short closure record below. Backups are overwritten on our provider's normal rolling cycle.
- Account closure record: when your account is deleted, we keep a short record that it was closed: your email address, the names of the stores you had connected, your plan, the date you signed up and the date it was closed. We keep it so we can answer questions about the account later and show that the deletion was carried out. It holds none of your store data, and we do not use it to market to you.
- Setting-up record inside Shopify: deleted 90 days after we last saw you if you never agreed to our Terms. If you did agree, it is part of your account and is deleted with it.
- Shopify order data: cached for a rolling 60 months (five years). Orders older than that are deleted automatically by a daily job, whether or not your account is still active.
- Storefront pixel data: retained for a rolling 24 months. Visitor events and visit-to-order links older than that are deleted automatically by the same daily job. We keep this for a shorter period than order data because it is behavioural and we do not need it for longer.
- Integration tokens and keys: deleted immediately upon disconnection or account deletion.
- Aplo chat history: retained for the life of your account unless you request earlier deletion.
- Live chat: deleted automatically 30 days after the chat began. If you asked for a person, the conversation was also copied into a support request, which is kept as the next line says.
- Support requests: what you sent us and our replies are kept for as long as we need them to help you and to keep a record of what we said. You can ask us to delete them at any time (section 14).
- Files attached to a support request: deleted automatically by a daily job, 90 days after the request is closed or 365 days after they were sent, whichever comes first.
- Reviews: while the review counts towards the rating on aplon.io or is quoted there, then three years. A review that never counts and is never quoted, three years after it was sent to us or copied from the Shopify App Store. Any email reply we keep as a record of consent is deleted with its review.
- Case studies: three years after it comes down, or three years after our last contact about it if it never goes up.
- Demo invites: five years after your visit. Your IP address, browser name and the number of questions you asked Aplo: 90 days after your visit. An invite that was never used is deleted 30 days after it was made. A daily job does the deleting.
- Push notification subscriptions: deleted when you unsubscribe or delete your account.
- Marketing list: an address stays on the list until you unsubscribe. An address that is not confirmed is deleted 30 days after our last email asking you to confirm. If you unsubscribe, an email bounces or you report one as spam, we keep your address so that we do not email you again. If you delete your account, your address is removed from the list, even if you had unsubscribed.
- Stores we contact first: deleted six months after our last email if there is no reply. If you ask us to stop, we keep only the email address and the store's web address, so that we do not write to you again, and delete the rest.
- Billing and commission records: retained for 7 years as required by applicable financial and tax law. This includes affiliate referral and commission records, which we keep after an account is deleted because they evidence money we have paid.
- Server logs: retained for up to 90 days for security and debugging purposes.
You can delete your account and all associated data at any time from the Settings page. Deletion is permanent and irreversible.
8. Security
We implement appropriate technical and organisational measures to protect your personal data against unauthorised access, loss, or disclosure:
- Integration access tokens and keys — Shopify, Meta, Google, Snapchat, Klaviyo — are encrypted at rest using AES-256-GCM
- All data in transit is encrypted via TLS 1.2 or higher
- Sessions expire after 30 days, and you can sign out any individual device from your account settings
- Passwords are stored only as salted PBKDF2 hashes, and two-factor authentication is available
- Access to production systems is restricted to authorised personnel only
- We do not log or store access tokens in plaintext anywhere in our systems
- Errors sent to our monitoring provider are scrubbed of personal data first
In the event of a personal data breach that poses a risk to your rights and freedoms, we will notify the Cyprus Commissioner for Personal Data Protection within 72 hours of becoming aware. Where the breach is likely to result in a high risk to you, we will also notify you directly without undue delay.
9. Your rights under GDPR
If you are located in the European Economic Area or the United Kingdom, you have the following rights regarding your personal data:
- Right of access (Article 15): to request a copy of the personal data we hold about you and information about how we process it
- Right to rectification (Article 16): to request correction of inaccurate or incomplete personal data
- Right to erasure (Article 17): to request deletion of your personal data where there is no longer a lawful basis for us to hold it. You can also delete your account directly from Settings.
- Right to restriction of processing (Article 18): to request that we limit how we use your data in certain circumstances
- Right to data portability (Article 20): to receive your personal data in a structured, commonly used, machine-readable format and to transfer it to another controller
- Right to object (Article 21): to object to processing of your personal data based on our legitimate interests. You can object to direct marketing at any time, for any reason, and we will stop.
- Right to withdraw consent: where processing is based on consent (push notifications, email digests, and analytics storage on aplon.io), you may withdraw consent at any time without affecting the lawfulness of processing prior to withdrawal
- Right not to be subject to automated decision-making: we do not make solely automated decisions that produce legal or similarly significant effects about you
To exercise any of these rights, email contact@aplon.io. We will respond within 30 days. We may ask you to verify your identity before processing your request.
You also have the right to lodge a complaint with the Cyprus Commissioner for Personal Data Protection (dataprotection.gov.cy) or the supervisory authority in your country of residence or place of work.
10. Your rights in the United States
If you live in a US state with a comprehensive privacy law — California, Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Delaware and a growing number of others — you have the rights set out below. We honour them for residents of every US state, whether or not we currently meet the thresholds that would make a particular law apply to us.
10.1 Which data this covers — please read this first
Aplon holds three different kinds of personal information, and your route to exercising a right depends on which one you are asking about.
- If you are an Aplon merchant or user — your account, usage and billing data (sections 2.1, 2.8, 2.9, 2.10). For this we are the business, and the rights below are ours to answer. Contact us directly.
- If you shopped at a store that uses Aplon — the Shopify customer records in section 2.2 and the storefront analytics data in section 2.3. For this the merchant is the business and Aplon is only their service provider: we hold the data on that merchant's instruction and process it solely on their behalf. Please send your request to the store you purchased from, and they will instruct us. If you contact us directly we will tell you so, and we will act on any request the merchant or Shopify forwards to us — including a deletion request Shopify passes on under its own shopper-privacy process.
- If we wrote to your store first (section 2.18): for this we are the business, and the rights below are ours to answer. Contact us directly.
10.2 Categories of personal information we collect
Using the categories named in the California Consumer Privacy Act. This describes information about you as an Aplon user; the full detail of what each item is, and where it comes from, is in section 2.
| Category | Collected | What it is in Aplon |
|---|---|---|
| Identifiers | Yes | Email address, name if you give it, account and store identifiers, the number Shopify uses for you, IP address, the name, store name and email you give with a review, the name and email you give with a demo invite, and the name and business email address of someone at a store we write to first (section 2.1, 2.2, 2.9, 2.10, 2.14, 2.15, 2.17, 2.18) |
| Customer records information | Yes | Name and contact details held against your account (section 2.1) |
| Protected classification characteristics | No | We do not collect age, race, sex, disability, or any other protected characteristic |
| Commercial information | Yes | Your subscription plan, billing status and transaction history (section 2.8) |
| Biometric information | No | Never collected |
| Internet or network activity | Yes | Pages visited in the app, features used, Aplo chat messages, error logs, session metadata (section 2.9), and the stars and words of a review you leave us (section 2.15) |
| Geolocation data | Approximate only | Country derived from IP address. We do not collect precise geolocation (section 2.3) |
| Audio, video or similar sensory data | No | Never collected |
| Professional or employment information | Limited | The store you work for, when we write to it first (section 2.18) |
| Education information | No | Never collected |
| Inferences used to build a profile | No | Aplon's analysis is about your store's performance. We do not build a profile of you as a person, and we do not profile you for decisions that produce legal or similarly significant effects |
| Sensitive personal information | Limited — see 10.3 | Your account log-in credentials, held only to sign you in (section 2.1) |
Where it comes from: from you directly, from the platforms you choose to connect (Shopify, Meta, Google, Snapchat, Klaviyo), from your use of the service, and from our payment provider. Why we collect it: the purposes are listed in section 4. Who we disclose it to: the sub-processors named in section 5, each for the stated operational purpose only. How long we keep it: section 7 sets the retention period for each kind of data — it is not repeated here so there is only ever one copy to maintain.
10.3 Sensitive personal information
The only sensitive personal information we hold is what lets you into your own account: your log-in credentials, stored as a salted PBKDF2 hash together with your two-factor secret and recovery-code hashes (section 2.1). We use it for one thing — authenticating you — and for the security and fraud-prevention purposes the law permits without further consent. We do not use or disclose it to infer characteristics about you. Because of that, the right to limit the use of sensitive personal information does not arise here; there is no additional use to limit.
10.4 Selling and sharing your personal information
We do not sell your personal information. We have never taken money, or anything else of value, in exchange for it, and we do not.
We do "share" it, in the narrow sense the CCPA uses. Since 24 August 2026 our marketing website aplon.io has run the Meta pixel described in section 2.11, and since 2 November 2026 Google Analytics with Google's advertising features. Disclosing your visit and signup to Meta and to Google so that they can measure and re-show our ads counts as sharing for cross-context behavioural advertising. This applies only to visitors of aplon.io and of our listing on the Shopify App Store. The categories involved are identifiers, internet activity and, for Google, approximate location — no sensitive personal information, no store data, no ad account data and no Aplo chat data are ever disclosed for advertising. Nothing inside the product at app.aplon.io is shared with anyone for advertising. We have no knowledge of selling or sharing the personal information of anyone under 16.
How to stop it. Use this Do Not Sell or Share My Personal Information link, or the Cookies link in the footer of any page — they open the same choice. Selecting "Essential only" stops the Meta pixel and Google Analytics loading, withdraws consent with Meta and with Google and deletes their cookies from your browser. No account is needed and we do not ask you to verify your identity for this.
Global Privacy Control. We honour it. If your browser or extension sends the GPC signal, we treat it as an opt-out request and neither script loads, without you having to do anything else. If you later choose "Accept all" on our own banner we treat that as the more recent and more specific choice, and it takes precedence — you can reverse it at any time.
10.5 Your rights
- Right to know and access: to be told what personal information we have collected about you, where it came from, why we collected it, who we disclosed it to, and to receive a copy of it
- Right to delete: to have your personal information deleted, subject to the exceptions the law allows — chiefly the billing and tax records in section 7 that we are legally required to keep
- Right to correct: to have inaccurate personal information corrected
- Right to data portability: to receive your data in a portable, readily usable format
- Right to opt out of sale, sharing, targeted advertising and profiling: we do not sell your information and we do not profile you to make decisions about you. We do share aplon.io visit and signup events with Meta for advertising, as set out in 10.4 — use the "Do Not Sell or Share My Personal Information" link in 10.4, or the Cookies link in any footer, to stop it, or send the GPC signal and it never starts
- Right to limit the use of sensitive personal information: see 10.3 — our only use is authenticating you, which the law permits without a limit right arising
- Right to non-discrimination: we will not deny you service, charge you a different price, or give you a lower quality of service for exercising any of these rights. We run no financial-incentive or loyalty programme tied to your data
- Right to appeal: if we refuse a request, you may appeal by replying to our decision or writing to the address below. We will respond to an appeal within 60 days, and if we uphold the refusal we will tell you how to complain to your state Attorney General
10.6 How to make a request
Email contact@aplon.io and say which right you are exercising. You can also delete your account and its data yourself, at any time, from Settings → Delete account — described in section 11.
We will confirm receipt within 10 business days and respond within 45 days. If we need longer we will tell you why, and take no more than a further 45 days. We will ask you to verify your identity first — normally by confirming control of the email address on the account — and for a request to know, we will match the request to the account before releasing anything. An authorised agent may act for you if they provide your written permission; we may still contact you to confirm it. Exercising these rights is free unless a request is manifestly unfounded or excessive, in which case we will say so rather than quietly ignore it.
10.7 California "Shine the Light"
Under Californian Civil Code section 1798.83, California residents may ask whether we disclosed personal information to third parties for those third parties' own direct marketing. We do not, and never have.
11. Data deletion requests
You can delete your Aplon account and all associated data at any time from Settings → Delete account. If you cannot reach that screen, email support@aplon.io and we will delete your account. This immediately and permanently removes your login, every store you own, your integration tokens and keys, your Aplo chat history, your team seats, and your notification subscriptions. If you are a team member on someone else's store, you lose your login, and the store stays with its owner. Any active subscription is cancelled at the same time, and Aplon is removed from every Shopify store you own. If we cannot do this for a Shopify store, we will email you how to finish it by uninstalling Aplon from that store. Records we are required to keep for tax and accounting are listed in section 7. If you have connected a Meta Ads account, you can also revoke Aplon's access directly from Meta Business Integrations settings. For Google Ads, you can revoke access from your Google Account permissions.
12. Children's data
Aplon is not directed at children under the age of 16. We do not knowingly collect personal data from children. If you believe we have inadvertently collected such data, please contact us at contact@aplon.io and we will delete it promptly.
13. Changes to this policy
We may update this Privacy Policy from time to time. We will notify you of material changes by email and by updating the "Last updated" date at the top of this page at least 14 days before changes take effect. Continued use of the service after that date constitutes acceptance of the updated policy.
14. Contact
Aplon Ltd
Agiou Andronikou 21, 5350 Frenaros, Cyprus
contact@aplon.io