Privacy policy
Effective 17 August 2026
Packlog turns the orders a merchant has already shipped into packaging reports for extended producer responsibility (EPR) schemes. It needs to know what packaging left the warehouse and roughly where it went — nothing about the people who received it.
Who we are
Packlog is operated by Digit Grove, the data controller for the information described on this page. You can reach us at support@digitgrove.com, or by post at #16, Subramaniam Nagar, Kolathur, Chennai 600099, Tamil Nadu, India.
Where a merchant installs Packlog, that merchant is the controller of their own store’s data and we act as their processor.
The short version
Packlog does not collect, store or process the personal data of your customers. Not names, not email addresses, not shipping addresses, not phone numbers, not payment details. An order reaches our database as a reference number, a date, a destination country, and a list of product IDs and quantities. That is everything the law requires us to weigh, and it is everything we keep.
What we access, and what we store
Packlog requests two permissions and no others: read_products and read_orders. Both are read-only — Packlog cannot alter anything in your store.
From your store
| What we store | Why |
|---|---|
| Order reference and order number | So a figure in a filed report can be traced back to the parcel behind it during an audit |
| Order date | Decides which reporting period the packaging falls in |
| Destination country and province or state | Decides which scheme applies. No street address, city or postcode is read or stored |
| Product and variant references, and quantities | Matches each item to the packaging you mapped to it, so the weight can be calculated |
| Cancellations and refunds | Reverses packaging already counted, so reported totals stay net and correct |
| Product titles and variant names | So you can recognise your own catalogue when mapping packaging to it |
Customer records are never requested, and the fields that would identify a person are not part of the data we retrieve.
From you
- Your registered producer identity for each scheme: legal entity name, registration number (such as a LUCID number), VAT number, business address, compliance contact email, and any notes you add. These are business details you enter yourself, and they appear on the reports Packlog generates because the registry requires them.
- Your packaging library: components, materials, weights, and the rules mapping them to your products.
- An email address for notifications, if you choose to receive deadline reminders.
Automatically
- Your store’s domain, name, plan, timezone and owner email, as provided when the app is installed.
- An access token permitting the two read-only scopes above. Packlog uses offline access tokens, so no individual staff member’s name or email address is stored.
- Server logs containing request paths, timings and errors, retained for operational troubleshooting.
Why we are allowed to hold it
For merchants in the UK and EU, our lawful basis under the UK GDPR and EU GDPR is performance of a contract — you asked us to calculate and document your packaging obligations, and this is the data that calculation runs on. Keeping a filed report reproducible afterwards rests on our legitimate interest and yours in being able to defend a regulatory submission you have already made.
Who else sees it
We do not sell data, share it for advertising, or use it to train machine-learning models. It is disclosed only to the service providers that run the product:
| Provider | Purpose | Location |
|---|---|---|
| Google Cloud Run | Runs the application | Frankfurt, Germany (europe-west3) |
| Neon | Hosts the database | European Union |
| Resend | Sends the welcome email and any deadline reminders you opt into | Recipient address only |
We may also disclose information where the law requires it. We will tell you first unless we are prohibited from doing so.
Packlog does not file on your behalf
This is worth stating plainly, because it limits what we can do with your data. Packlog produces a file and you submit it. We hold no account with any packaging registry, we transmit nothing to LUCID, CITEO, the UK Report Packaging Data service, the Circular Action Alliance or any dual system, and no figure becomes a regulatory submission until you enter it there yourself. Packlog is a configuration and documentation tool, not a compliance scheme, and nothing it produces is legal advice.
Where it lives, and for how long
Data is stored in the European Union and encrypted in transit. We keep it for as long as the app is installed, because an EPR filing has to stay explicable for years after the period it covers.
When you uninstall:
- your access token is revoked and the session deleted immediately;
- 48 hours later, everything else is permanently erased — company details, packaging library, product mappings, the order ledger, and every report including those already filed.
Filed reports are otherwise protected against deletion, so that a submission cannot be quietly rewritten after the fact. Erasure deliberately overrides that protection: a right to be forgotten that stops at our convenience is not a right.
Your rights
You may ask us to give you a copy of your data, correct it, delete it, or restrict what we do with it, and you may object to processing. Two of those need no request at all:
- Access and portability — Packlog has a full data export built in, on every plan including the free one. It produces every table the app holds about your store as CSV files. Access tokens are deliberately excluded from it.
- Erasure — uninstalling triggers the deletion described above, with no need to contact us.
For anything else, write to support@digitgrove.com and we will respond within 30 days. If you are in the UK or EU and are unhappy with our answer, you may complain to your national data protection authority.
Requests about a shopper
Stores are obliged to answer data requests from their own customers, and Shopify forwards those to installed apps. Packlog receives and logs each one. Because we hold nothing that identifies a shopper, there is never anything to return and never anything to erase — and we record that answer rather than staying silent, so a merchant can evidence it.
Security
- All traffic is encrypted with TLS.
- Credentials are held in a managed secret store, readable only by the application’s own service account and granted per secret rather than across the project.
- Each store’s data is isolated and every query is scoped to the store that owns it.
- The strongest control is the one above: the highest-risk category of data is absent rather than protected.
Cookies
Packlog sets a session cookie so the app stays signed in while you use it inside your admin. There are no advertising cookies, no third-party analytics and no cross-site tracking.
Children
Packlog is a business tool, is not directed at children, and is not intended to be used by anyone under 16.
Changes
If we change what we collect or why, we will update this page and move the effective date at the top. Material changes will also be sent to the notification address on file.
Contact
Questions about this policy, or about anything Packlog holds: support@digitgrove.com.