Privacy Policy
Scribe was called The Usual until November 2026. The app, its data and this policy are the same; this version adds purchase orders uploaded in the app and receipts sent to buyers.
How Scribe handles data from the Shopify stores that install it, and from the buyers who use it. This policy covers the app only. True COGS has its own policy.
The short version
- The app stores identifiers, not people. Company, location and contact IDs, and the ID of a buyer who changes an order or asks for a new one.
- Names, addresses, phone numbers and email addresses are never written to our database. They are read from Shopify at the moment they are needed — to create an order, or to send a reminder — and not kept. The one exception is a purchase order the merchant forwards or uploads to the app: its files are kept as received for 30 days, then erased.
- Email is used only for the orders themselves. The merchant gets alerts about orders that need attention. When the merchant turns them on, a buyer gets a reminder before their order's deadline, and a notice when their order goes out changed or the store's closure skips or moves it. The merchant can name other contacts of the same company location to get the same emails. No marketing email.
- Nothing is sold, shared for advertising, or used to profile anyone. There is no tracking and no automated decision-making with legal effect.
- Uninstall deletes everything. All of a store's data is erased when Shopify confirms the uninstall.
1. Who we are
Scribe Draft Order Import ("the app") is a Shopify application published by Nexus Logic Systems ("we", "us"). The app places a Shopify B2B company location's recurring order on a schedule set by the merchant.
For data protection law, the merchant who installs the app is the controller of their store's data and we act as a processor on their instructions. Where we decide how and why data is handled — for example, our security logs — we are the controller for that limited purpose.
2. What the app accesses
The app requests the narrowest set of Shopify access scopes that lets it do its job. It reads and writes only what each feature needs.
| Data | Why the app needs it | Written to our database? |
|---|---|---|
| Companies, company locations and contacts | A standing order belongs to one company location and is placed for one contact | Identifiers and the business names shown in the app |
| Contact and recipient names | The merchant picks a contact by name; the recipient name on the location's shipping address goes on the order | No — read live, shown, then discarded |
| Company location shipping address and phone | Copied onto each order so it ships to the right place | No — read at order time and sent to Shopify on the order |
| Customer records of company contacts | To confirm a signed-in buyer may manage their location's standing orders | Only the buyer's customer ID, and only on actions they take |
| Company contacts' email addresses, first names and language | To email the contact an order is placed for — and up to five other contacts of the same company location that the merchant names on the standing order — a reminder before an order's change deadline, and a notice when an order is placed without an item or with fewer than asked for, or when a closure skips or moves it. Each kind is sent only when the merchant turns it on, and is written in the language Shopify holds for that contact | The address and name: no — read at the moment of sending and passed to our email provider only to deliver the message. The language code (for example fr) is kept on the queued email |
| The store's own email addresses | Alerts to the merchant go to the store owner's address (or one the merchant sets); the store's contact address is the reply-to on buyer reminders | Yes — the store owner's and contact addresses, refreshed from Shopify |
| Past orders a buyer asks to repeat | When a buyer chooses "Make this my usual" on an order, to read its items and check it belongs to their company | The order's identifier and name, the items to repeat, the schedule asked for and the buyer's optional note |
| Purchase orders the merchant forwards to the app by email, or uploads in the app | To read the order (tables by code; PDFs and the email's text by an AI model, every line checked against the document), find which company location it is for, match its items to products, price it at that location's prices, compare it with the location's usual order, and create the order the merchant approves. To find the location, the sender's email address is looked up among the store's customers | What was read — items, quantities, prices, purchase order number, dates, business names — with any email address removed; the sender's customer ID when they are one of the store's customers; the files themselves for 30 days. The sender's address: no — looked up, then dropped |
| Products, variants and stock levels | To price the order in the buyer's catalog and check items are available before placing it | Variant identifiers, titles and quantities on the standing order |
| Draft orders and orders | The app creates each order and reads back the order it produced. When the merchant turns on the credit hold, it also reads whether a company location's recent orders are overdue and what is still owed on them | Order and draft identifiers, names and totals; for a credit hold, the overdue orders' names and the amount outstanding, in the reason the order was held |
A buyer's email address is read only to deliver an email about their own orders, or to find which account a purchase order they sent is for, and is never stored. Invoices and order confirmations are sent by Shopify, not us.
3. What is stored, and for how long it lives in our database
The app's database holds the merchant's configuration and an audit trail. In detail:
- Store record: the store's myshopify.com domain, its time zone and display name, its plan, and the encrypted Shopify access token that lets the app act on the store's behalf.
- Standing orders: the name the merchant gave it, the company, location and contact identifiers (the contact it is placed for, and any other contacts the merchant named to receive its emails), the business and location names for display, the product variants and quantities, the schedule, a pause and the date it ends, and the placement settings.
- Runs: one record per scheduled order date, with its status, the items as they were locked in (including any extra items added for that order only), the prices Shopify calculated, the purchase order number, its delivery date, whether and when the buyer confirmed it, why it was held, any items left out of it or sent short, and any resulting draft or order identifier.
- Audit trail: a dated list of what happened — orders placed, orders held and why, emails sent, buyer confirmations, skips, quantity changes and extra items. When a buyer takes the action — in their customer account, or from the order link in a reminder email — their Shopify customer ID is recorded so the merchant can see who did it.
- Requests: when a buyer asks to repeat a past order, the order's identifier and name, the items, the schedule asked for, the buyer's customer ID, their optional note, and the merchant's answer.
- Purchase orders received by email: what was read from each (items, quantities, prices, purchase order number, dates, business names, with any email address removed), the company location it was matched to and how, the sender's Shopify customer ID when they are one of the store's customers, the checks the app made, the order it led to, the number of AI tokens used, and the files as received — the files for 30 days only. Item codes a merchant confirms are remembered for that company.
- Email queue: what each alert, reminder or notice says (for example the order date and items), the language it is written in, and whether it was delivered — never the address it went to.
That is the complete list. No customer name, postal address, phone number or email address from Shopify is written to our database at any point. A note a buyer types on a request is kept as they wrote it, and a forwarded purchase order's files are kept as received for 30 days, so they hold whatever the buyer wrote in them.
4. Why we handle this data
- To place the merchant's orders on the schedule they set, with the right prices, purchase order number and payment terms.
- To check an order before it goes out and hold it when a price has moved, stock has run out, an item has been removed, or — when the merchant turns this on — the company location has an overdue invoice.
- To show buyers their upcoming orders in their customer account and let them confirm, skip or adjust one before the deadline, and to remind them by email when the merchant turns reminders on — with a link that opens that one order, in their language.
- To tell buyers when their order changes — placed without an item or with fewer than asked for, or skipped or moved because the store is closed — when the merchant turns these notices on.
- To turn the purchase orders a merchant forwards into orders — read, matched to the right account and products, priced, and checked against that account's usual order and upcoming orders — so nobody re-types them.
- To alert the merchant by email when an order is held, fails, is ready for review, went out short of an item, or a buyer sends a request.
- To give the merchant an audit trail of what the app did and what their buyers changed.
- To keep the service working and secure — error diagnosis, abuse prevention and billing.
We do not use any of it for advertising, we do not sell or rent it, and we do not build profiles of merchants or their customers.
5. Legal bases (UK and EU merchants)
Where the UK GDPR or EU GDPR applies, we rely on these bases. The merchant, as controller, is responsible for the basis on which they instruct us.
| Purpose | Basis |
|---|---|
| Running the app for a merchant | Performance of a contract with the merchant |
| Placing orders that contain buyer details | Processing on the merchant's documented instructions, on their legal basis |
| Security logs and abuse prevention | Our legitimate interest in keeping the service safe |
| Answering support requests | Performance of a contract, and our legitimate interest in supporting users |
| Meeting Shopify's compliance obligations | Legal obligation, and contract with Shopify |
6. Who else sees the data
Five companies process data on our behalf. We use no analytics, advertising, session-recording or marketing services in the app.
| Provider | Role | Where |
|---|---|---|
| Shopify | Source of the store data and the platform the orders are created on; sends invoice and confirmation emails | Per Shopify's own terms |
| Render | Runs the application | United States |
| Neon | Hosts the PostgreSQL database | United States |
| Resend | Delivers the app's emails: alerts to merchants, and reminders and order notices to buyers. Receives the purchase orders merchants forward to the app | United States |
| Anthropic | Reads the purchase orders merchants forward to the app (PDFs, and the email's text with email addresses removed), only to turn them into orders. By default, Anthropic doesn't use data sent through its API to train its models | Stored in the United States; processed in the United States, Europe, Asia or Australia |
Because our hosting is in the United States, data from the UK, the EEA or Switzerland is transferred there. Those transfers rely on the European Commission's Standard Contractual Clauses, with the UK Addendum where relevant, in our agreements with each provider.
We may also disclose data where the law requires it, or to establish or defend legal claims. If our business or this app is ever transferred to another owner, this policy travels with it and merchants will be told before anything changes.
7. Retention and deletion
- While the app is installed, standing orders, runs and the audit trail are kept so merchants have a complete record of the orders the app placed.
- Purchase orders received by email: their files are erased 30 days after they arrive; the record of what was read and ordered stays while the app is installed. When the merchant uninstalls, all of them are deleted at once.
- When a merchant uninstalls, Shopify sends a shop redaction request. On receiving it, the app deletes the store's record, its standing orders, runs, audit trail and stored session — everything it holds for that store.
- When a customer asks a merchant to erase them, Shopify sends a customer redaction request. The app removes that customer's identifier from every audit entry and request, erases the notes they wrote on requests, deletes the purchase orders they emailed (with their files), and deletes any queued email that quoted them, leaving anonymous records of what happened to the orders.
- When a merchant forwards a customer data request, the app compiles the entries, requests and purchase orders linked to that customer's identifier so the merchant can answer within the legal deadline.
- Email delivery records are kept by Resend under its own retention settings; they hold the address a message went to and whether it was delivered.
- Server logs are kept briefly for diagnosis. They record store domains, identifiers, counts and error messages — never customer names, addresses, phone numbers or email addresses. Values under keys that look like tokens, secrets, passwords, authorization headers or cookies are removed before anything is written, and the secret part of an order link is never logged.
8. Security
- In transit: HTTPS everywhere, and the database refuses connections that are not encrypted with TLS.
- At rest: the database is encrypted with AES-256, and its backups are encrypted too.
- Webhooks from Shopify are rejected unless their signature verifies.
- Order links in reminder emails open one upcoming order without signing in. Each is signed for that order and the one company contact it was sent to. It stops working if the store takes that contact off the standing order or the contact loses access to the location, and expires a week after the order's deadline. The page shows items and quantities — never prices, addresses or other orders — and is never cached, indexed or embedded in other sites.
- Secrets exist only as environment variables on the hosting platform. They are never committed to source control or written to logs.
- Access to production systems is limited to the accounts that operate them, each protected by two-factor authentication.
- Testing is done against separate databases and Shopify development stores. The test suite refuses to run against anything that is not an explicitly named test database.
No system is perfectly secure. If a breach affects a merchant's data, we will notify the affected merchants without undue delay and describe what happened, what it affects and what we are doing about it.
9. Your rights
If you are a merchant, you can ask us for a copy of what we hold about your store, ask us to correct it, or ask us to delete it. Uninstalling the app deletes it automatically. You may also object to or restrict processing, and complain to your data protection authority.
If you are a buyer whose company orders through a store using this app, the merchant is your point of contact: they hold your details, and we act on their instructions. Send your request to the store you buy from and it reaches us through Shopify's redaction process. You are welcome to write to us directly and we will help the merchant answer.
If you are in California, we do not sell or share personal information as the CCPA defines those terms, and we do not process it for cross-context behavioural advertising.
10. Children
The app is a business tool sold to merchants. It is not directed at children, and we do not knowingly handle the personal information of anyone under 16.
11. Changes to this policy
If this policy changes, the effective date and version at the top of the page change with it. A change that materially affects how merchant or buyer data is handled will be announced to installed merchants before it takes effect.
12. Contact
Write to support@nexuslogicsystems.com for any privacy question, data request or security report. Put Privacy in the subject line and we will reply within 30 days, and sooner for anything urgent.
Nexus Logic Systems, United States.