Blacklark

Blacklark privacy policy

Effective date: 16 November 2026

Blacklark is a Shopify app. It lets a shopper ask to be emailed when a sold-out product is back in stock, and sends that email on the store's behalf. This policy explains what data Blacklark collects, why, how long it is kept, who else sees it, and the choices shoppers and merchants have. It is written for merchants who install the app and for shoppers who sign up through a store that uses it.

Who we are

Blacklark is operated by Herdís Helga Helgadóttir, Copenhagen, Denmark. You can reach us at support@blacklark.app.

Our role

What we collect and why

From shoppers, through the sign-up form on the store

When a shopper submits the form, the app receives their email address, the product and variant they asked about, and the store it came from. The app records the time of sign-up, whether the address was confirmed, and whether the alert has been sent. The form also sends the language the store was shown in, and the app keeps it with the sign-up when it is one the app supports (English, German, French, Spanish, Italian or Dutch; any other is treated as English), only to write the confirmation email, the back-in-stock email and the confirmation and unsubscribe pages in that language. That is everything the form sends. The app does not store a name, browser details, or the page the shopper came from, even though the browser's request carries some of these on its way through the store and Shopify.

The form sets no cookies and loads no third-party scripts. Its script keeps one item in the browser's local storage, restock-ping-at: the time of its last check-in, a number, used so the script checks in with the store's own domain at most once a day per browser (on every page load if the browser blocks local storage). It holds nothing about the shopper and is never sent anywhere; a shopper can clear it in the browser at any time. The script talks only to the store's own domain: the sign-up request, and that daily check-in, which the script sends with no body and no shopper data and which only lets the merchant's setup guide see that the form is on a live page. Shopify's app proxy adds the shopper's customer id (logged_in_customer_id) to every request it forwards when the shopper is logged in to the store; the app does not store it, and its access log drops the query string it travels in. The shopper's IP address is used only to compute keyed hashes for rate limiting and for stopping a source whose confirmation emails keep bouncing. The IP address itself is not stored and is not written to the app's logs. Those hashes count for 10 minutes or 24 hours and are removed by the daily cleanup (see the retention table). Our hosting provider, Railway, keeps its own log of each web request for up to 30 days. It records the time, the path without its query string (so no link token or customer id), the response status, the IP address the request came from and the browser's user-agent string.

Why. To send one confirmation email, and then at most one back-in-stock email for that sign-up once the item can be bought online again. (A shopper who confirms while the item is already back sees that on the confirmation page instead of getting an email.) The address is used for nothing else: no marketing, no profiling, no sharing beyond the providers listed below, and no sale of data. This is consistent with the consent line shown under the form by default: "One email when it's back. Nothing else."

From merchants, through Shopify's APIs

With the permissions the merchant grants at install (read_products, read_inventory, read_orders, write_app_proxy), the app reads the store's name, primary domain, contact email and currency; product and variant titles, handles, prices and images; and whether a variant can be bought online. Shopify also sends the app inventory update notifications. The app writes one setting to the store (a metafield on the app's own installation) listing the products the merchant has marked as not coming back, so the form is hidden on those pages.

Orders. With read_orders, the app receives Shopify's order-created notifications to attribute revenue to alerts: an order is matched to an alert when it contains an alerted variant, was placed with the same email address, and was placed within 7 days after the alert. The app stores only the order id, product and variant, quantity, amount, currency and date, and whether it was a test order, and when it was cancelled. It never stores the email address from the order. The app asks Shopify to send only the fields it uses (include_fields in shopify.app.toml), so the buyer's name, address and phone number are not delivered to the app. Each stored row links to the shopper's sign-up by its internal id, so the row is deleted when Shopify's customer-erasure request for that shopper is processed. (If the shopper unsubscribes instead, the sign-up is deleted but the order row, which holds no address, stays until its own 90 days are up.) Cancelled and voided orders are excluded from the merchant's totals; unpaid orders are included and refunds are not subtracted.

Customer data requests. When a customer asks the store for their data, Shopify forwards the request to the app with the customer's email address and the ids of the orders the customer asked about. If the app holds sign-ups or attributed orders for that address or those orders, it keeps the request so the merchant can see in the app what Blacklark holds and answer the customer. If it holds nothing, the request is acknowledged and not stored.

