Privacy Policy

Frontspace AB · Last updated: 16 October 2026

Svensk version: frontspace.se/integritetspolicy

1. Who this covers, and in which role

Frontspace AB (company reg. no 559387-8647), Ulriksbergspromenaden 12A, SE-352 36 Växjö, Sweden, runs the Frontspace e-commerce platform.

We handle personal data in two different roles, and which one applies decides whom you should contact:

As controller — for the people who use Frontspace itself: merchants, their staff, and visitors to frontspace.se. We decide why and how that data is processed, and this policy covers it.

As processor — for the people who visit or buy from a merchant's store built on Frontspace. That data belongs to the merchant, who decides why it is collected. We process it only on the merchant's instructions and under our data processing agreement. If you are a shopper, contact the merchant first; their own privacy policy applies. Sections 3 and 6 describe what we do with that data on their behalf.

2. What we process as controller

Account: name, email, password hash, role, language. Why: to give you an account and control access. Legal basis: performance of contract.
Store configuration: store name, domains, theme settings, content you create. Why: to run your store. Legal basis: performance of contract.
Billing: plan, invoices, receipts, payment status, billing address, company and VAT number. Why: to charge you and meet Swedish bookkeeping law. Legal basis: contract; legal obligation.
Payment card: encrypted card reference from Surfboard, card brand, last four digits, expiry — never the full card number or security code. Why: to charge plans and purchases you approved. Legal basis: performance of contract.
Domains: holder's name or company, company number, address, phone, email. Why: to register a domain in your name. Legal basis: performance of contract.
Support: messages you send us and our replies. Why: to help you. Legal basis: legitimate interest.
Security and audit: sign-ins, IP address, API and assistant activity. Why: to detect abuse and answer “what changed, and who did it”. Legal basis: legitimate interest; legal obligation.
Website analytics: page views on frontspace.se, referrer, coarse device type. Why: to understand how our own site is used. Legal basis: legitimate interest.

We do not sell personal data, and we do not use your data or your store's content to train AI models.

3. What we process on behalf of merchants

When a merchant runs a store on Frontspace, we store and process — as processor — the data that store collects. Depending on what the merchant has enabled, this can include:

Order data: items, prices, order status, delivery and invoice address.
Customer data: name, email, phone, address, order history, and an account if one was created.
Form submissions: whatever a merchant's contact or enquiry form asks for.
Shipping data: recipient details sent to a carrier to book a delivery or return.
Store analytics: page views on the merchant's storefront.

We use it only to provide the service to that merchant, and never for our own purposes.

4. AI assistants and connectors

Frontspace offers two AI features. Both are opt-in, and neither is on by default.

The in-admin assistant helps a merchant build and edit their store from inside Frontspace.

The Frontspace connector lets a merchant connect an external assistant — such as Claude or ChatGPT — to their store. To connect, the merchant must sign in and approve a consent screen that names each permission.

What an assistant can read

Access is bounded by the permissions the merchant ticked. Across all of them, an assistant can be given:

Store content: pages and their blocks, popups, header and footer, navigation menus, redirects, posts, content types and their fields, revision history, and the store's colours and fonts.
Media: file names, dimensions and public URLs of images and files in the merchant's media library.
Forms: the questions a form asks — never the answers.
Products: names, descriptions, images, categories, prices and stock levels, and their revision history.
Integration status: which apps are installed and connected, which shipping carriers are set up and whether they book for real or in test mode, and whether accounting is connected.

What an assistant is never given

These are enforced in our software, not only stated here:

Orders. No tool can read an order.
Customers. There is no customer tool.
Form submissions. What someone sends a merchant through a form stays private.
Integration credentials. API keys, tokens and carrier agreements held by connected apps are removed from every response before it leaves our servers.
Payment and billing routes, which are refused outright to a connected assistant.

What this means for data leaving Frontspace

When a merchant uses a connected assistant, the content that assistant reads is sent to the assistant's provider (for example Anthropic or OpenAI) and is then covered by their privacy policy and terms. That is the point of connecting one, and the merchant chooses it. We log which tools an assistant called and when, so the merchant can see what happened.

A merchant can disconnect at any time from Settings → Connected assistants in the admin, which revokes access immediately.

5. Cookies and analytics

We use cookies that are necessary for the service: keeping you signed in, keeping a cart, and maintaining security. They cannot be switched off without the service breaking.

For analytics we run Umami on our own servers. It sets no cookies at all, builds no cross-site profile and does not follow you elsewhere. frontspace.se loads no advertising or profiling trackers.

