Privacy Policy
Effective date: September 2, 2026 · Last updated: October 16, 2026
This policy explains what personal data StoreToNative collects, why, and what rights you have over it. It covers our website at storetonative.com, our console at app.storetonative.com, and the mobile apps we build for merchants.
We are StoreToNative LLC, a New Mexico limited liability company. Contact us at support@storetonative.com.
1. Two different roles — please read this first
We handle two kinds of personal data, under two different legal roles. The distinction determines who you contact about your rights.
When you are a merchant using StoreToNative, we are the controller. We decide how and why your account data is processed. Section 2 applies.
When you are a shopper using an app built with StoreToNative, the merchant is the controller and we are their processor. We hold and transmit your data on the merchant's behalf and act on their instructions. Section 3 applies. Direct your privacy requests to the merchant whose app you are using — we will support them in responding, but the decision is theirs.
2. Merchant data — where we are the controller
2.1 What we collect
| Data | Why we hold it | Legal basis (GDPR) |
|---|---|---|
| Name and email address | To create and identify your account, and to contact you | Performance of a contract |
| Password | To secure your account. Stored as a salted hash — never in plain text, and never recoverable by us | Performance of a contract |
| Optional sign-up answers — your store's web address and how you heard about us | To understand which channels bring merchants to us, and to offer help getting your store connected. Both are optional; leave them blank and nothing is stored | Legitimate interests |
| Store connection credentials | To read your catalogue and receive order events. Encrypted at rest | Performance of a contract |
| Store URL and configuration | To build and operate your app | Performance of a contract |
| Billing details | To take payment and meet tax and accounting obligations. Full card numbers are held by our payment processor, not by us | Contract; legal obligation |
| Partner program details — if you apply to, or take part in, our partner program: your name, email address, company, website, the country you work from, what you tell us about who you would refer, how you want to be paid and, for PayPal, your PayPal email address; and, before a payout, the tax form (it may include a tax identification number) and the payout details, such as bank details, that you send us by email | To review your application, run your partner account, work out and pay your commissions, and meet tax and accounting obligations. The tax form and your bank details are not stored in our product database or in your partner area. We keep the tax form in a private file outside our product systems, and we enter your bank details at our bank to pay you | Performance of a contract; legal obligation |
| Support messages | To answer your questions and improve support | Legitimate interests |
| Website chat messages | To answer questions asked through the chat assistant on this website, and to find the questions it could not answer | Legitimate interests |
| WhatsApp messages — your WhatsApp number and profile name, what you write or send to our WhatsApp number, and, if you fill in the short form we offer there, your name, email address, store address and your answers about your store | To answer your questions, and to follow up with you about StoreToNative when you ask us to. An AI assistant answers first and says so; a person on our team can join the conversation | Legitimate interests |
| Server and access logs, including IP address | Security, abuse prevention, debugging | Legitimate interests |
| Account activity log — what changed in your workspace, who changed it and when, with the IP address and browser it came from | To show you and your team what happened in your account, and to investigate security problems | Legitimate interests |
| Product usage analytics | To understand which features are used and improve them | Legitimate interests |
2.2 What we do not do
We do not sell your personal data. We do not share your account data, your store data or your billing details with advertisers. The one thing we do share with an advertising company is visit data from our public website and demo page, which goes to Meta as described in section 10. We do not use your store data to compete with you, to build a competing product, or to contact your customers for our own purposes.
2.3 Marketing
We may email you about your account, billing, security and material service changes — you cannot opt out of these, because they are necessary to the contract.
We will only send you marketing email with your consent, and every marketing email has a one-click unsubscribe.
The same goes for WhatsApp. We only send product updates or offers there if you ticked that box in our WhatsApp form, and you can tell us to stop at any time by replying in the chat.
3. Shopper data — where we are a processor
When a shopper uses an app we built for a merchant, we may handle:
- Push notification tokens — only where the shopper has granted notification permission on their device, and used only to deliver the notifications the merchant sends or sets up: order updates, abandoned-cart reminders, promotional messages and automated campaigns (such as a thank-you after a first order), and the price-drop or back-in-stock alerts a shopper has asked for;
- Cart summary — the number of items and the cart total, so that an abandoned-cart reminder can be sent;
- Products a shopper asks to watch — so that the price-drop or back-in-stock alert they asked for can be sent;
- Order references and order contents — to display order status and history in the app;
- Names and delivery or billing addresses — where the app's native address step is enabled by the merchant;
- Account identifiers — where a shopper signs in to their store account through the app;
- App usage data — a random identifier created when the app is installed, the device platform, when the app was first and last opened and how many times, and totals (such as notifications opened) that are not linked to any device.
Payment card details are never handled by StoreToNative. Checkout runs through the merchant's own payment gateway.
We process this data only to provide the app to the merchant. We do not sell it, do not use it for our own marketing, and do not combine it across merchants to build profiles of individuals.
4. Where your data is held
Our primary infrastructure is hosted with Hostinger, in a data centre located in Paris, France (European Union).
Where personal data is transferred outside the EEA or UK — for example to a sub-processor, or to our own personnel in the course of support — we rely on an appropriate safeguard, including the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum where applicable.
5. Who else processes data for us
| Sub-processor | Purpose | Location |
|---|---|---|
| Hostinger | Application and database hosting | Paris, France (EU) |
| Hostinger Email | Transactional and support email, and the mailbox that receives what you send us by email | EU |
| Stripe | Payment processing and subscription billing | USA / global |
| Apple, Google | App distribution and push notification delivery (APNs, Firebase Cloud Messaging) | USA / global |
| Your own AI assistant, if you connect one | On Pro and Agency you may connect an AI assistant you choose (for example Claude or ChatGPT) to your workspace. It receives the workspace data you ask it for, under its provider's terms, not ours. It never receives your shoppers' names, email addresses or delivery or billing addresses, or who placed an order. About shoppers it receives counts and totals and, for each recent order, its number, total, status and item count, never what was in the order. It can also read your product and category catalogue | Chosen by you |
| Umami (self-hosted) | Website and product usage analytics — runs on our own infrastructure, not a third-party service | Paris, France (EU) |
| Google (Gemini) | Powers three assistants: the chat assistant on this website, the assistant in the console, and the assistant that answers first on our WhatsApp number. Only what a visitor or merchant types into them, plus the product or console context needed to answer, is sent — never shopper data. On WhatsApp this includes your WhatsApp profile name and the earlier messages of the same conversation, but not your phone number. Where an assistant runs on Google's free tier, as the website chat assistant and the WhatsApp assistant do, Google may use the conversation to improve its products and human reviewers may read it — so please do not type personal or confidential information into it | USA / global |
| OpenAI | Backup for the WhatsApp assistant. If Google's service does not answer, the same message, your WhatsApp profile name and the earlier messages of the conversation are sent to OpenAI instead | USA / global |
| Meta (WhatsApp Business Platform) | Carries the messages between you and our WhatsApp number, and the short form we offer there | USA / global |
| Telegram | Our team reads and answers WhatsApp conversations in a private Telegram group, so a copy of each WhatsApp conversation, including files you send and the answers to our WhatsApp form, passes through Telegram | Global |
| Cloudflare (Turnstile) | Bot protection on the console's sign-up and sign-in forms and on this website's contact form. Cloudflare receives the visitor's IP address and browser signals to tell people from automated abuse | USA / global |
| Cloudflare R2 | Off-site nightly backups of the databases and merchant files (uploads, screenshots, support attachments). Private buckets in our Cloudflare account | USA |
| Sentry | Error monitoring for our server and, only for merchants who agree to it, for their shopping app. When something breaks, it receives the error message, the code location and which kind of request failed (and, for an app, its version). Request contents, cookies, headers, account details, email addresses, push tokens and shopper data are removed before anything is sent | USA |
| GitHub (Actions) | Builds each merchant's app. The app's own configuration and assets — name, icon, store address, screenshots — pass through the build | USA / global |
Our bank, and PayPal if you choose it, receive your payout details to carry out a payment to you. They handle them under their own terms.
We require every sub-processor to protect personal data to a standard consistent with this policy.
Meta Platforms is not a sub-processor. It receives visit data from our website and demo page through the Meta Pixel and also uses that data for its own advertising systems, under its own privacy policy. Section 10 says what it receives and how to opt out.
6. How long we keep things
| Data | Retention |
|---|---|
| Account data | For as long as your account is open |
| Account data after closure | Deleted within 90 days, except where we must keep it by law |
| Build artifacts and app configuration | 90 days after a subscription lapses, then permanently deleted |
| Billing and tax records | 7 years, as required by US tax law |
| Partner tax forms and payout details | Tax forms: 7 years after the last year in which we paid you. Bank details: at our bank, for as long as the bank keeps payment records. The email you sent them in: deleted from our mailbox within 30 days after we have saved the form |
| Server logs | 90 days |
| Account activity log | 180 days; failed sign-ins and refused requests 30 days |
| Support correspondence, website chat conversations, and WhatsApp conversations with the details you gave us there | 2 years from the last message |
| Backups | Nightly off-site backup copies of the databases are kept for 30 days. The backup of merchant files mirrors the current files, and keeps changed or deleted files for 30 days |
| Shopper data | For as long as the merchant's account is active, then per the merchant's instruction |
7. Security
We take security seriously and apply measures appropriate to the risk, including:
- encryption in transit (HTTPS/TLS) for all connections;
- encryption at rest for store connection credentials;
- password hashing with a salt — we cannot read or recover your password;
- access controls limiting who can reach production data;
- regular patching of our infrastructure and dependencies.
No system is perfectly secure. If a personal data breach occurs that is likely to result in a risk to your rights, we will notify you and the relevant supervisory authority within the timeframes required by law.
8. Your rights
Depending on where you live, you may have the right to:
- access the personal data we hold about you;
- correct data that is inaccurate or incomplete;
- delete your data ("right to erasure");
- restrict or object to processing, including profiling;
- portability — receive your data in a structured, machine-readable format;
- withdraw consent at any time, where processing is based on consent;
- not be discriminated against for exercising these rights.
How to close a StoreToNative account. There is no self-service button for this in the console yet — email us and we will close the account and delete its data on the schedule in section 6. We say this plainly rather than implying a control that does not exist.
Shoppers using a merchant's app. Two different things, and they are not interchangeable. The app's “Delete my data on this device”removes what we hold for that device — the notification token, the saved cart, the links from that device to its orders, and app-usage counts — and it is available whether or not you have an account. “Delete account”, where the merchant has enabled shopper accounts, deletes your account on the merchant's own store. Your orders themselves belong to the merchant's store and are kept under that store's own retention policy, not ours — for those, contact the merchant.
If you are in the EU or UK, these rights come from the GDPR and UK GDPR, and you have the right to lodge a complaint with your national supervisory authority.
If you are in California, the CCPA/CPRA gives you rights to know, delete, correct, and to opt out of sale or sharing. We do not sell personal information for money.
Do Not Sell or Share My Personal Information
We use the Meta Pixel on storetonative.com and on our public demo page (section 10). Sending visit data to Meta to measure our advertising may count as “sharing” personal information for cross-context behavioral advertising under California law. It applies only to visits to those public pages — never to your account, your store data or shoppers in the apps we build. You can opt out in any of these ways:
- Turn on Global Privacy Control in your browser (built in to Brave, DuckDuckGo and Firefox, or available as an extension). We treat it as an opt-out: when your browser sends it, we do not load the Meta Pixel at all.
- Block or clear cookies for storetonative.com and app.storetonative.com in your browser.
- Change how Meta uses this data in your Meta ad preferences, and under “Your activity off Meta technologies” in your Meta Accounts Center.
To exercise any right, email support@storetonative.com. We will respond within30 days. We may need to verify your identity first.
Shoppers: please contact the merchant whose app you used. They are the controller of your data.
9. Children
The Service is not directed to children under 16, and we do not knowingly collect their personal data. If you believe a child has provided us with personal data, contact us and we will delete it.
10. Cookies and similar technologies
Our website and console use cookies that are strictly necessary to sign you in, keep your session secure, and remember your preferences. These do not require consent.
Our website analytics — on storetonative.com and on the public demo page at app.storetonative.com/demo — are self-hosted and cookieless: they do not set cookies or track you across other websites.
Meta Pixel (advertising measurement). On storetonative.com and on our public demo page at app.storetonative.com/demo we use the Meta Pixel, a tool from Meta Platforms, Inc., to measure whether our ads on Facebook and Instagram lead people to visit us, try the demo, or get in touch. It does not run on the console's sign-in, sign-up or signed-in pages, and never inside the shopping apps we build for merchants. When it runs, your browser sends Meta the address of the page you are on (on the demo page this includes the store address you typed in), the page that referred you, your IP address, browser and device information, and which of these happened: you viewed a page, a demo preview was shown, you sent us the contact form or the demo's “talk to us” form, or you clicked a link on storetonative.com that goes to the console's sign-up page. Apart from that store address, we do not send Meta your name, your email address or anything else you type into a form. The Pixel sets a first-party cookie (_fbp) so Meta can recognise repeat visits, and Meta may connect this activity to a Facebook or Instagram account you are signed in to, under Meta's own privacy policy.
The _fbp cookie is not strictly necessary, and we do not show a consent banner for it. Instead, we do not load the Pixel at all if your browser sends a Global Privacy Control signal, or if your device's time zone places you in the EU, the EEA or the UK — our ads are aimed at the United States, and we would rather not measure visitors we are not advertising to. The time-zone check is a simple safeguard, not a precise location test. Everyone else gets the Pixel without being asked, and can opt out at any time using the steps under “Do Not Sell or Share My Personal Information” in section 8.
Partner link cookie. If you reach storetonative.com through a link from one of our partners (a link that ends in ?ref= and the partner's code), we set a first-party cookie named stn_ref. It holds only that partner's code and, if the link had one, the partner's own label for the link. It holds nothing about you. It lasts 90 days, and our console reads it when you create an account, so that the partner who sent you is credited and you receive the partner's discount. We also count that the link was opened, as a number only: no IP address and no browser details are stored with it. This cookie is not strictly necessary and we do not show a consent banner for it. We do not set it if your browser sends a Global Privacy Control signal, or if your device's time zone places you in the EU, the EEA or the UK; in those cases the partner's code travels only in the address of the pages you open during that visit.
YouTube videos. Our home page and our partner program page at storetonative.com/partners each have a video that is hosted on YouTube, a service of Google LLC. Each page shows only a picture until you press play; until then, nothing is sent to YouTube. When you press play, the video loads from YouTube's privacy-enhanced address (youtube-nocookie.com). Google then receives your IP address and browser and device information, and may store information on your device, under Google's own privacy policy. If you do not want that, do not press play; what each video shows is also written on its page.
Our mobile apps do not use cookies, but do use device identifiers for push notifications and analytics as described in section 3.
11. Changes to this policy
We may update this policy. For material changes we will notify you by email or in the consoleat least 30 days before they take effect, and we will update the date at the top of this page.
12. Contact
StoreToNative LLC
1209 Mountain Road Pl NE, Ste N
Albuquerque, NM 87110, USA
+1 (505) 926-5550
support@storetonative.com
For data protection questions, use the same email address and mark your message "Privacy".