Pereiti prie turinio

Teisinė informacija

Privacy policy

The controller for the processing of your data is Adam Max, Sudbrackstr. 46, 33611 Bielefeld, GERMANY. Email: support@brickvpn.net.

We have not appointed a data protection officer because we are not legally required to. For all privacy questions, write to support@brickvpn.net.

We only process what we need to run BrickVPN. We do not store which websites and services you access through the VPN. We store no DNS queries, no content of your traffic and no list of your VPN connections with start and end. Your real IP address is not in our VPN databases. We set no tracking or advertising cookies and embed no analytics or advertising services.

We store your account (account ID encrypted, email optional), orders and payments, per device its name, key, tunnel address and server. We do not store when a device was connected or how much data it transfers. The website and web server store IP addresses for a short time. Details and periods are below. That is why we say “no browsing logs” and not simply “no logs”.

We process data on the basis of the General Data Protection Regulation (GDPR):

Because a VPN service can be a telecommunications service, we also observe telecommunications secrecy and the German Telecommunications Digital Services Data Protection Act (TDDDG), in particular §§ 3, 9 and 12 TDDDG. Storing information on your device is governed by § 25 TDDDG.

Our website with the customer account and our VPN servers run on rented servers from these providers. They process data as processors only on our instructions (Art. 28 GDPR):

Server logs. On every request our web server stores the IP address, date and time, requested address, status code, amount of data transferred, referrer and browser identifier. We use this data to deliver the website, find errors and fend off attacks (Art. 6(1)(f) GDPR). The logs are deleted after 7 days. The application error log is deleted after 14 days.

Page view counting. We count views of public pages on our own server, without cookies and without third-party scripts. Per day we only store the page, the language and the domain of the page you came from, neither IP address nor browser nor an identifier. Visits therefore cannot be linked to a person. We do not count known bots. We delete the counts after 400 days unless a shorter period is set.

“Your connection” display. The connection menu shows the IP address you are using to access the website right now. It is only used while delivering the page and is not written to our database.

Ping measurement. Response times to our locations are only measured when you tap “Measure ping”. Your browser then sends short WebRTC requests (STUN, UDP port 3478) to the VPN servers of the locations shown on the map. These servers receive your IP address because they could not answer otherwise. They do not store it. The permission is kept in this tab’s session storage, not in a cookie. You can revoke it at any time: with the “Revoke” button that appears in the same place after you agree, or by closing the tab. When you revoke it, we delete the session storage entry and stop running measurements; no further requests are sent. If you open the website in a new tab, measurement is off again until you agree once more. Without the click, no such request is sent (Art. 6(1)(a) GDPR, § 25(1) TDDDG).

Status page. On the status page you can voluntarily report whether BrickVPN works on your network. We use your IP address once to determine your provider network (ASN) and do not store it. We store country, ASN, network, protocol, result and time (Art. 6(1)(f) GDPR, informing all users about blocks).

Spam protection. Some forms use ALTCHA, a computing puzzle your browser solves. ALTCHA runs on our own server, without cookies and without third-party services (Art. 6(1)(f) GDPR, protection against automated requests).

We only use technically necessary cookies and storage. That is why we do not ask for consent (§ 25(2) no. 2 TDDDG):

When you pay, we forward you to the PayPal or Stripe page. Their cookie rules apply there.

There is no newsletter you can sign up for. We may, however, send notes about the service to customers with a confirmed email address. These are not emails that belong to the contract.

Each of these emails contains a link to a page where you can turn these notes off. We still send emails about orders, tickets, your password and other contract matters.

For each mailing we record which address it went to, in which language and whether it was delivered. Sending goes through Lettermint (no. 16).

An account is created with a random 16-digit account ID. We store it encrypted; a hash of it is used for login. An email address is optional. If you add one, we store it and the time of confirmation. We store a password only as a hash. If you turn on one-time codes or a passkey, we store the secret or public key needed for that. We also store the chosen language of the customer account and whether you want reminders by email. The legal basis is Art. 6(1)(b) GDPR.

Login log. To protect your account we store the time and the IP address of the request on login, logout, failed login, change of password, two-factor login or passkeys and on account deletion. For a failed login we also store a masked account ID or the email address entered. To limit login attempts we keep the IP address in a cache for a few minutes. The legal basis is Art. 6(1)(f) GDPR (protection against account takeover). We delete the entries after 30 days.

You can delete your account in the account settings at any time. We then delete the account data unless we must keep it because of legal obligations (no. 9).

Order data. For each order we store package, period, currency, amount, tax, the chosen payment method, the billing details, that access should start during the withdrawal period, and the time of payment. We need the country to treat VAT correctly. We need street, postal code and city for the invoice; for small amounts the checkout may mark them as optional. The details are also stored with your account so you do not have to enter them again next time. The legal bases are Art. 6(1)(b) and (c) GDPR.

