Who we are
Briks is a trading name of SEMICOLON WEB TECHNOLOGIES ("Briks", "we", "us"). We provide the Briks website and app builder: the marketing site at briks.dev, the studio at app.briks.dev, and hosting for the sites built with it, including addresses on briks.live and domains our customers connect.
For your account and the studio, we are the controller of your personal data. For the visitors to sites our customers build, the customer is the controller and we process that data on their behalf (see "Data from your sites' visitors").
Questions or requests about privacy go to hello@briks.dev.
What we collect
When you use the studio we collect:
- Account details: your name, email address and password. Passwords are stored only in a scrambled, one-way form, never as you typed them. If you sign in with Google instead, Google tells us your name, email address and profile picture, and that Google has confirmed the address; we never see your Google password.
- Sign-in records: the cookies and records that keep you signed in and secure, including the address and browser a session came from, and for each sign-in, the browser, system and country it came from.
- Dashboard page visits: the pages of the studio you open while signed in, logged for support and security, and kept for 180 days.
- Email records: for each email the studio and your sites send, who it went to, what kind it was, its subject and whether it went (never its words), kept for 90 days for delivery and abuse checks. An address that bounced, was reported as spam or was blocked is kept on a list so it is not emailed again until it is removed.
- What you put into the studio: the descriptions you write, your answers to the studio's questions, messages you send in a project, addresses and screenshots of sites you like, brand settings, and the pictures, videos and files you upload.
- What Briks makes for you: your sites, their code, their versions, their records and their settings.
- Workspace details: its name, its members and their roles, and the invitations you send.
- Usage: the credits each request held and was charged, your plan, and when things ran.
- Telegram, if you connect it: your Telegram user number, username and first name, the mobile number you add to your profile to link by phone, the chats the Briks bot is in, the site each works on, the alerts each takes, and every message to and from the bot.
- Discord, if you link it or add Briks to a server: your Discord user number, username and display name, the servers and channels the Briks bot is in and their names, who added it, the site each channel works on and the alerts it takes. For each message to and from the bot we keep only when it was sent, what kind it was (such as the command used) and whether it went, never its words, for 90 days. The changes and questions you send join the project's conversation, as in the studio.
- Chat activity: a short note, in our own words, of what was done or sent through Telegram or Discord, such as a change asked for, a channel's site chosen or an alert delivered, shown on your workspace's Activity page and kept for 13 months.
On briks.dev, we count visits without cookies, with a privacy-friendly analytics service that does not identify you or follow you across other sites. Any analytics cookies are set only if you accept them, and your choice is kept in your browser.
Data from your sites' visitors
When you publish a site with Briks, we process data about its visitors so the site works and you can see how it is doing. You decide what your site collects and you are the controller of that data; we process it only on your instructions, to run your site and show you the results.
- Visits: counted without cookies, and nothing is kept on the visitor's device for counting. A visitor is told apart only by a code made from their network address and browser that changes every day, and the address itself is not kept. We also keep the page, how long it was in view and how far down it was read, the buttons, links and files pressed, where the visit came from, campaign tags, screen width, browser and system, page speed, and an approximate location (country, city and the coordinates of that area). Browsers that ask not to be tracked are not counted, and where Briks wrote the site's privacy page, a visitor can stop their own visits being counted from it.
- Form entries: what visitors send through your site's forms, kept in your studio, and emailed to you once the site is in production.
- Chat: if you switch on your site's chat, the questions visitors ask and the answers, with the page the chat started on and the visitor's country (never their address), kept for you to read for 90 days after the last message; and the questions passed on to you by email.
- Records: anything your site keeps in its own database, such as bookings or listings.
- A/B tests: when you test two versions, cookies keep each visitor in the same version and count one visit and at most one conversion.
You are responsible for telling your visitors how their data is used, for example in your site's own privacy notice. When Briks writes a privacy page for your site, it describes the counting and gives visitors a link to opt out. Our data processing terms for your sites are part of our Terms of Service.
How we use data, and why
- To provide the studio and host your sites, as our contract with you requires: building, changing and publishing what you ask for, keeping versions, sending the emails the service needs (confirmations, invitations, notices about your sites).
- To keep the service secure and fair, which is our legitimate interest: preventing abuse, fraud and attacks, enforcing limits, and fixing faults.
- To improve the studio, which is our legitimate interest: understanding how it is used and where builds go wrong.
- To count visits to briks.dev without cookies and without identifying you, which is our legitimate interest in knowing how the site is used; any analytics cookies only with your consent, which you can withdraw at any time from the cookie settings link at the foot of every page.
- To meet our legal obligations, such as keeping billing records.
We do not sell personal data, and we do not send marketing emails without your consent.
AI processing
Briks uses AI models to plan, write, design, build and check sites, and to draw pictures. To do that, the descriptions you write, your messages and answers, the sites you show it, and your site's content are sent to the AI model providers we use, who process them on our behalf.
If you switch on your site's chat, visitors' questions and your published pages are sent to an AI model to write the answers.
Pictures the studio draws for your site may be kept in our picture library and used on other sites built with Briks. Pictures and videos you upload stay yours and are used only on your own sites.
AI output can be wrong. Check what Briks makes before you publish it.
International transfers
Some of our providers process data outside the European Economic Area, including in the United States. Where they do, we rely on an adequacy decision or on safeguards such as the European Commission's Standard Contractual Clauses.
How long we keep data
- Your account and workspace data: for as long as your account exists.
- When you delete your account: your account and what is yours alone are deleted. A workspace you share with others stays with them.
- Nightly copies of a site's database, if you switch them on: each kept for 30 days.
- Chat apps: the activity of Telegram and Discord for 13 months; Discord's message details for 90 days, and a server's details for 90 days after Briks is removed from it.
- Records the law requires us to keep, such as billing records: for as long as the law requires.
Counts of your sites' visits: each visit's details for 25 months, then only daily totals, for as long as the site exists, unless you delete them sooner. Other data about your sites' visitors, such as form entries and records, is kept while the site and your account exist, unless you delete it sooner.
Your rights
Under data protection law you can ask us to:
- give you a copy of your personal data
- correct it
- delete it
- limit how we use it, or stop using it where we rely on our legitimate interests
- give it to you, or to another service, in a common format
- withdraw a consent you gave, at any time
Write to hello@briks.dev. We answer within one month. You can also complain to the Data Protection Commission in Ireland, or to the data protection authority where you live.
If you are a visitor to a site built with Briks, ask the site's owner first: they decide what their site collects. We will help them answer you.
Security
Connections to Briks and to the sites it hosts are encrypted. Passwords are stored only in a one-way form. Access to customer data is limited to what running the service needs, and each workspace's data is kept apart from every other's.
No system is perfectly secure. If we learn of a breach that puts your data at risk, we will tell you and the authorities as the law requires.
Age
Briks is for people aged 18 or older. We do not knowingly collect personal data from anyone younger.
Changes to this policy
We will post any change here with a new date, and email you about significant changes before they take effect. This policy was last changed on 19 October 2026.