Privacy policy

Last updated 25 October 2026. Applies to the Reshelf app for Shopify, made by Scorptek LLC.

In short: we store a shopper’s email address and, if they give one, their mobile number, both encrypted, to send the back-in-stock or price-drop alert they asked for. We don’t sell them, use them for our own marketing, or keep them longer than needed. They are also added to the customer list of the store the shopper signed up with, in that store’s Shopify admin, and a shopper who ticks the store’s newsletter box is recorded there as subscribed to email marketing and, if the store connects Klaviyo, added to its Klaviyo list. Merchants control their own store’s data from inside the app.

Who this covers

Merchants who install the app on their Shopify store, and shoppers who ask to be notified when a product is back in stock or drops in price. Merchants are the data controllers for their shoppers’ data; Scorptek LLC processes it on their behalf.

What we collect and why

Data	From	Why
Shopper email address (stored encrypted), the product and variant they asked about, the time, and whether they ticked the newsletter box	The “Notify me” form	To send the alert they asked for and let the merchant see demand. The email address is added to the store’s customers in Shopify, subscribed to email marketing only if the newsletter box was ticked (see “What goes to the store’s Shopify admin”).
Delivery events for each alert email or text: sent, delivered, delayed, bounced, complained, failed	Our email and SMS providers	To show merchants whether alerts arrived, and to stop messaging shoppers who don’t want it. When an email is reported as spam or bounces permanently, that store stops emailing alerts to the address and cancels its other waiting email requests, and a new request from it is not taken. When a number replies STOP, its text requests with that store are cancelled.
Shopper mobile number (stored encrypted); a record of each time they ticked the SMS consent box: the time, the exact wording shown, the page, the store language, the browser and the IP address (stored encrypted); the confirmation text sent in reply; and any opt-out reply	The “Notify me” form, and replies to our texts	To send the texts they asked for, to show proof of their consent if Twilio or a carrier asks for it, and to honour opt-outs, which are remembered for that store. Only collected when the merchant turns the phone field on. The number is added to the store’s customers in Shopify; SMS marketing consent is never recorded there.
The price a shopper saw when asking for a price-drop alert	The “Notify me” form	To know when the price has dropped below it
Order number, order total, currency and the item bought	Shopify order webhooks	To attribute a purchase to an alert (within 14 days) so merchants can see recovered revenue. The order’s email address is read to make the match; it is turned into a keyed hash for the lookup and is not stored. We don’t use or store the buyer’s name, address or payment details.
Store domain, chosen plan, email wording and sending rules, the store’s postal address, product and inventory data	The merchant and the Shopify API	To run the app for that store. The postal address is shown at the end of the alert emails the store sends.
The store’s contact email address	The Shopify API, read each time it is needed and not stored	To email the merchant when alerts stop sending and when they recover, before a dedicated texting number is released, and with the data a shopper asked the store for (see “Shoppers’ rights”).
For a dedicated texting number: the business’s legal and trading name, registration number (such as an EIN), address, website and type; a contact person’s name, email and phone; the product page and screenshot given as opt-in proof; and when the merchant agreed to the number’s terms	The merchant, on the app’s SMS page	To register the store’s number with Twilio and the carriers in the business’s name, which they require, and to show what was agreed. The screenshot is served at an unguessable address for the carriers’ review.
The merchant’s own mobile number, if they save one for test texts	The merchant, on the app’s SMS page	To send the test texts the merchant asks for from the SMS page, and only to that number. It is deleted with the rest of the store’s data after the app is uninstalled.
Shopper IP address	The “Notify me” form	To limit abusive signups, which only holds it in memory. For a text request it is also stored, encrypted, in the consent record described above.

The storefront form sets no cookies. It keeps a single flag in the browser’s session storage so it reports that it is installed only once per visit.

What goes to the store’s Shopify admin

Shopify requires apps to return customer details collected on a store to that store. Within a few minutes of a request, Reshelf adds the shopper to the store’s customers in Shopify with the email address or mobile number they gave and the tag “Reshelf”. If the shopper is already a customer of the store, only the tag is added. Where a shopper gave both an email address and a mobile number, both are put on one customer record when Shopify allows it; details already on a customer record are never replaced.