Payment providers. To pay, we forward you to PayPal or Stripe. They process your payment data as independent controllers under their own privacy policies: PayPal (Europe) S.à r.l. et Cie, S.C.A., 22–24 Boulevard Royal, L-2449 Luxembourg, and Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Dublin 2, Ireland. We receive a payment reference, the payment status and the data the provider sends along, and store it with the payment. We do not receive or store card data.

Cash by post. If you pay in cash (§ 6a of the terms), we store a payment code with the order and the fact that you agreed to refunds by bank transfer. Two people open every letter together. We note the date of receipt, amount, currency, denominations, the content of the enclosed slip and who opened the letter. We do not need your name or address. If the envelope shows a sender, we do not copy it into our data. We destroy slip and envelope no later than 14 days after matching, and unmatched letters after 6 months. We delete the denominations and the slip content at the same time. After that only payment code, order, date of receipt, amount and currency remain as part of the accounting record. We delete payment codes for which no money arrived 120 days after the order. If we have to refund something, we ask for a bank account and use the bank details only for the refund. The legal bases are Art. 6(1)(b) and (c) GDPR.

Retention. We keep invoices and accounting records for 8 years and commercial and business letters for 6 years (§ 147 AO, § 257 HGB), each from the end of the calendar year. We delete raw data a payment provider sends us after 6 months; the payment reference stays as part of the accounting record.

Device data. For each device you create in your account we store the name you give it, the protocol, the public key, the tunnel address and the server. If our system generates the private key, we store it so you can download the configuration again. If your app generates the key itself, we only store the public key.

Connection status. We do not store when a device was connected or last communicated with the server, not even as a single point in time. The server only reports how many devices are connected in total right now, as one number without reference to any device. We use it to manage capacity.

Data volume. We do not record or store how much data a device or account transfers. We only count the total traffic of each server per month, as one number without reference to any device or account. We use it to plan the costs at the data centre and, if needed, to lower the speed of all devices on a server (§ 10 of the terms).

What our VPN servers do not store. The server software reports no client IP address and no destination to our system. So that your traffic finds its way back to you, the server knows your current IP address in memory during a connection. We store no logs of websites visited, DNS queries or content.

Locations outside the EU. If you choose a location outside the EU or EEA, the server there processes your IP address and traffic while you are connected. This is necessary for the connection you requested (Art. 49(1)(b) GDPR). Gcore has also agreed standard contractual clauses for third countries.

The legal bases are Art. 6(1)(b) GDPR (providing the VPN), Art. 6(1)(f) GDPR (security, abuse and fault detection) and, where the TDDDG applies, §§ 9 and 12 TDDDG. We delete device data when you delete the device or your account.

Requests from authorities. We only hand over data to authorities if we are legally obliged to. Data we do not store under this policy we cannot hand over either.

When you redeem a prepaid card we store the code, the time of redemption and the account that was credited. You need neither an email address nor a name. To protect against guessing codes, we store redemption attempts for 30 days with a hash of the IP address. The seller only sees whether and when the card was redeemed, not your account, devices or usage. The legal bases are Art. 6(1)(b) and (f) GDPR.

If you apply as a reseller, we store the details of your application and, if we work together, the contract, billing and voucher data (which vouchers were created, activated, blocked and redeemed). We file the application as a ticket with a ticket number (section 13). Name, contact and address details are stored encrypted in the database. The 90-day deletion period from section 13 does not apply to this ticket. The legal bases are Art. 6(1)(b) and (c) GDPR.

If you write to us through the contact form, by ticket in your account or by email to our support mailbox, we open a ticket with a ticket number. We process your details and the content of your messages to answer you (Art. 6(1)(b) GDPR where it concerns your contract, otherwise (f)). Subject, name, contact details and messages are stored encrypted in the database. If you give an email address, we confirm receipt with the ticket number and send you our replies by email. We delete closed tickets 90 days after the last message unless they must be kept as business letters. Please never send us your account ID or keys by email.

Contact form. Through the contact form we store the topic, name or alias, email address, the message, the language and the time. To protect against spam, your browser solves a small computing task (ALTCHA). It runs on our own server, without cookies and without third parties. To stop mass submissions, the server keeps your IP address in its cache for at most one hour.

Email to support. Our server fetches emails sent to our support mailbox at Febas (section 4) over an encrypted connection. From each email we take the sender address and name, the subject, the text without the quoted history, the message ID and the time into a ticket. We do not take over attachments. If you reply to one of our emails and the ticket number is in the subject, we add your reply to that ticket, but only if it comes from the address stored on the ticket. Otherwise we open a new ticket. We do not take over automatic replies such as out-of-office notices.

Telegram. If you use our Telegram bot or write to us via Telegram, Telegram processes your data under its own terms, including outside the EU. We see your Telegram ID, display name and messages. The bot stores your Telegram ID, language, a linked account and whether you want reminders. Telegram is optional; for confidential matters we recommend email (Art. 6(1)(b) or (f) GDPR).