Why. To check that a sign-up refers to a real variant, to decide when the item is back, and to fill in the emails.

Optional customer sync, off by default. A merchant can turn on "Add subscribers to Shopify customers" in the app's settings. Only then does the app ask for the write_customers permission. With it on, the app looks up each confirmed subscriber in the store's customer list by email address, creates a customer record if none exists, adds the tag restock-waitlist, and stores the Shopify customer ID on the sign-up. The app never sets marketing consent on those records. Customer records and tags created this way belong to the store's customer list: the app does not remove them when a shopper unsubscribes, when it processes a customer-erasure request, when the switch is turned off, or when the app is uninstalled. The merchant manages them in Shopify, and Shopify's own customer-erasure handles the store's copy. Turning the switch off stops further syncing. If Shopify or the merchant later removes the permission, the app switches the sync off by itself.

From merchants directly

The merchant's choices inside the app: the email template (subject, heading, body, button label and colour, logo URL, and any subject, heading, body or button label written for a particular language), per-product settings (minimum stock, alerts on or off), send settings (how many shoppers are emailed per unit in stock and how often the app re-checks), the customer sync switch, how long alerted sign-ups are kept (7 days, 30 days, 90 days or 12 months after the alert; 30 days unless the merchant changes it), and the emails to the store owner described below. A test email can be sent from the app to the store owner's email address as held by Shopify. The app also stores the store's plan (free or paid, the id and status of the Shopify app subscription behind the paid plan, and whether the store is a Shopify development store, as Shopify reports them) and the month in which it last emailed the store owner that the month's alerts were used up; that email, at most one a month, goes to the same owner address, which is looked up from Shopify when it is sent and not stored.

The merchant can also get a weekly summary email (on unless turned off) and an email when a product's waiting shoppers reach a number the merchant chooses (off unless set). Both go to the same owner address, looked up when sent and not stored, and contain only counts, product titles, prices, stock and the store's own figures, never a shopper's address. For them the app stores the two settings, when the last waiting-shoppers email went out, the week of the last summary, and which products have reached the chosen number (store and product ids only). Each email has a link that turns it off without logging in; the link is signed for that store and email type, and nothing about it is stored.

The app stores one connection record per store: the store domain, the access and refresh tokens Shopify issues, and the permissions granted. It uses offline tokens only and does not store the names, email addresses or logins of the store's staff.

Automated logs

The app writes operational logs: the store domain, internal record numbers, counts, and error types. By design, shopper email addresses, IP addresses and link tokens are not written to logs, and stored error messages are scrubbed of anything shaped like an email address. Railway keeps these logs for up to 30 days.

Email delivery events

Our email provider reports what happened to each email it accepted: sent, delivered, delayed, bounced, complained, failed or suppressed. The app stores that status (failed and suppressed are recorded as bounced) and a bounce category (for example "Permanent/General") against the internal record number of the sign-up, not the address. A permanent bounce or a spam complaint on a back-in-stock email stops any further email to that sign-up; any failed delivery of a confirmation email makes its confirmation link stop working.

The app does not use open or click tracking, and both are switched off on the sending domain at the email provider.

The emails we send

Emails are sent from alerts@blacklark.app with the store's name as the sender name. Replies normally go to the store's contact email; if the store has none set, or an invalid one, they reach the sending address.

Who else sees the data