If the shopper ticked the newsletter box, the customer is also marked as subscribed to email marketing, dated when they ticked it, so the store’s Shopify admin matches what the shopper chose. Reshelf never unsubscribes anyone, and doesn’t override a customer who unsubscribed after ticking the box. SMS marketing consent is never recorded: the text-alert box covers alert texts about one item, not the store’s other marketing. Nothing else is sent: not the product they asked about, and no name, because the form doesn’t ask for one.

Merchants can turn this off in the app’s Settings. Customer records in Shopify belong to the merchant and are kept by Shopify under the merchant’s own policies: they stay when a request is deleted from Reshelf or the app is uninstalled, and the merchant can edit or delete them in the Shopify admin.

How long we keep it

A request that is still waiting after 90 days expires and is deleted.
A request that has been alerted is deleted 35 days after the alert, whether or not it was cancelled afterwards.
A request cancelled before any alert went out is deleted 90 days after it was made.
SMS consent records are kept for 12 months after the consent, so it can be proven if Twilio or a carrier asks. A store’s list of numbers that opted out of its texts is kept, as keyed hashes rather than the numbers themselves, while the store uses the app.
Alert log entries are kept for 90 days. An entry identifies the shopper by a keyed hash of their email address or mobile number (a one-way code that only our secret key can match), not by the address or number itself, and the hash stays in the entry after the request is deleted, until the 90 days are up. If an alert failed, the error the provider reported is kept with it, with any email address or phone number in it removed. When a shopper’s erasure request arrives through Shopify, their entries are deleted outright.
To honour unsubscribes and spam complaints, a store keeps a suppression record (a keyed hash of the email address, not the address) until the shopper’s or the store’s erasure request arrives through Shopify.
Order attribution records are kept while the merchant uses the app, and are deleted sooner when a shopper’s erasure request arrives through Shopify.
When a merchant uninstalls the app, sending stops immediately; Shopify sends us an erasure notice 48 hours later and the store’s data is deleted then.
A dedicated texting number is paused when the merchant uninstalls, in case they reinstall. When the store’s data is erased (and in any case 7 days after uninstalling), or when the merchant releases the number, we delete the texts stored in the store’s Twilio account, release the number and close the account. Twilio may keep deleted messages in its backups for up to 30 days. When a shopper’s erasure request arrives, we delete the texts to and from their number in the store’s Reshelf-managed Twilio account. Texts sent through a merchant’s own Twilio account stay in that account, under the merchant’s control. After the account is closed, we keep a record of it (the store’s domain, the number and Twilio’s IDs for them, no shopper data), including after the store’s data is deleted, so Twilio’s charges can be reconciled.
The business details, opt-in proof and agreement record given for a dedicated texting number are kept with the store’s settings while the app is installed, including after the number is released, so they can be reused for a new number. They are deleted with the rest of the store’s data after the app is uninstalled, as above.

Who else handles it

We use a small number of providers to run the service. Each only receives what it needs:

Shopify (platform, billing, and the webhooks that tell us about inventory and orders). Unless the merchant has turned it off, each shopper’s email address or mobile number and the “Reshelf” tag are written to that merchant’s own customer list in Shopify, as described above. A newsletter tick is written as email marketing consent; SMS marketing consent never is.
Railway (hosting and database, United States).
Cloudflare (DNS and network for getreshelf.com). Every request to this website and to the app, including the storefront form’s requests that carry a shopper’s email address or mobile number, passes through Cloudflare on its way to our servers. Cloudflare also forwards email sent to our support address.
Google Fonts (the typefaces on this website, getreshelf.com). A visitor’s browser loads them from Google, which receives the visitor’s IP address and browser details. The app inside the Shopify admin, the storefront form and the alert emails don’t load them.
Resend (sending the alert emails and reporting delivery, and the emails we send merchants at their store’s contact address). Resend keeps its own records of the emails sent, under its own retention.
Twilio (sending alert texts and reporting delivery). Every text goes out from a number that belongs to one store. With a dedicated number set up through Reshelf, the shopper’s mobile number and the message pass to Twilio under our account, and the merchant’s business details are sent to Twilio and carriers for the verification they require. A merchant using their own Twilio account has their own agreement with Twilio.
Klaviyo, only for merchants who connect their Klaviyo account, and only for shoppers who ticked the newsletter box: their email address, the requests they ticked it on, the alerts sent for those requests, and the newsletter opt-in are sent to that merchant’s Klaviyo account under Klaviyo’s terms. Mobile numbers are never sent to Klaviyo. A shopper who didn’t tick the box is not sent to Klaviyo.
Shopify Flow, if the store uses it: when a back-in-stock request is made with an email address, and when its alert email is sent, the shopper’s email address, the product, and the product and variant titles are sent to that store’s Shopify Flow, where the merchant’s own workflows can use them. Mobile numbers are never sent to Flow.