What is actually stored: a visit record holding browser, operating system, device type, screen size, language, country, region and city, plus which pages were viewed and when. No IP address is stored, no cookie is set, and no identifier that could be traced back to you is kept.

Your IP address is used only at the moment of collection — to derive the approximate location above and to compute a one-way hash that tells one visit from another. It is not written to disk and cannot be recovered from what is stored.

The platform supports a merchant switching on advertising tools such as the Meta pixel in their own store. That is the merchant's choice, it is off unless they configure it, and it is covered by that merchant's own privacy policy and cookie consent — not by this one.

6. Who else processes data, and where

Our infrastructure runs on Scaleway in Paris, France (fr-par) — inside the EU. Our sub-processors:

Scaleway: hosting, databases, object storage, transactional email. Location: France (EU).
Bunny.net (EU company): delivery of images and static files. Location: global edge network; Swedish edge for Swedish visitors.
Surfboard Payments AB: card payments for Frontspace plans and purchases, and payments in merchants' stores where the merchant uses Surfboard. Location: Sweden (EU).
Domain registrar and the top-level domain's registry: registering domains a merchant buys. Location: depends on the top-level domain.
Anthropic / OpenAI: only when a merchant has connected that assistant (section 4). Location: USA.
Carriers (PostNord, DHL, nShift): booking deliveries and returns when a merchant uses them. Location: EU.
Fortnox: our bookkeeping, and accounting sync if a merchant connects it. Location: Sweden.
Google: product feeds and Merchant Center, only if a merchant connects it. Location: USA.

If a merchant uses another payment provider in their store, that provider's terms and the merchant's privacy policy apply.

An up-to-date list is available on request, and we will tell merchants before adding a sub-processor that handles their data.

Transfers outside the EU/EEA happen only where a merchant has connected a service outside it — an AI assistant or Google — or registers a domain whose registry is outside it. Such transfers rely on the European Commission's Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework.

7. How long we keep it

Account and store data: for as long as the account exists. Closing a store is a soft delete with a 90-day reactivation window, after which stored files are permanently deleted by an automatic daily job. An account paused for non-payment is not deleted.
Payment cards: until you remove the card, when our reference to it is deleted.
Shipping labels: 12 months, then deleted automatically. A label holds a recipient's name and address, so it is kept only as long as a delivery dispute could reasonably run.
Invoices, receipts and accounting records: seven years, as Swedish bookkeeping law requires.
Security and audit logs: no security log keeps an IP address or a user for longer than 12 months. Server logs are kept for 7 days, API logs for 90 days, expired sign-in sessions for 30 days, and sign-ins and known devices for 12 months. The record of what a connected assistant did stays after 12 months, but without who used it. The change history of content — what changed and who changed it — is kept for as long as the account exists, including for deleted content, so that it can be restored. For products, the 60 latest versions are kept.
Analytics: kept indefinitely as aggregate statistics. Because no IP address, cookie or identifier is stored (see section 5), there is nothing in it that singles out a person to delete or time-limit.
Data we hold for a merchant: for as long as their agreement runs; on termination we delete or return it as our processing agreement sets out.

8. How we protect it

Data is encrypted in transit (TLS) and at rest. The reference to a saved payment card is additionally encrypted on its own and never shown, not even to you. Access is limited to what a person's role allows, and every store is isolated from every other — that isolation is enforced in software and tested automatically on every change. Passwords are stored hashed, never readable. We log administrative and assistant activity.

No system is perfectly secure. If a breach affects your personal data, we will notify the Swedish Authority for Privacy Protection (IMY) and, where the law requires, tell you.

9. Your rights

Under the GDPR you may ask us to:

give you the personal data we hold about you;
correct it if it is wrong;
delete it, unless the law requires us to keep it;
restrict processing, or object to processing based on legitimate interest;
give it to you in a portable format;
withdraw consent, where processing is based on consent.

Write to alvin@frontspace.se and we will answer within one month.

If you are a shopper on a merchant's store, send your request to that merchant — the data is theirs. If you send it to us, we will forward it.

You may also complain to the Swedish Authority for Privacy Protection (IMY), Box 8114, SE-104 20 Stockholm, imy.se.

10. Children

Frontspace is a business tool and is not directed at children. We do not knowingly collect personal data from anyone under 13.

11. Changes

We will post any change on this page and update the date at the top. If a change materially affects how we handle your data, we will tell account holders directly before it takes effect.

12. Contact

Frontspace AB
Ulriksbergspromenaden 12A, SE-352 36 Växjö, Sweden
Company reg. no: 559387-8647 · VAT no: SE559387864701
Email: alvin@frontspace.se · Phone: +46 72 516 62 84

Our terms and conditions govern the agreement with us.