Provider What they receive Where
Shopify The app runs inside Shopify and exchanges store, product, inventory and (if enabled) customer data with it over Shopify's APIs. Per Shopify's own privacy policy.
Resend (email delivery) For every email the app sends: the sender and recipient addresses, the subject, the email body, the reply-to address when the store has a valid one, for back-in-stock emails the unsubscribe headers (which carry that sign-up's unsubscribe link), and a per-email reference so a retried request cannot send twice. Resend reports delivery events back to the app. United States. Covered by Resend's data processing addendum with the EU Standard Contractual Clauses (see International transfers). Privacy policy: https://resend.com/legal/privacy-policy
Railway (hosting) Runs the app and its database, which holds everything listed above. Amsterdam, the Netherlands (Railway's EU West region). Stored data is encrypted at rest. The database is backed up once a day and each backup is kept for 6 days.
Proton (mailbox) Email sent to support@blacklark.app or alerts@blacklark.app: messages to our support address, a shopper's reply to one of the app's emails when the store has no valid contact email, and a merchant's reply to an email from Blacklark. Switzerland, Germany or Norway, per Proton's privacy policy (https://proton.me/mail/privacy-policy). Covered by Proton's data processing agreement (https://proton.me/legal/dpa).

Product images in emails are loaded by the shopper's mail app from Shopify's image servers, and the store's logo, if the merchant set one, from the URL the merchant entered; whoever hosts that logo sees the IP address and mail app of a shopper who opens the email. Apart from these, no other company receives shopper data.

Deleting a sign-up in the app does not recall emails already delivered, and Resend keeps its own record of the emails it has sent (content, recipient address and delivery events) for 30 days, in the United States; the app cannot shorten that period or delete a single email there. So an address erased from the app after, say, 7 days can still be in Resend's records until 30 days after the email was sent.

International transfers

Every email the app sends is handed to Resend (Plus Five Five, Inc., United States), which sends it from its EU (Ireland) region and stores it in the United States. Resend's data processing addendum applies to every account and covers this transfer with the EU Standard Contractual Clauses; Resend also states that it complies with the EU-U.S. Data Privacy Framework. Its sub-processors are listed at https://resend.com/legal/subprocessors.

The app's database and its backups are stored by Railway (Railway Corporation, United States) in its EU West region (Amsterdam, the Netherlands). Railway states in its data processing addendum (https://railway.com/legal/dpa) that it processes customer data primarily in the United States, for example to operate and support its platform; that addendum covers such transfers with the EU Standard Contractual Clauses.

How long we keep data

Data Kept until
Sign-up that was never confirmed Deleted once its confirmation link has lapsed, 48 hours after the confirmation email was sent. If that email could not be delivered, deleted once 48 hours have passed since the sign-up. Also deleted when the merchant turns off alerts for the product.
Confirmed sign-up still waiting Deleted 12 months after confirming if no alert has been sent by then, or earlier when the alert is sent, the shopper unsubscribes, the merchant turns off alerts for that product (which deletes its waiting sign-ups after a confirmation prompt), the daily check finds that the product variant no longer exists in the store, a customer-erasure request from Shopify is processed, or Shopify's store-redaction request arrives after the app is uninstalled.
Sign-up that has been alerted Deleted by the daily cleanup once the store's chosen period after the alert has passed: 7 days (plus up to 2 days), 30 days (the default), 90 days or 12 months (for a shopper who confirmed while the item was already in stock, counted from confirming). Never sooner than 9 days: an order is matched to an alert for 7 days after it, and Shopify can deliver the order notification late. Deleted earlier when the shopper unsubscribes, a customer-erasure request from Shopify is processed, or Shopify's store-redaction request arrives after the app is uninstalled. The merchant's counts of alerts sent, delivered and attributed revenue come from the per-send counts, delivery records and attributed order records, which hold no address, so they do not change when the sign-up is deleted. When the daily cleanup deletes an alerted sign-up, its delivery records are detached from it: the internal sign-up number, the email provider's message id and any keyed IP hash are removed from them. (A sign-up deleted another way, such as by unsubscribing, leaves its delivery records as they are until their own 90 days are up.)
Sign-up whose address was refused by the email provider (permanent bounce, spam complaint, or the provider rejecting the address itself) after a back-in-stock email Deleted 30 days after the attempt.
Email delivery records (delivery status, the sign-up's internal number and the email provider's message id; no address; for a confirmation email also a keyed hash of the IP address it was signed up from, never the IP address itself, used to stop a source whose emails keep bouncing) Deleted 90 days after sending, or earlier with the sign-up's other data when a customer-erasure request from Shopify is processed or Shopify's store-redaction request arrives. The keyed IP hash is removed from the record by the daily cleanup once the email is more than a day old (so it can remain up to about two days), and when the cleanup detaches the record from a deleted alerted sign-up.
Rate-limit hashes (keyed hashes of the IP address, email address or store, never the IP or email address itself; for an IPv6 address, of its /64 network) Count for 10 minutes (per IP address, and per store), 1 hour (per address, per store, and a store's test emails) or 24 hours (per address across all stores, a store's confirmation emails, the sign-up attempts one IP address made at a store, a store's pause of confirmation emails after too many bounces, and when the store last resumed them). The daily cleanup deletes entries once they are more than 24 hours old, so one can remain up to about two days.
Shopify webhook receipts (ids only) Deleted after 30 days.
Background job records (no shopper addresses; the email jobs carry the store's name, its contact email, product details, and the prepared subject and body of the email without the address or link token; a confirmation email job also carries the keyed IP hash its delivery record will hold) Deleted 7 days after completion, 30 days if they failed for good. Queued ones are cancelled when the app is uninstalled.
Sell-out markers and not-live product markers (store and product ids only, no personal data) Sell-out markers are deleted by the daily cleanup after a day; not-live markers once no sign-up is waiting for the product.
Attributed order records (order id, product, variant, quantity, amount, date; no address) Deleted 90 days after the order date (the app shows 30), when Shopify sends a customer-erasure request listing the order or for that shopper's sign-ups, or when Shopify sends its store-redaction request after uninstall.
Customer data request records (email address, order ids Shopify listed, Shopify's request id, date received) Deleted when the merchant marks the request answered, 60 days after it arrived (30 days past the answer deadline), when the address's customer-erasure request is processed, or when Shopify sends its store-redaction request after uninstall.
Connection record (access and refresh tokens) Deleted at once when the app is uninstalled.
Per-send counts (store, product, variant, product title, number of emails, time; no address) Deleted about 13 months after the send (the app shows 12 months), or when Shopify sends its store-redaction request after uninstall.
Store settings, product list, email template, plan record, waiting-shoppers markers Kept after uninstall, and deleted when Shopify's store-redaction request arrives 48 hours later. (At uninstall, customer sync is switched off and the plan record goes back to free.)

Timed deletions run in a daily cleanup at 03:30 UTC, so a record can remain up to a day beyond the period shown. The 48-hour limit on confirmation links themselves is enforced exactly.

When a store uninstalls the app, its access token is deleted at once, queued work is cancelled, customer sync is switched off, and the plan record goes back to free (Shopify cancels the app's subscription with the uninstall). Sign-ups and the rest of the store's data are not deleted at that moment: they stay, so that a merchant who reinstalls keeps them, and nothing is sent for them while the app is uninstalled. Shopify then sends us its store-redaction request 48 hours after the uninstall, and we delete everything else held for that store, including every sign-up and, should the uninstall notice not have reached us, the store's connection record and its access token. Before it deletes anything, the app asks Shopify whether it is installed for that store again; if it is (the merchant reinstalled within the 48 hours, or the request is stale or repeated), nothing is deleted and the store's data stays under the retention periods above. If the app cannot confirm that with Shopify, the request is not acted on and Shopify repeats it, so an erasure is retried until it can be confirmed. Until the request arrives, those periods keep running.

Deleted rows are gone from the live database immediately. They remain in the hosting provider's daily backups, which are each kept for 6 days, and are gone from those too once the last backup containing them has expired.

Your choices and rights

If you are a shopper

If you are a merchant

If you write to us, or visit blacklark.app

Email sent to support@blacklark.app is used only to answer it and is kept for as long as the matter needs. Visiting blacklark.app sets no cookies and runs no analytics; the hosting provider's request log records the visit as described under "What we collect and why".

Legal basis for data Blacklark controls

For shopper sign-ups the store is the controller and decides the legal basis; the form is built for consent, which the shopper gives by submitting the form and confirming by email, and can withdraw by unsubscribing. For the data Blacklark controls itself, the bases under the GDPR are:

A merchant, or anyone who has written to us, can ask us for access to their data, for its correction or erasure, for its processing to be restricted, or for a copy of it, and can object to processing based on legitimate interest, at support@blacklark.app.

Complaints

If you think your data has been handled unlawfully, you can complain to the data protection authority where you live. Blacklark is based in Denmark, where the authority is the Danish Data Protection Agency (Datatilsynet, https://www.datatilsynet.dk).

Security

Children

The app does not knowingly collect data from children. A store that uses it sets its own age requirements for shoppers.

Changes to this policy

When this policy changes, the new version is published at this address with a new effective date. Before a material change takes effect, we email merchants who have the app installed, at the store email address Shopify holds for the store.