We don’t sell personal data, and we don’t use shopper emails for our own marketing.

Where it is processed

Scorptek LLC is in the United States, and Reshelf’s servers and database are hosted there. If you or your shoppers are outside the United States, including in the European Economic Area or the United Kingdom, the data described here is transferred to the United States and processed there, where data-protection law may differ from the law where you are. The providers above may also process it in other countries.

Text messages

A shopper is only texted if they entered a mobile number and ticked the consent box on a store’s “Notify me” form. Message frequency: message frequency varies with the number of requests: one confirmation text when the shopper asks, then one text when the item comes back in stock or its price drops — we never send a shopper a text for anything they didn’t ask for. Alert texts are sent between 8 a.m. and 9 p.m. in the shopper’s time zone. Message and data rates may apply. Reply STOP to any text to opt out, or HELP for help. STOP applies to the store whose number sent the text, and cancels every text request with that store.

Mobile numbers and SMS consent are not shared with third parties for marketing purposes.We don’t sell or rent them. A shopper’s number goes to Twilio and the delivering carrier so the alert can be sent. It is never sent to Klaviyo. It is also added to the customer list of the store the shopper signed up with, in that store’s Shopify admin, as a contact detail only: no SMS marketing consent is recorded with it. The consent the form collects covers texts about the item the shopper asked about (the confirmation and the alert) and nothing else; a merchant’s newsletter opt-in is a separate box, unticked by default, and covers email only.

Shoppers’ rights

Every alert email has a link to cancel the request, which opens a page to confirm and to stop all alerts from that store to the address if they prefer, and a one-click unsubscribe header that mail apps can show as their own button. Replying STOP to a text cancels text requests with that store. Shoppers can also ask the store to delete their request, which the merchant can do from the app; the customer record in the store’s Shopify admin is the merchant’s to delete there. Requests for access or erasure that a shopper makes through Shopify are passed to us automatically and honoured within 30 days. For an access request, we email the store’s contact address everything we hold for that shopper, for the store to pass on to them. For an erasure request, we delete the shopper’s requests, their alert log entries, their SMS consent records and opt-out, their email suppression record, and the orders attributed to them. Depending on where you live (for example under the GDPR or the CCPA), you may have further rights to access, correct, delete or restrict use of your data; contact the store you bought from, or us at support@getreshelf.com.

Merchants’ responsibilities

Merchants decide what the form says and whether it offers a newsletter opt-in. If you enable the opt-in and export those addresses, or use the customers Reshelf adds to your Shopify admin, you are responsible for using them lawfully, including getting any confirmation of the opt-in that the law where you sell requires. The Reshelf tag shows which customers came from the form; it is not marketing consent. The form doesn’t confirm the address, so a newsletter opt-in is recorded as single opt-in.

Security

Shopper emails and mobile numbers, and merchants’ Twilio and Klaviyo credentials, are encrypted at rest with a key that lives outside the database. All traffic uses HTTPS. Storefront requests are verified as coming through Shopify before they are accepted. Each time shopper details are viewed, exported, sent to or deleted in the app, Reshelf records the store, the staff account, the action and the time, never the details themselves, and keeps that record for 12 months.

Changes and contact

If this policy changes in a way that matters, the date at the top changes and merchants are told in the app. Questions: support@getreshelf.com.