Fjordsync Privacy Policy
In short
- Fjordsync is a Shopify app that connects your store to bol.com. It lists your products on bol.com, creates your bol.com orders in Shopify and sends tracking back.
- The buyer's name and shipping address go straight from bol.com into the order in your Shopify store. Fjordsync does not keep them, does not create a Shopify customer, and does not use the buyer's e-mail address or phone number.
- We keep order numbers, items and status for 90 days after an order is done, your settings while the app is installed, and your bol.com access keys in encrypted form.
- The app and its database run on Google Cloud in Finland. Alert e-mails go through Resend in the USA.
- When you uninstall the app, we delete your data and the bol.com keys straight away.
1. Who is responsible
For your store's data and settings, the data controller is Fjord Studio, which makes Fjordsync. Fjord Studio is a trading name of Langsæter Labs (org. no. 937939493, Norway), a sole proprietorship (enkeltpersonforetak). Contact: fjordstudio.app@gmail.com.
For your buyers' order data, you (the merchant) are the controller, and Fjordsync processes it on your behalf only to create your orders and shipping confirmations. bol.com is an independent controller for its own marketplace.
2. What this policy covers
This policy covers the Fjordsync app for Shopify, the bol.com login steps it shows (/bol/start and /bol/callback) and e-mails with us about the app. It does not cover Shopify or bol.com, which have their own privacy policies.
3. What we store and why
| Data | Where it comes from | Why | Legal basis |
|---|---|---|---|
| Store details: shop domain, Shopify shop ID, shop name, store currency, whether it is a development store, your plan | Shopify | To run the app for your store and apply your plan | Contract |
| E-mail address for alerts (starts as your store's contact e-mail; you can change it or turn e-mails off) | Shopify, or you | To send you alerts | Contract |
| bol.com access keys: either the access and refresh token from bol.com's login, or the API key (client ID and secret) you paste in Fjordsync, plus short-lived access tokens. All encrypted with AES-256-GCM, with the date the connection ends | bol.com, when you log in there, or you, when you paste your API key | To work with your bol.com seller account, and to remind you before the yearly login | Contract |
| Settings: fulfilment method, delivery promise, countries, price rule, stock buffer, default carrier, chosen collection, and the manufacturer (economic operator ID) per brand | You | To create your offers | Contract |
| Offers: product and variant ID, inventory item ID, EAN, product title, SKU, the price, stock and delivery settings last sent to bol.com, the bol.com offer ID, and bol.com's reasons when an offer is offline | Your store and bol.com | To keep offers in step and send only changes | Contract |
| Orders: bol.com order and order item numbers, order date, delivery country, EAN and quantities, shipped and cancelled quantities, cancellation requests, bol.com's expiry date, the Shopify order ID and name, and the order's status | bol.com and Shopify | To create each order once, follow cancellations and shipments, and warn you before bol.com's expiry date | Contract |
| Shipments: Shopify fulfillment ID, carrier code, the tracking number until bol.com has confirmed it, and bol.com's answer | Shopify (fulfillments) and bol.com | To confirm shipments to bol.com | Contract |
| Alerts: type, time and a short text with order numbers, EANs or product names | Built by the app | To show banners and send alert e-mails | Contract |
| Usage events with your shop domain and time: install, uninstall, plan change, bol.com connected, first offer online, orders imported, shipments confirmed, sync errors, alerts, privacy requests | Recorded by the app | To run the app, find faults and see which features are used | Legitimate interest |
| Shopify access token | Shopify | To read products and create orders on schedule | Contract |
| Request logs: IP address, browser, address requested, time and response code; our own log lines (shop domain, IDs, counts, error codes, never buyer data) | Google Cloud, automatically | Security and fixing errors | Legitimate interest |
| E-mails you send us | You | To answer you | Contract or legitimate interest |
- Contract: needed to provide the app you installed (GDPR article 6(1)(b)).
- Legitimate interest: keeping the service secure and working (article 6(1)(f)). You can object; see section 10.
4. Buyer data: what happens to it
- Every 10 minutes Fjordsync asks bol.com for new orders. For a new order it reads the order details, which include the buyer's name and shipping address (and a pick-up point name if the buyer chose one).
- Fjordsync puts the name and address into the order it creates in your Shopify store, with no order confirmation e-mail and no shipping e-mail to the buyer. It holds them only in the server's working memory while the order is created, and never writes them to its database, alerts or logs.
- It does not use the buyer's e-mail address, phone number or billing details, and it does not create a customer in Shopify. Orders are marked so the buyer is not opted in to marketing.
- If bol.com has hidden a buyer's details (shown as ANONYMISED), Fjordsync writes them as bol.com gives them.
- When you fulfil an order, Shopify notifies the app. Fjordsync reads only the order, line items, carrier and tracking number from that notice and ignores the address in it.
bol.com's rules ask sellers to delete a buyer's data when the buyer asks bol.com to conceal it. That data is in your Shopify order, so you handle it there.
5. What we send to bol.com
For offers: EAN, price, stock, SKU (as your reference), product title (used by bol.com only for products it doesn't know), the manufacturer ID and your delivery settings. For orders: shipping confirmations (order item numbers, carrier and tracking number) and the cancellations you accept. No buyer data is sent to bol.com.
6. Service providers and where data is stored
| Provider | What they do for us | Location and safeguards |
|---|---|---|
| Google Cloud (Google Cloud EMEA Limited) | Runs the app (Cloud Run), stores data (Firestore), keeps secrets and logs | App and database in europe-north1 (Finland). Encrypted at rest. Google's Cloud Data Processing Addendum. EU Standard Contractual Clauses where data is accessed from outside the EEA. Logs may be stored outside Finland. |
| Resend (Resend, Inc.) | Delivers alert e-mails: the alert address and the alert text | USA, under the EU Standard Contractual Clauses in Resend's data processing agreement. |
| Google (Gmail) | Our support mailbox | Google's terms for Gmail |
7. How long we keep data
- Buyer names and addresses: not kept.
- Orders and shipments: deleted 90 days after the order is shipped or cancelled. A tracking number is deleted as soon as bol.com has confirmed it.
- Settings, offers, alerts and the bol.com keys: while the app is installed. Disconnecting bol.com in Settings deletes the keys at once.
- When you uninstall the app: we delete everything above at once, including the bol.com keys and the Shopify access token. Your offers stay on bol.com as they were; you manage them in bol.com's seller dashboard.
- About 48 hours after uninstall: Shopify asks us to delete the shop's data. We delete the small uninstall record and replace your shop domain in the usage events with a one-way code (pseudonymisation).
- Usage events: 24 months, then deleted automatically.
- Request and error logs: up to 30 days.
- Customer data requests from Shopify: the summary is kept in the app for 30 days.
8. Shopify's privacy requests
- Customer data request (
customers/data_request): we send you, by e-mail and in the app's Settings, what Fjordsync holds for the orders in the request: order numbers, items, status, delivery country and shipments. It holds no names or addresses. - Customer deletion (
customers/redact): we delete our records for those orders and their shipments. - Shop deletion (
shop/redact): we delete everything still stored about the shop, as in section 7.
9. Cookies
- Inside the Shopify admin, Fjordsync uses no cookies; Shopify handles sign-in with session tokens.
- When you connect bol.com, the step before bol.com's login sets one strictly necessary cookie,
fs_bol, for up to 10 minutes. It ties the login to your browser so nobody else can finish it, and is deleted when you come back. - No analytics, advertising or tracking cookies or scripts.
10. Your rights
Under the GDPR you can ask for a copy of your personal data, correction, deletion, restriction, portability, and object to processing based on legitimate interest. Most you can do yourself: change the alert e-mail, disconnect bol.com or uninstall the app. Otherwise e-mail fjordstudio.app@gmail.com from the store's contact or alert address; we answer within one month.
Buyers who want to use their rights should contact the shop they bought from or bol.com. If a request reaches us, we pass it to the shop.
You can complain to the Norwegian Data Protection Authority, Datatilsynet, or to the authority where you live or work in the EU/EEA.
11. Security
- HTTPS for all traffic. The database is reachable only by the app's server.
- bol.com keys are encrypted per shop (AES-256-GCM) with a key kept in Google Secret Manager. Shopify's expiring tokens are used.
- Test and production run in separate Google Cloud projects. Automated tests use made-up data and check that no buyer data reaches the database or logs.
- If an incident affects your data, we tell you within 72 hours of confirming it.
12. Changes
If we change how Fjordsync handles data, we update this page and the date at the top, and tell you in the app or by e-mail before a significant change takes effect.
13. Contact
Fjord Studio, Norway
E-mail: fjordstudio.app@gmail.com