Privacy notice

Who is responsible?

The controller for personal data collected through this website is:

Our Vienna office is at Wiegelestraße 34, Objekt 1
1230 Vienna, Austria.

Email: office@berrinex.com
Telephone: +43 677 61991832

Contact the company above for privacy questions or requests. See the Imprint for company registration details.

Scope of this notice

This notice covers the Berrinex marketing website, its project enquiry and meeting-request forms, and its editorial login. Docelix and GoSocio are separate products with their own privacy information on their respective websites.

The website does not currently include advertising trackers, marketing analytics, newsletter subscriptions or automated decisions about visitors that produce legal or similarly significant effects.

Enquiries and meeting requests

When you contact us, we process the information you provide: your name, email address, optional company, selected topic and message. A meeting request also includes your preferred date, time, time zone and requested duration. We use these details to answer, assess your request and arrange the next step. A meeting request does not reserve a slot or confirm an appointment.

For requests about a potential contract, processing is based on taking steps at your request before entering a contract (Article 6(1)(b) GDPR). For other business correspondence, the basis is our legitimate interest in responding and managing communications (Article 6(1)(f)). Where processing genuinely depends on consent, the basis is Article 6(1)(a), and that consent can be withdrawn.

The form acknowledgement records that the privacy information has been presented. It is not consent to advertising, a waiver of your rights or permission to use your information for unrelated purposes.

You are not obliged by law to submit a form. Your name, email and message are needed to process that request; the company field is optional. If you prefer, use the email or telephone details above. Please do not include passwords, sensitive financial records or special-category personal data in a general enquiry.

Technical data and editorial login

Serving the website involves processing connection information such as an IP address and request details. The server also uses request information for error handling and basic abuse prevention. These operations support our legitimate interest in providing and protecting the website (Article 6(1)(f) GDPR).

Editors sign in through Supabase Auth. Authentication and role information are used to check whether an account may access the editorial workspace, draft previews and post or image management. Visitors do not need an account to read public pages or send an enquiry.

Cookies, browser storage and local resources

Public marketing pages do not set advertising or analytics cookies. The editorial area uses Supabase authentication cookies and related browser session storage to maintain and refresh an authorized login. These serve the requested login function rather than marketing.

You can remove stored cookies or site data through your browser; doing so may sign you out. Fonts and bundled website images are served by this website. Published blog images may be delivered by the configured Supabase storage service, which receives the connection information needed to serve them. Loading a public page does not require a Google Fonts request.

Recipients, service providers and international transfers

Enquiries and meeting requests are stored in the configured Supabase database. Supabase also provides editorial authentication and blog image storage. Browser users, including editorial users, do not have direct access to the enquiry table; access is restricted to trusted server operations and authorized company administration.

Website hosting, database hosting and email or telephone services used to answer a request may process the data needed to provide those services. We do not claim that every provider, subprocessor or data flow is within the EEA without checking the actual deployment.

This website is hosted on Netlify. The database, editorial sign-in and blog media use Supabase in Frankfurt, Germany (eu-central-1). Project enquiries, demo requests and meeting requests are stored in this Supabase project. Provider and subprocessor operations may involve additional locations; no EU-only processing guarantee is made. Contact office@berrinex.com for the applicable processor and transfer details.

Where a transfer outside the EEA is necessary, its legal mechanism and relevant safeguards must be assessed for that provider and processing activity. Contact us for the details applicable to your request.

How long information is kept

The retention criteria depend on the purpose. Enquiry and meeting-request information is needed while dealing with the request and necessary follow-up. If it becomes part of a contractual relationship, relevant records may need to be retained for that relationship, legal obligations or the establishment, exercise or defence of legal claims.

Data that is no longer needed for a valid purpose should be deleted or anonymized. Deletion and rights requests are handled by the company; this website does not promise automatic deletion after a fixed number of days. Technical log and backup retention depend on the selected hosting and database setup.

Ask us for the retention details applicable to your correspondence. A production retention schedule and the procedures for deletion, logs and backups must be confirmed for the chosen services.

Your data protection rights

Depending on the processing and the applicable conditions, you can request access, correction, erasure, restriction or portability of your data. You may object to processing based on legitimate interests on grounds relating to your situation. You may withdraw consent where consent is the basis; withdrawal does not invalidate earlier lawful processing.

Send your request to office@berrinex.com. We may ask for proportionate information to verify identity. The usual response period is one month; where a lawful extension is necessary, you must be informed within that first month.

You can complain to the Austrian Data Protection Authority or another competent supervisory authority. The Austrian authority can be contacted at dsb@dsb.gv.at, Barichgasse 40–42, 1030 Vienna.

External links, scheduling and media

Links to product websites, maps or other third-party pages take you to services governed by their own privacy information. The office map is a link, not an automatically loaded map embed.

When the administrator publishes a Calendly event, its calendar loads only after you choose to load it or open its booking page. Calendly then handles the details you enter there under its own privacy terms.

The introduction video is currently a placeholder. If a video hosted on another service is added later, its delivery can disclose connection information to that host; the notice and loading behavior must be reviewed for that change.

How information is protected

The application uses authenticated editor access, database row-level policies, server-side credential handling, validation of submitted data and browser security headers. These controls reduce specific risks; they are not a guarantee that a system is immune to every incident.

See security information for the implemented controls and how to report a concern. Do not send confidential material through a public enquiry form.

Updates and further information

This notice should be updated when the purposes, providers or website functionality change. The date above identifies this version. The European Data Protection Board’s guidance explains the underlying data protection principles.