Our role
For the merchant’s own account, settings, and billing, Castor decides how that data is used. For shopper data a store collects through a Castor popup or widget, the merchant decides why it is collected and what it is used for, and Castor processes it on the merchant’s behalf and on their instructions. In privacy law terms, the merchant is the controller of shopper data and Castor is the processor.
Who to write
Questions about this policy go to hello@castorapp.com or the contact page. Shoppers asking about a signup on a store should write to that store. The merchant decides why the address was collected and what the offer said.
What we process
From the merchant, after they install and approve permissions in Shopify Admin:
- The shop domain, store id, and the access Shopify grants the app.
- Products, variants, inventory, and locations, so the product desk and product blocks can run.
- Theme access, so the Castor App embed and the Castor Widgets block can be checked and placed.
- Orders, when the merchant approved them at install. The current install list includes orders, customers, and languages. We use units and revenue. Recommendations do not use the customer’s name, email, phone, or street address from those orders.
- Customers, only if the merchant turns on adding signups to Shopify customers. We create or update the customer for a signup, and nothing else.
- The store’s published languages, from the same install list, so a translation can show to the right shopper.
- Discount codes the app creates in that store when a form is set to generate a one-use code at a percent the merchant chose.
- Designs, popups, widgets, and settings the merchant saves in the dashboard.
From a shopper, only when they submit a form the merchant placed:
- The fields on that form, which can include a name, an email, and a phone number.
- Which popup or widget collected it, and when.
- If orders were approved at install and a paid order matches that signup, the fact of the sale and the amount, on that shop’s list.
On the storefront, the script reads the product on the page and the cart total so it can fill a product block, a stock line, or a free-shipping bar. That is tied to the visit, not to a name.
What the storefront keeps in the shopper’s browser
Castor does not set cookies on the storefront. The script uses the browser’s own storage for that store only:
- A random visitor number, so a popup is not shown again after it was closed, a visitor keeps seeing the same A/B version, and views are not counted twice. It is not a name, an email, or a device fingerprint, and it is not shared with other stores.
- Whether a popup was closed or already shown in this visit, so the merchant’s “how often” setting works.
- After a signup, a reference to that signup, so the same shopper is not asked again.
- The height of a widget, so the page does not jump while it loads.
With the visitor number, the script sends us events such as “seen”, “clicked”, “closed”, and “signed up”, the type of page, and whether there is something in the cart. Merchants see these as counts. Your IP address is used only for a moment to limit abusive traffic, and is not stored. Clearing the browser’s site data removes all of this.
Why
- To run the app the merchant installed: designs, popups, widgets, the catalog, and one-use codes.
- To keep a contact list for that shop and let the merchant export it.
- To answer Shopify’s required privacy webhooks, described below.
- To bill the plan through Shopify. We do not take a card on this website.
What we do not do
- We do not sell contacts, and we do not rent a shop’s list to another shop.
- We do not use shopper name, email, phone, or address to recommend products.
- We do not drop advertising cookies, and we do not let other sites read the dashboard’s browser storage.
- We do not claim a conversion rate, a star rating, or a revenue lift we have not measured for that store.
Who else sees it
Shopify already holds the store, the orders, the theme, and any discount code we create. Those stay in the merchant’s Shopify account.
If the merchant typed a list URL on a form, the shopper’s browser also posts that signup to the address the merchant entered. We do not send that address to the recommendation engine.
If the merchant turns on “Add signups to Shopify customers”, each new signup is also saved as a customer in that store’s own Shopify admin, tagged “Castor signup”. It is marked as an email subscriber only when the shopper ticked the form’s consent box. Customers are on the install list. Sending signups is a setting you can turn off.
When a merchant asks Castor to write a layout, rewrite product SEO, or make a product picture, the text and images they send for that job are used to produce the result. Those jobs spend coins from the plan. The in-app assistant does not spend coins.
We use these service providers, each only for the job listed:
- Shopify, for the store, sign-in, billing, discount codes, and customers.
- Railway, which hosts the app, its database, and its cache.
- Cloudflare R2, which stores the images used in designs.
- OpenAI, for AI jobs the merchant starts: drafting words, rewriting product SEO, and making product pictures. It receives the text and images for that job, and never the contact list.
- Pollinations, a backup image generator used only if OpenAI is unavailable. It receives the picture description, and nothing about the store or its shoppers.
- Google Analytics, on the public pages of try.castorapp.com only, to count visits to this website. It is not loaded inside the app in Shopify Admin, and it is never loaded on a merchant’s storefront, so it sees no shopper and no store data.
We do not publish a shop’s catalog or contact list, and we do not give shopper data to advertisers.
Where data is processed
Our providers may process data in the United States and other countries. Where the law asks for it, such as for data from the European Economic Area, the United Kingdom, or Switzerland, we rely on the providers’ standard contractual clauses or an equivalent safeguard.
The dashboard in the browser
Opening the app from Shopify Admin starts a short login that lives in the browser tab and expires. The shop domain and store id stay in the browser so the next page still knows which store is open. That storage is for this app, on this site.
Shopify’s required requests
We accept Shopify’s compliance webhooks and check the signature before acting.
- customers/data_request. We record the request and show it to the merchant on the Contacts page, with a file of every signup we hold for that shopper, so the merchant can send it to them.
- customers/redact. We delete contact rows for that store that match the email or phone Shopify sends, then we drop the address.
- shop/redact. After a store is uninstalled, and if it has not been installed again, we delete that store’s contacts, catalog copy, saved designs, popups, widgets, and the other shop data we hold for it. We keep a record that the store was redacted so a later restart cannot restore that copy.
Uninstall by itself stops new calls. The full delete waits for Shopify’s shop/redact, which is the timing Shopify uses.
How long it stays
Catalog copy, contacts, designs, popups, and widgets stay until the merchant deletes them, until a customers/redact request removes that signup, or until shop/redact removes the store. Discount codes live in the merchant’s Shopify admin after we create them.
Security
The app is served over HTTPS. Data on the host is encrypted at rest. Shopify webhooks are checked before we act on them. Access to a store’s data in the dashboard requires the merchant session Shopify issues. When a merchant opens or deletes a signup, or when Shopify asks us to redact or disclose one, we keep a short access record of the action, the store, and the time. That record does not store the shopper’s email or phone. If you believe a store’s data was exposed, write to hello@castorapp.com. We will look at the access record, stop the leak if we can, and tell the merchant. If the law or Shopify requires it, we will tell them too.
Choices
- A merchant can uninstall from Shopify Admin at any time, and can export contacts before they do.
- A merchant chooses which form fields to ask for, and whether a form generates a discount code.
- The current install asks for orders, customers, and languages in one list. Without orders we do not download orders.
- A shopper who wants a signup deleted should contact the store. The store, or Shopify’s redact webhook, is how that row is removed.
Your rights
Depending on where you live, including under the GDPR, the UK GDPR, Canada’s PIPEDA, and California’s CCPA, you can ask to see the personal data held about you, to correct it, to delete it, to receive a copy, or to object to or limit how it is used. We do not sell or share personal information for cross-context advertising, as the CCPA defines those terms.
- Merchants can write to hello@castorapp.com about their account. We answer within 30 days.
- Shoppers should write to the store where they signed up, since the store decides how their data is used. If a store asks us to, we help it answer. If you write to us directly, we pass the request to that store.
- You can also complain to your local data protection authority.
Children
Castor is a tool for Shopify merchants. It is not directed at children, and we do not knowingly collect a child’s information on our own behalf.
Changes
If this policy changes, the date at the top of this page changes with it. Continued use of the app after that date is use under the updated policy.
The commercial terms are on the terms of service.