If you cancel or withdraw via our forms, we store your name, contract reference, type of declaration, reason, requested end of contract, the optional email address, the language and the time. Name, contract reference, reason and email address are encrypted in the database. If you are logged in, the case is also linked to your account. We also file each declaration as a ticket with a ticket number (section 13). The retention period of this section applies to that ticket, not the 90 days from section 13. We do not store an IP address. We need the details to process the declaration and prove its receipt (Art. 6(1)(b), (c) and (f) GDPR). They stay stored as long as statutory retention or limitation periods require.

If you request a refund under your right of withdrawal or your rights for defects, we process your account’s email address or your order number, an optional reason and the time of the request (Art. 6(1)(b) GDPR). We check for abusive repeated use using the refunds on your account, your email address and the payment reference (Art. 6(1)(f) GDPR). We do not use IP addresses, device fingerprints or connection data for this.

If you added an email address, we send you emails that belong to the contract, for example confirmations, invoices and important security and change notices (Art. 6(1)(b) and (c) GDPR).

Before your period ends we tell you when your access ends. These notices contain no advertising. You can turn them off in your account under “Profile” at any time.

Sending through Lettermint. Every email our system sends automatically goes through Lettermint B.V., Willemsvaart 16 B, 8019 AB Zwolle, the Netherlands. Lettermint acts as a processor on our instructions (Art. 28 GDPR). This includes in particular confirmation of your email address, password resets, order and payment confirmations, the notice that a device is set up (without the configuration), notices of payments due for a renewal, confirmations of cancellation and withdrawal (no. 14), ticket notifications (no. 13) and reminders before access ends. Automatic notices to us, for example about orders, tickets or outages, also go through Lettermint. For this Lettermint receives the email address, the content of the email and technical delivery data: sender, subject, headers, message ID, time, delivery status and the receiving mail server’s response. We do not send attachments such as invoices or VPN configurations. Lettermint processes this data in the EU and only to deliver the emails, to detect delivery problems and abuse and to secure the service. Lettermint does not use the data for advertising or to train AI models. Lettermint automatically deletes content, delivery data and delivery events after 28 days.

If an email cannot be delivered permanently or is reported as spam, Lettermint puts the address on a suppression list so that no further emails go to it. We do not set this block ourselves and we do not remove the entry when you delete your account or confirm a new address. The legal basis is Art. 6(1)(f) GDPR. The legitimate interest is reliable delivery and protecting our sender domain from abuse.

We do not measure whether you open our emails or click links in them. Our emails contain no tracking pixels, and links go directly to the destination.

Personal replies to support requests are sent from our mailbox at Febas (no. 4, no. 13).

Service notes that we send by hand are covered in no. 7.

Data between your browser and our website is only transferred encrypted (TLS). We transfer system emails encrypted to Lettermint, and Lettermint delivers them encrypted where the receiving mail server supports it. We store account IDs, cancellation and withdrawal details, contact enquiries and notes on cash payments encrypted and passwords only as a hash. We keep our servers up to date and limit access to the data to what is necessary (Art. 32 GDPR).

We do not sell data and do not pass it on for advertising. Recipients are only our processors (no. 4), payment providers if you pay through them (no. 9), Telegram if you use it (no. 13), our tax advisor as far as needed for accounting and taxes, and authorities and courts if we are legally obliged.

Website, customer account, database and email mailboxes run in Germany, and our system emails are sent through Lettermint in the EU. Data is transferred outside the EU and EEA in these cases:

Statutory retention periods start at the end of the calendar year in which the record was created.

For an account you only need the account ID we generate. For an order we need the billing details the checkout marks as required and payment via a payment provider. Without them we cannot conclude the contract. All other details, such as an email address, are optional.

We make no decisions based solely on automated processing that produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR), and we do not create profiles. The speed limit under § 10 of the terms applies equally to all devices on a server and does not depend on your use.

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to withdraw consent with effect for the future (Art. 7(3)).

Right to object (Art. 21 GDPR): where we process data on the basis of Art. 6(1)(f) GDPR, you can object at any time on grounds relating to your particular situation. We then stop processing the data unless we can demonstrate compelling legitimate grounds that override your interests, or the processing serves the establishment, exercise or defence of legal claims.

Write to support@brickvpn.net for this. Accounts without an email address can only be identified by the account ID. In that case, log in to your account and send the request as a ticket. Do not send us the account ID by email. If we cannot identify you, Art. 11(2) GDPR applies.

You can complain to a data protection supervisory authority, in particular in the EU state where you live, work or where the infringement took place (Art. 77 GDPR). For website, account, payments and support, the authority of the German federal state where we have our seat is responsible for us (address in the legal notice). Where we process data to provide the VPN as a telecommunications service, the Federal Commissioner for Data Protection and Freedom of Information (BfDI), Graurheindorfer Straße 153, 53117 Bonn, is responsible (§ 29 TDDDG).

We update this privacy policy when our service or the law changes. The version published here applies.

As of 21 November 2026, version 1.0