Moving your data
Last updated: 17 October 2026
This page is not finished: some details below are still missing.
The data Tagwright keeps for your store is yours to take to another service, or to your own systems, at any time. This page says how, what the file holds, and where your data is. Our terms of service set out your rights under “Moving your data”.
How to move your data
- In Tagwright, open “Your data” and choose “Download your data”. You get the file at once, on every plan, as often as you like.
- Give the file to your new provider, or keep it. If you want us to work with your new provider, or need something the file does not hold, write to us at support@countinghouseapps.com or with our contact form: we give it within the transition period.
- When you have what you need, uninstall Tagwright. That ends our agreement; we email your store that it has ended, and erase your store’s data as our privacy policy describes.
There is no notice period. The transition period is 30 days from when you ask, and you can extend it once by telling us; you can download your data for as long as Tagwright stays installed. Moving your data, downloading it and erasing it are free, and there are no fees for ending the agreement early; ending it yourself does not refund a charge already paid.
The file
One file in JSON (RFC 8259), a structured, commonly used and machine-readable format, in UTF-8. Dates and times are in ISO 8601, in UTC. At its top: “format” (“Tagwright store data”), “version” (1), “exportedAt” (when it was made) and “store” (your store’s myshopify.com address). Then one list for each part below, under the name given, with one entry per record; a part with nothing in it is an empty list. No common specifications or harmonised standards for this kind of service have been published in the EU yet.
What the file holds
Print list (“printList”)
The print list's stock location.
- “locationId”: The Shopify id of the stock location chosen for the list.
- “updatedAt”: When the list last changed.
Print list rows (“printListItems”)
Each product variant on the print list.
- “id”: The row's number.
- “variantId”: The variant's Shopify id.
- “quantity”: The number of labels typed or taken from a transfer or an order; empty when it follows the stock.
- “note”: The note typed for its labels.
- “addedAt”: When it was added.
Orders on the print list (“printListOrders”)
Each order added to the print list (kept encrypted; given here in the clear).
- “id”: The record's number.
- “orderId”: The order's Shopify id.
- “name”: The order's number, such as #1001.
- “itemIds”: The numbers of the print list rows holding its counts.
- “addedAt”: When it was added.
Shopify's requests about a customer's data (“dataRequests”)
Each request Shopify sent about one of the store's customers, until it is answered (kept encrypted; given here in the clear).
- “id”: The record's number.
- “requestId”: Shopify's id for the request.
- “orders”: The customer's orders on the print list: each one's Shopify id and number.
- “receivedAt”: When it came.
Label templates (“templates”)
Each label template.
- “id”: The template's number.
- “name”: Its name.
- “format”: The label size it prints on: a built-in size's code, or custom-<number> for a custom size below.
- “settings”: What it prints and how (Tagwright's own template settings), with a logo's black and white dots when it has one.
- “isDefault”: Whether it is the default template.
- “createdAt”: When it was made.
- “updatedAt”: When it last changed.
Starter templates given (“starterTemplates”)
Which built-in label sizes the store was given a starter template for.
- “format”: The label size's code.
- “createdAt”: When it was given.
Custom label sizes (“labelSizes”)
Each label size the store defined, in millimetres.
- “id”: The size's number.
- “name”: Its name.
- “printer”: The printer kind it is for.
- “labelWidthMm”: The label's width.
- “labelHeightMm”: The label's height.
- “marginMm”: The margin kept clear inside each label.
- “paper”: For a sheet: the paper size.
- “columns”: For a sheet: labels across.
- “rows”: For a sheet: labels down.
- “firstLabelXMm”: For a sheet: the first label's distance from the left edge.
- “firstLabelYMm”: For a sheet: the first label's distance from the top edge.
- “pitchXMm”: For a sheet: the distance from one label's left edge to the next.
- “pitchYMm”: For a sheet: the distance from one label's top edge to the next.
- “createdAt”: When it was made.
- “updatedAt”: When it last changed.
News about reports (“notices”)
Each piece of news the app has for the store about its reports.
- “id”: The news item's number.
- “reportId”: The report it is about.
- “kind”: What happened (fixed, declined, extra labels given, a feature shipped).
- “subject”: What the news names, such as the feature.
- “grantUntil”: For a Pro feature given: until when.
- “shownAt”: When the app showed it.
- “createdAt”: When it was made.
Problems and ideas sent (“reports”)
Each problem or idea the store sent us.
- “id”: The report's number.
- “kind”: A problem or an idea.
- “status”: Where it stands.
- “message”: What was typed.
- “setup”: For a problem: the setup typed.
- “workaround”: For a problem: the workaround typed.
- “details”: For a problem: the details the form showed (page, label format, printer kind, browser and system).
- “plan”: The store's plan when it was sent.
- “declineReason”: Our reason, if it was declined.
- “rewardedAt”: When we thanked the store for it.
- “publishedRequestId”: The published request it became part of.
- “createdAt”: When it was sent.
- “updatedAt”: When it last changed.
Votes (“votes”)
Each published request the store voted for.
- “id”: The vote's number.
- “publishedRequestId”: The published request voted for.
- “createdAt”: When the vote was given.
Barcode numbering (“barcodeNumbering”)
Where the store's created barcodes go on from.
- “next”: The next number Tagwright will use.
- “runUntil”: Until when a barcode run holds the numbering.
Labels per month (“labelCounts”)
How many labels the store downloaded each month.
- “month”: The month (YYYY-MM), in the store's time zone.
- “labels”: How many labels.
Print-menu windows (“printMenuWindows”)
How many labels each open Print-menu window has counted (kept an hour).
- “id”: The window's random id.
- “labels”: How many labels it counted.
- “openedAt”: When it was opened.
Extra labels given (“extraLabels”)
Each thanks with extra labels.
- “id”: The thanks' number.
- “reportId”: The report it thanked.
- “labels”: How many labels.
- “grantedAt”: When they were given.
Pro features given (“featuresGiven”)
Each Pro feature given to the store for a time.
- “id”: The gift's number.
- “feature”: The feature.
- “until”: Until when.
- “createdAt”: When it was given.
Notes closed (“closedNotes”)
Each note about Pro features the store closed.
- “id”: The record's number.
- “banner”: Which note.
- “dismissedAt”: When it was closed.
How the store used Tagwright (“usage”)
What the store did in Tagwright, in our own words: kept 13 months, except when it first opened Tagwright.
- “id”: The record's number.
- “kind”: What the store did, such as downloading labels or opening the Plan page.
- “detail”: For labels, their format (a size of the store's own only as “custom”); for a feature, which one.
- “count”: How many labels, or 1.
- “at”: When.
Email address (“contact”)
The store's email address in Shopify, for the notices the terms promise.
- “email”: The address.
- “readAt”: When it was last read from Shopify.
Plan (“plan”)
The store's plan, as Shopify last reported it.
- “shopGid”: The store's Shopify id.
- “plan”: Free or Pro.
- “planHandle”: The plan's handle in Shopify.
- “checkedAt”: When Shopify was last asked.
- “failedAt”: When asking Shopify last failed.
Open requests (“openRequests”)
Each request about the store we must still answer by a date.
- “id”: The request's number.
- “kind”: What it asks for.
- “receivedAt”: When it came.
- “dueAt”: When it must be answered.
- “createdAt”: When we recorded it.
What is left out, and why
- Sign-in: The access tokens Shopify issues to Tagwright for the store, and how they are kept: handing them out would let anyone holding the file reach the store's data, so they are left out for the security of the service.
- Open requests, “requester”: Who asked: their own email address, which may not be the store owner's, so it is given to them on request, not in the store's file.
- Open requests, “note”: Our own note on how we handle it.
- Open requests, “storeUninstalledAt”: When the store uninstalled Tagwright: it only sets how long the request may be kept.
- Each record’s store: named once, at the top of the file, instead.
- Our server logs, backups and error reports: they keep the service running and secure, and are deleted on their own schedules (our privacy policy says when).
- Emails between you and us: they are in our mailbox, not in the database; ask us, and we send you what we hold.
- Tagwright itself: its code, its built-in label sizes and starter layouts, and its fonts. Nothing of your data is held back as our trade secret.
Known risks, and what to know before you move
- Tagwright depends on Shopify: Shopify can limit or end Tagwright’s access to your store at any time, and Tagwright may then stop working without warning (our terms, “Availability and changes”). Download your data early in your move.
- Label templates are in Tagwright’s own format: another app may not read them as they are.
- Label files (PDF and ZPL) are made when you download them and are not kept, so they are not in the file: download the labels you need first.
- Barcodes Tagwright created are saved in your Shopify products, and stay there.
- What you have not downloaded before you uninstall cannot be recovered.
Where your data is held
Tagwright, its database and its backups run on servers of Hetzner Online GmbH in Germany, in the European Union, and are subject to the law of Germany and of the European Union; we are established in Lithuania. Our emails with you are kept by Hetzner Online GmbH, which may process them in [not set: PRIVACY_EMAIL_COUNTRIES].
Protection from access by governments outside the EU
To keep the data we hold in the EU from unlawful access by governments outside it: the database cannot be reached from the internet; Shopify access tokens, order ids and numbers, and the addresses of people who send us requests are stored encrypted; backups are encrypted with a key locked by a passphrase that is never stored on the server; and only we can sign in to our server and database.
We give an authority outside the EU access to your data, or transfer it, only where Article 32 of the EU Data Act allows it, such as on an international agreement like a mutual legal assistance treaty. We then give the least the request needs, and we tell you before we comply, unless the request serves law enforcement and only for as long as telling you would undermine it.
Contact
Questions about moving your data: support@countinghouseapps.com, or our contact form.