The short version
- We collect what we need to run your account and the personalization service: your name, your email address, a password we cannot read, the designs and templates you create, and technical records that keep the service secure.
- We do not sell personal data, and this site has no advertising or analytics cookies or scripts.
- Photos that shoppers upload into a personalizer are deleted automatically after 2 days, unless the store attaches them to an order.
- Providers such as Cloudflare and DigitalOcean handle data only to deliver the service for us. They are listed below.
- You can ask to see, correct, export or delete your data at any time. Contact us and we will answer within 30 days.
Who we are
This policy explains how Brown Linx (“we”, “us”) handles personal data when you visit this website, create an account, or use Linx: the workspace, the design library, the embeddable personalizer, the API and the connection for AI assistants (together, the “Service”).
We are the controller of the personal data described here: the organization that decides why and how it is used. The one exception is when a store uses Linx to personalize its own products: for the shoppers of that store we act on the store’s behalf. When a store uses Linx explains.
To reach us about your data, use the contact form with the topic “Privacy or data request”.
What we collect
| What | Details | Where it comes from |
|---|---|---|
| Account details | Your name, email address and role. Your password is stored only as a one-way hash, so we cannot read it. | You, when you register (on this site, or on a fulfillment center’s website when you ask to open stores there), or an administrator who creates the account for you. |
| Your content | Templates, designs and artwork, mockups, previews, the text and images you add, and your workspace settings. | You, including any AI assistant you connect to your account. |
| Shoppers’ input | Text typed and photos uploaded into a personalizer on a store that uses Linx. Photos can show people; we use them only to draw the preview and the print file. | The shopper. |
| Messages | What you write in the contact form: your name, email address, company, topic and message. To stop spam we also keep your browser’s user-agent text and a keyed hash of your IP address (not the address itself). | You. |
| Connections | Access tokens you create (only a hash is stored; the token itself is shown once) and the AI assistants you have connected, with their permissions and dates. | You. |
| Account activity | An audit log of what happens in the Service: sign-ins, changes to templates and settings, and who made them, with the IP address and browser used. | Created by the Service as you use it. |
| Technical data | IP address, browser and device type, pages requested, dates and times, and error details, in our server logs and in those of our network provider. | Your browser. |
| Cookies and browser storage | A few cookies that keep you signed in and protect forms. See the Cookie Policy. | Your browser. |
The Service does not take payments at the moment. If paid plans are switched on, a payment provider will handle the payments, and we will add it to this policy before any payment is taken. We do not ask for sensitive categories of data such as health, religion or political views.
How we use it, and why
Under data-protection law we need a lawful basis for every use of personal data. These are ours:
| Purpose | Data | Lawful basis |
|---|---|---|
| Create and run your account, sign you in and provide the Service you asked for | Account details, your content, connections | Contract |
| Draw previews and prepare print files from what you or shoppers enter | Your content, shoppers’ input | Contract (for shoppers: the store’s instructions, see When a store uses Linx) |
| Keep the Service secure: stop abuse, limit requests, investigate incidents and keep the audit log | Account activity, technical data | Legitimate interests: keeping the Service safe and accountable |
| Answer your messages and requests | Messages | Legitimate interests, or steps you asked for before a contract |
| Find and fix errors, and plan capacity | Technical data | Legitimate interests |
| Meet legal duties and answer lawful requests from authorities | Whatever the law requires | Legal obligation |
We do not use personal data for advertising. We do not sell it or share it for cross-context behavioral advertising. We make no decisions about people by automated means that have legal or similarly significant effects.
Who we share it with
| Who | Why | What they receive |
|---|---|---|
| Cloudflare (network and security) | Delivers the site, protects it from attacks and abuse, and connects visitors securely to our servers. | Requests to the site: IP address, browser, pages requested. When you connect a domain of your own: that domain name. |
| Public DNS resolvers (Cloudflare and Google) | When you connect a domain of your own, our server looks up its DNS records to tell you what is missing. The lookups come from our server, not from your browser. | The domain name you connect and the names of our records under it. Not your account details. |
| The DNS provider of a domain you connect | Only if you choose to let it add the records for you: you sign in with your DNS provider directly, and it adds them. Before that, our server asks it whether it offers this. | The domain name and a code that shows the domain is yours. Never your password, which we do not see. |
| DigitalOcean (file storage, San Francisco, United States) | Stores uploaded and generated files such as artwork, previews and print files. | Your files and their names. |
| The fulfillment center whose website you sign up on | When you sign up on a fulfillment center’s website to open stores, the center decides whether to let you in, and works with you after that. | Your name, your email address and whether the center has let you in. Never your password. |
| Print providers a store chooses | When a store routes an order to a print provider, the provider needs the print files and order details to make and ship it. The store chooses the provider. | What the store sends: print files, order and delivery details. |
| AI assistants you connect (for example Claude or ChatGPT) | Only when you connect one. It can read and change what you allow, and its provider receives what you and the assistant exchange. You can disconnect it at any time. | What your assistant reads or writes in your account. |
| Google Fonts, Bunny Fonts and jsDelivr | Your browser fetches typefaces from Google Fonts (Archivo) and Bunny Fonts (Inter), and an open-source graphics library from jsDelivr, when it loads pages of the Service. As with any website, they see your IP address and browser details. | IP address and browser details, directly from your browser. |
Our team. Only authorized people can open personal data, and only to run, secure and support the Service. A member of our team can open your account to help you with a problem. Every such session is recorded in the audit log together with its reason.
Others. We may share data with professional advisers, with authorities when the law requires it, and with a successor if the business is sold or merged (this policy would keep applying). We do not sell personal data.
Where data is processed
Our application and database run on servers that we operate. Files are stored with DigitalOcean in the United States, and Cloudflare delivers traffic through its worldwide network. Your data can therefore be processed outside the country where you live, including outside the European Economic Area and the United Kingdom. Where the law requires safeguards for such a transfer, we rely on the standard contractual clauses, or another recognized mechanism, that the provider offers.
How long we keep it
| Data | How long |
|---|---|
| Account details and your content | While your account exists. We delete them when the account is deleted, except what the rows below describe. |
| Rendered previews | Until they expire and are deleted automatically: 30 days unless an administrator has set another period. |
| Shoppers’ photos | 2 days, then deleted automatically, together with every cropped version. The exception is a photo that a store ties to one of its orders: it is kept for that order and does not expire on its own. Ask the store or us to delete it when the order no longer needs it. |
| Messages that visitors send to a website that runs on Linx | 365 days, then deleted automatically, or sooner when the website’s owner deletes them. |
| Messages to us | As long as we need to answer you and keep a record of the conversation. You can ask us to delete yours at any time. |
| Access tokens and AI assistant connections | Until you revoke them or they expire. An assistant’s sign-in uses short-lived tokens that are renewed while you keep the connection. |
| Account activity (audit log) | 36 months. Your IP address and browser details are kept in full for 12 months; after that the address is shortened and the browser text is removed. |
| Server and security logs | For as long as needed for security and troubleshooting, and no longer. |
| Backups | Copies made only so that we can restore the Service. Data you delete can remain in a backup until that backup is replaced or deleted. |
Your rights and choices
Depending on where you live, you may have the right to:
- see the personal data we hold about you and get a copy;
- have data corrected when it is wrong or incomplete;
- have your data deleted;
- restrict how we use it, or object to uses based on our legitimate interests;
- receive the data you gave us in a portable format;
- withdraw consent where we rely on it;
- complain to the data-protection authority where you live or work.
If you live in California, you may also ask what personal information we collect and use, and ask us to correct or delete it. We do not sell or share personal information for cross-context behavioral advertising, and we will not treat you differently for using these rights.
How to use them. You can change your name, email address and password yourself in your account settings. For anything else, including access, export and deletion, contact us. We may need to check that the request comes from you, and we answer within 30 days. There is no self-service button yet for deleting an account or downloading your data, so we do it for you on request.
If you met Linx on a store’s website, ask the store first: it decides what happens to your data, and we will help it respond.
When a store uses Linx
Many people meet Linx on a store’s website without knowing it: a shopper types a name or uploads a photo into a personalizer that the store has embedded. For that data the store is the controller and we are its processor. We draw the preview and prepare the print file on the store’s instructions, keep the shopper’s photo for 2 days (or for as long as the store keeps it tied to an order), and do not use it for our own purposes.
Stores are responsible for telling their shoppers about this in their own privacy notice and for having a lawful basis for it. Businesses that need a data-processing agreement can ask for one: contact us.
Storefronts. A fulfillment center’s website can let its clients sign up to open stores. When you do, you make an account on Linx with your name, your email address and a password that we store only as a one-way hash. We are the controller of that account, as of any other. The center whose website you signed up on can see your name, your email address and the state of your request, answers it, and can take you out again, after which you can no longer sign in there. Your admin is served on that website’s own address, not on this site’s, and it uses the cookies that the Cookie Policy describes. The center is the controller of its own website and of what it does with the data it sees there.
Websites that run on Linx. A fulfillment center can run a website on Linx. When a visitor writes to that website through its contact form, we store for the website’s owner the name, email address, optional phone number and message that the visitor typed, the page they wrote from, and a one-way code made from their network address, which only tells repeated messages apart (the address itself is not kept). The owner is the controller of these messages and we are its processor: the owner reads them in an inbox, can archive or delete them, and they are deleted automatically after 365 days. The form sets no cookie.
How we protect data
- The site is served over HTTPS, so what you send and receive is encrypted in transit.
- Passwords and access tokens are stored only as one-way hashes.
- Sign-in attempts and the contact form are rate-limited.
- Accounts have roles, and people see only what their role needs. Private designs and templates are visible only to their owner.
- Uploaded photos are kept private and are reached only through temporary signed links. Their location and camera metadata is removed when they are processed.
- What happens in the Service is recorded in an audit log that is protected against changes.
No system is perfectly secure. If we learn of a breach that affects your data, we will tell you and the authorities as the law requires.
Children
The Service is for businesses and adults. It is not directed to children under 16, and we do not knowingly collect their data. If you believe a child has given us personal data, contact us and we will delete it.
Changes to this policy
We may update this policy when the Service or the law changes. The date at the top of the page shows the latest version. For material changes we will give notice on this site or in your workspace before they take effect.
Contact
Questions about this policy or about your data: use the contact form and choose “Privacy or data request”.