What's new (22 November 2026). We now describe cookies more precisely (section 12): the website and the Marketplace use none, the app only those needed for signing in. We no longer keep the interface language in a cookie. This does not extend how we process your data.
At BuildPoint we value your privacy and are committed to protecting your personal data in accordance with the General Data Protection Regulation (GDPR), the Slovenian Personal Data Protection Act (ZVOP-2) and other applicable Slovenian legislation.
This policy describes how the platform actually works. It complements the Terms of Use; where the two texts differ on the processing of personal data, this policy prevails.
This is a translation of the Slovenian original. In the event of any discrepancy, the Slovenian version prevails — switch the language to Slovenian to read it.
1. Data controller
The controller of personal data collected through the BuildPoint platform (buildpoint.si) is:
BuildPoint, spletne rešitve, d.o.o. Svetla ulica 1, 2354 Bresternica, Slovenia Company registration number: 7594399000 | VAT ID: SI72021721 E-mail: info@buildpoint.si
Contact for data protection questions and for exercising your rights: dpo@buildpoint.si
This policy applies to the BuildPoint platform and all of its modules, including the website buildpoint.si and the surveyor marketplace at buildpoint.si/trznica/ (formerly marketplace.buildpoint.si).
2. When we are the controller and when we are a processor
The distinction matters, because it determines whom you should contact.
| Data | Our role | What this means for you |
|---|---|---|
| Account and subscription data: registration, e-mail address, issued invoices, payments, access logs, security records | Controller | We decide about this data; contact us directly to exercise your rights |
| Content you enter into the platform yourself: projects, bills of quantities, attachments, comments, data about your clients and collaborators | Processor | Your organisation is the controller. We process this data only on its instructions. If you are an individual whose data was entered into BuildPoint by an organisation, please contact that organisation — we will tell you which one it is |
Processing in our role as a processor is governed by a data processing agreement (Art. 28 GDPR), available on request, which also covers the list of sub-processors, security measures and the handling of data when the subscription ends.
3. What data we collect
- Identification and contact data: first and last name, e-mail address, language, role within the organisation, time of last login.
- Organisation data: company name, tax and registration number, address, logo, invoicing details.
- Sign-up source: if you registered through a link from one of our campaigns, we store that campaign's label with the organisation (
utm_*parameters, e.g. the campaign name and where it was posted). The label tells us which of our posts led to the registration; it contains no data about your device or visit. - Data from sign-in via external providers (Google, Microsoft): the name and e-mail address the chosen provider passes to us. We never see the password of your user account with that provider.
- Usage and technical data: IP address, browser and device information, access time, login logs (for security and troubleshooting).
- Payment data: subscription status and transaction history. We do not store payment card data — it is processed by our payment provider Mollie.
- Content you enter into the platform: projects, bills of quantities, uploaded files, comments.
- Audit trail: who performed which action, when, on what, and its outcome; separately also the IP address and device information (see section 3.1).
- Record of used trial periods: a hashed value of the company's tax number, not the tax number itself (see section 3.2).
- Data of people you share a bill of quantities with: when you share a bill of quantities with someone who has no user account, we process their e-mail address and the one-time access code we send them, and we log accesses to the link.
- Data published in the Marketplace module: when you publish a profile, selected data becomes publicly available (see section 3.3).
- Data in the surveyor marketplace (Marketplace module): the content of a surveyor profile (profile name, tagline, introduction, years of experience, trades, regions, availability, response time), uploaded proof of qualifications, the content of job requests and proposals, and reviews of completed work with their comment and the reply to it.
- E-mail address on joining the waitlist, if you sign up for it.
- E-mail address from the “Notify me” form on the website, if you sign up to be notified when a module in preparation is released: the e-mail address, the notification language, the module, and the text and time of your consent. We do not store the IP address.
- Message from the “Write to us” form on the Contact page: name, e-mail address, language, the text of the message and the time it was sent.
- Electronic signature data: when you electronically sign a proposal in the Marketplace module, we record evidence of the signature — your name and e-mail address, your role in the organisation, the name and tax number of the organisation, the time of signing, the IP address and device information, the time the one-time code was sent and confirmed, and the text of the declaration of intent you confirmed. The record is sealed so that it can be proven that it has not changed since signing.
3.1 The audit trail: who can see it and what it does not contain
The audit trail records changes to bills of quantities and accesses to them, so that every action is traceable. Within the application it can be viewed by the owner and the administrator of the organisation (Settings → Log); a project manager cannot.
Three points that are not self-evident:
- The IP address and device information are hidden in the display. They are recorded but not shown. Only the organisation owner can reveal them, and only for an individual record — and every such disclosure is itself logged as a new entry in the trail.
- The trail does not contain old and new values. It records that the price of an item was changed; it does not record from which amount to which.
- It does not contain logins and logouts — these are in the security logs and have their own retention period.
Actions performed on your organisation by our operator (for example a change of storage quota or the cancellation of an invoice) are visible in the trail, with the person shown as "BuildPoint (platform)" without a personal e-mail address.
3.2 The trial record stores a hash, not the tax number
The free trial belongs to the company, not to an individual user account. So that the same company cannot take the trial indefinitely by creating new registrations, we store a hashed value (HMAC-SHA256) of the normalised tax number, computed with a server key that is not stored in the database.
The record holds three items: the hash, the date of first registration and the date the trial was used. Nothing else — no name, no address, no owner, no link to the organisation. It is not possible to determine from this record which companies are our customers; without the server key an exported table is useless. Even our system administrator sees only the hash and the two dates, never the tax number.
This record is retained even after an organisation is closed and anonymised — otherwise it would not serve the purpose for which it exists.
3.3 Public Marketplace pages
If you publish a profile in the Marketplace module, selected data (name, description, regions, trades, average rating) becomes publicly accessible and may be indexed by search engines. Public publication is switched off by default — a profile is initially visible only to signed-in marketplace users. You initiate publication yourself by explicitly switching visibility to "public", and you can withdraw it at any time just as easily (by switching visibility back or withdrawing the profile); on withdrawal the page returns a "permanently removed" status (HTTP 410) and we flag it to search engines for removal. We have no control over copies held in search engine caches — removal there can take several weeks.
Individual reviews are not public. Public pages show only the average rating and the number of reviews. The text of a review (the author's comment and the surveyor's reply) is visible only to signed-in users of organisations that have the marketplace module enabled. If you enter free text in a review comment, that text may indirectly identify its author — we do not review comment content in advance, so do not include names of persons or details from which the job can be identified.
The review text goes, the numbers stay. On every deletion path — closure of the organisation account (section 8), expiry of the retention period (section 7) or a request by the author — we delete the review text (the comment and the reply to it) and hide the author. The numerical part of the review (ratings 1–5 per dimension, the recommendation, the trade and the date) remains in the surveyor's average. The author may at any time request deletion of the text of an individual review through the platform administrator — at dpo@buildpoint.si or through support; the administrator carries out the deletion, and the review continues to count towards the average.
3.4 Matching job requests and withdrawing inactive profiles (profiling)
In the Marketplace module we carry out two forms of limited profiling:
- Matching job requests with profiles. For each published job request we calculate a match score (0–100) with every active surveyor profile from five data points: overlap of trades, region, average rating, years of experience and availability. Surveyors with a high match are notified of the new job request, and matches are shown to them as suggestions. The score and its individual components are stored so that we can explain why a surveyor was or was not notified.
- Automatic withdrawal of inactive profiles. If no member of a surveyor's organisation signs in for an extended period (6 months by default), the profile is withdrawn from the directory. The organisation's administrators receive a warning 14 days in advance; on the first new sign-in the profile automatically returns to the directory.
We do not make automated decisions producing legal or similarly significant effects (Art. 22 GDPR): matching only helps with notifications, and the choice of surveyor is always made by the client. The processing is based on legitimate interest (section 4). You may object to it and request human review of an individual outcome at dpo@buildpoint.si.
4. Purposes and legal bases for processing
| Purpose | Legal basis |
|---|---|
| Creating and managing a user account, providing the platform's services | Performance of a contract (Art. 6(1)(b) GDPR) |
| Subscription billing, issuing invoices | Contract and legal obligation (tax and accounting legislation) |
| Verifying a company's VAT number (VIES) | Contract / legitimate interest |
| System security, abuse prevention, error logging | Legitimate interest (Art. 6(1)(f) GDPR) |
| Traceability of changes to bills of quantities and of access to them (audit trail) | Legitimate interest (Art. 6(1)(f) GDPR) — provability of actions on business documentation |
| Preventing repeated abuse of the free trial | Legitimate interest (Art. 6(1)(f) GDPR) |
| Sharing a bill of quantities with a person without an account (sending the access code) | Performance of the contract with the customer and the legitimate interest of both parties in sharing securely |
| Operating the surveyor marketplace within the application, connecting clients and surveyors | Performance of a contract (Art. 6(1)(b) GDPR) |
| Public publication of a profile and job requests in the Marketplace module | Consent (Art. 6(1)(a) GDPR) — publication is switched off by default; you switch it on yourself and withdraw it just as easily (sections 3.3 and 10) |
| Reviews of completed work: collection, display to marketplace users and calculation of the average | Legitimate interest (Art. 6(1)(f) GDPR) — clients need a reliable indicator of a surveyor's quality, and the surveyor needs the reputation earned through the work |
| Matching job requests with profiles and notifying surveyors of suitable job requests (3.4) | Legitimate interest (Art. 6(1)(f) GDPR) — so that a surveyor learns of work relevant to them and the client receives proposals from suitable contractors |
| Automatic withdrawal of inactive profiles from the directory (3.4) | Legitimate interest (Art. 6(1)(f) GDPR) — a directory of responsive surveyors does not offer clients contractors who will not reply |
| Waitlist notifications and invitations | Consent (Art. 6(1)(a) GDPR) |
| Notification of the release of a module you signed up for with the “Notify me” form on the website | Consent (Art. 6(1)(a) GDPR) — withdraw it with the one-click unsubscribe link in every notification or at dpo@buildpoint.si |
| Answering support enquiries | Legitimate interest (Art. 6(1)(f) GDPR) |
| Replying to a message sent with the “Write to us” form on the website | Legitimate interest (Art. 6(1)(f) GDPR) or steps taken at your request prior to entering into a contract (Art. 6(1)(b) GDPR) |
| Processing feedback you send through the in-app form (including a screenshot, if you attach one) | Legitimate interest (Art. 6(1)(f) GDPR) — fixing errors and improving the platform; submission is voluntary |
| Proving an electronic signature on a proposal and its content | Performance of a contract (Art. 6(1)(b) GDPR) and the legitimate interest of both contracting parties in being able to prove the commitment (Art. 6(1)(f) GDPR) |
| Analytics cookies (if and when we introduce them) | Consent via a cookie banner |
For processing based on legitimate interest we have carried out a balancing test. We will send you a summary on request at dpo@buildpoint.si; the right to object is described in section 10.
Providing data at registration is a contractual requirement: without the organisation's name, tax number and an e-mail address we cannot conclude the contract or open an account.
5. Recipients of personal data (processors)
To operate the platform we use carefully selected contractual processors, who process data on our instructions:
- Hetzner Online GmbH (Germany) — server hosting and data storage (data centres in the EU).
- Mollie B.V. (Netherlands) — payment processing.
- Functional Software, Inc. (Sentry) (USA) — logging of technical errors in the application and receiving feedback that you send us yourself. The processing is threefold:
- Automatic error reports. When an error occurs in the application, the error message, the location in the code and basic technical data (browser type, address of the page on which the error occurred) are transferred. We do not transmit personal data, IP addresses or authentication tokens — they are stripped before sending.
- Session recording on error. When an error occurs in the application, the report is accompanied by a recording of page use before and after the error (page layout, clicks, scrolling). All text on the screen and all input fields are masked in the recording, and images and other media are left out, so the content of your projects cannot be read from it. Sessions in which no error occurs are not sent.
- Feedback form. Through the "Send feedback" button in the application header, data is sent to us only if you fill in and submit the form yourself. What you enter is transferred: the message (required) and, optionally, your name and e-mail address — these fields are not pre-filled and you may leave them empty. If you yourself add a screenshot to the form, it is transferred unmasked, i.e. with everything visible on the screen at that moment, including client names, prices or margin; you can remove it before submitting. The submission may also be accompanied by the session recording described in the previous item (with masked text). We use the data sent to fix errors, improve the platform and reply to your message.
- Hitrost.com d.o.o. (Cesta železarjev 8b, 4270 Jesenice, Slovenia) — sending system e-mails.
- VAT number verification provider (VIES) — verifying the validity of a VAT ID at registration.
- The controller's accounting service — for issued invoices.
Public marketplace pages. Profiles and job requests that a user explicitly publishes are accessible to every visitor on the web and are indexed by search engines. Details are in section 3.3 and in the notice on the processing of personal data in the marketplace, linked in the footer of every public marketplace page.
We do not sell your data and do not pass it to third parties for their own marketing purposes. Beyond the above, we disclose data only to competent authorities, and only on the basis of a lawful request.
An up-to-date list of processors is always published in this policy. We inform business users in advance, through the application or by e-mail, of any replacement or addition of a processor, so that they can object under the data processing agreement.
6. Transfers to third countries
Data is primarily processed and stored within the EU. For the provider established in the USA (Sentry), transfers are based on the EU-U.S. Data Privacy Framework or on standard contractual clauses (SCC) with additional safeguards.
The content you enter into the platform (projects, bills of quantities, attachments) is stored exclusively on servers in the EU and is not transferred to third countries. The only exception is content you send yourself: a screenshot you attach to feedback (section 5) is transferred to the provider Sentry together with it.
7. Retention periods
- User account data: for as long as the account is active, or until a deletion request.
- Organisation data and project content: until the organisation account is closed and the reflection period expires (section 8).
- Invoices and accounting documentation: 10 years from issue (required by tax legislation, ZDDV-1).
- Access logs and security records: up to 12 months.
- Audit trail: up to 12 months; the period is set by the platform operator and cannot be changed by the customer.
- Technical error records: up to 90 days.
- Record of a used trial (hash): permanently — see the reasoning in section 3.2.
- Waitlist e-mail address: until the invitation is issued or consent is withdrawn.
- E-mail address from the “Notify me” form: until you unsubscribe or the module is released, no longer than 24 months from your consent. When the module is released we send you one notification and delete the e-mail address; if you unsubscribe, we delete it immediately. We also delete it if we withdraw the module from preparation, and 30 days after a notification could not be delivered. The 24-month limit also applies if you did not confirm your sign-up or the module has not been released yet.
- Messages from the “Write to us” form: 12 months from sending. We receive the message by e-mail in the info@buildpoint.si mailbox; after sending, the website database keeps only the name, e-mail address, language and time of sending. If the message cannot be delivered, we keep its content for a retry for no more than 30 days. We do not store rejected submissions (invalid input, automated or unwanted submissions). We use the IP address only to limit the number of submissions and keep it in temporary memory for no more than one hour.
- Support correspondence: 2 years after the case is closed.
- Surveyor profile and job request data: for as long as the profile or job request is active, and thereafter until the organisation account is closed.
- Text of a review of completed work (the author's comment and the surveyor's reply): 3 years from the creation of the review; after that we delete it automatically and hide the author. It is removed earlier on closure of the organisation account (section 8) or at the author's request (3.3).
- Numerical part of a review (ratings per dimension, recommendation, trade, date): for as long as the reviewed surveyor's profile exists. Without the text and the author's name it does not identify an individual.
- Electronic signature evidence: 5 years from signing. This period is deliberately longer than the retention of logs: the evidence must outlive the period in which claims arising from the transaction can still be brought (the general limitation period under the Slovenian Code of Obligations).
Deletion at the end of these periods is carried out by automated daily jobs; you do not need to remind us.
⚠️ Electronic signature evidence survives the closure and anonymisation of an organisation. A signature is a commitment given to the other contracting party, which did not create the evidence and cannot replace it; if it disappeared when an organisation account was closed, anyone could erase the proof of what they had committed to. The basis for continued retention is Art. 17(3)(e) GDPR (establishment, exercise or defence of legal claims). After five years we remove the name, e-mail address, IP address and device information from the record; only the seal, hash values and timestamps remain, which do not identify a person, while the record can still be verified. Evidence is deleted once both conditions are met: the period has expired and the transaction is concluded.
8. Closing an organisation account and anonymisation
An organisation account passes through three states:
- Active organisation — the owner closes the organisation account under Settings → Close account.
- Closed — access is revoked and sessions terminated, while the data remains untouched. A reflection period follows (30 days by default), during which the account can be restored.
- Anonymised — personal and identifying data is deleted; restoration is no longer possible.
On closure all members lose access, active sessions and tokens are revoked, and the data remains untouched so that an accidentally closed account can be restored. Restoration is possible through support within the reflection period. The event is recorded in the audit trail.
After the reflection period expires we delete: the organisation's name (replaced by a neutral label), its web identifier, its tax and registration number, its address, its logo, unused invitations and join requests, and the e-mail addresses and one-time codes of people with whom bills of quantities were shared.
We retain: issued invoices and their line items (a legal retention obligation that the right to erasure does not override — Art. 17(3)(b) GDPR), the hash in the trial record, electronic signature evidence (section 7), neutral settings containing no personal content (country, currency, time zone) required for the compliance of issued invoices, and the numerical part of reviews in the Marketplace module (without the text and without the author's name).
The marketplace on closure of the organisation account. On closure the surveyor profile is withdrawn from the directory and from public pages (the public address returns 410), reviews the organisation has received are no longer displayed, and the author is hidden on reviews it has written. After the reflection period expires we delete all free text of reviews — both written and received (comments and replies) — as well as the profile's name (replaced by a neutral label), tagline and introduction, and we remove the proof of qualifications and portfolio photos from storage. The review numbers remain in the average as an anonymous record of the job.
A person's user account and an organisation's account are separate. When an organisation is anonymised, we also anonymise the user accounts of its members who are not members of any other active organisation. A person who leaves an organisation that remains active may submit a request for deletion of their own user account themselves; the request is carried out by the platform administrator by anonymising the user account (deleting the name, e-mail address, phone number, picture and password). Records of the work the person did in the organisation (authorship, audit trail) remain attached to the anonymised user account. The organisation that remains does not lose its data.
Content you hold for your own clients: where we act as a processor, we delete or return the project content once the subscription ends — tell us which before the reflection period expires. Without such notice, deletion applies. You can export your data yourself at any time (section 10).
9. Data storage and security
We store data on secure servers within the European Union. We apply technical and organisational measures, including:
- tenant separation at the database level — each organisation sees only its own data, and this separation does not depend on application code alone;
- least-privilege access — roles and assigned user seats determine who may see and change what;
- an encrypted connection (TLS), one-way hashing of passwords and encryption of sensitive data in the database;
- rate limiting of login attempts and logging of security events;
- regular backups within the EU and regular security reviews of the code.
9.1 In the event of a personal data breach
In the event of a breach likely to result in a risk to your rights and freedoms, we will notify the Slovenian Information Commissioner within 72 hours of becoming aware of it (Art. 33 GDPR). Where the risk is high, we will also notify you without undue delay (Art. 34 GDPR). Where we act as a processor, we will notify the customer as controller without undue delay.
10. Your rights
Under the GDPR you have the right to:
- access your personal data,
- rectification of inaccurate data,
- erasure of data ("right to be forgotten"),
- restriction of processing,
- data portability,
- object to processing based on legitimate interest, including the profiling described in section 3.4,
- withdraw consent (where processing is based on consent), without affecting the lawfulness of processing before withdrawal.
Some rights can be exercised directly in the application:
| Right | Where |
|---|---|
| Access and portability | Settings → Privacy → Export data (immediate download of the organisation's data in a machine-readable file) |
| Erasure of the organisation | Settings → Privacy → Request data deletion |
| Erasure of a user account (the organisation remains) | Settings → Privacy → Delete my account (the request is carried out by the platform administrator, section 8) |
| Erasure of the text of an individual review you wrote | Request at dpo@buildpoint.si or through support; carried out by the platform administrator (3.3) |
| Rectification | Settings → Organisation |
| Withdrawal of consent to publication | Switch the profile's visibility back to "signed-in users only" or withdraw the profile in the Marketplace module |
For everything else, write to dpo@buildpoint.si. We respond within one month at the latest; if a request is complex, we will inform you of an extension within that period.
Exercising your rights is free of charge. For manifestly unfounded or excessive requests we may charge a reasonable fee or refuse the request (Art. 12(5) GDPR); we always give reasons for any refusal. So that we do not disclose data to the wrong person, requests are executed from a signed-in user account, or identity is confirmed via the e-mail address used to create the user account.
Data export works even when an organisation account is suspended or closed. We do not make the right to portability conditional on payment status. The export does not include share link tokens and one-time codes (these are live credentials; they appear in the export marked as redacted) or platform security logs, which are available through a separate access request.
Limitation of the right to erasure for electronic signatures. We cannot delete electronic signature evidence at your request before the period in section 7 expires, because it is necessary for the establishment, exercise or defence of legal claims (Art. 17(3)(e) GDPR) — including claims by the other party. All other rights (access, rectification, restriction of processing, portability, objection) apply to this data without limitation.
11. Right to lodge a complaint
If you believe we are processing your data unlawfully, you may lodge a complaint with the Information Commissioner of the Republic of Slovenia, Dunajska cesta 22, 1000 Ljubljana, e-mail: gp.ip@ip-rs.si, website: www.ip-rs.si. You may lodge a complaint even if you have contacted us first.
12. Cookies
The buildpoint.si website and the Marketplace do not use cookies.
The app (app.buildpoint.si) uses strictly necessary cookies only, without which signing in does not work:
| Cookie | Purpose | Duration |
|---|---|---|
access_token |
sign-in session (httpOnly) | 15 minutes, then renewed automatically |
refresh_token |
keeping you signed in (httpOnly) | 7 days or until you sign out |
csrf_token |
protection against forged requests | 7 days or until you sign out |
sessionid |
only when signing in with Google or Microsoft; emptied after sign-in | until you close the browser |
All are set with SameSite=Lax and transmitted over HTTPS as Secure only; we delete them on sign-out. We keep your language choice and your cookie decision in the browser's local storage (localStorage), not in cookies. Strictly necessary cookies do not require consent.
What “Accept all” turns on. On your first visit to the app we ask for your consent. Only after “Accept all” do we, through the provider Sentry (section 5), save a recording of the session when an error occurs and measure the app's performance on a sample basis. Sentry sets no cookies for this. The recording and measurements are stored in the EU (Germany); the processor is a company based in the USA, so access from the USA cannot be ruled out — the transfer is protected by standard contractual clauses and/or the EU-US Data Privacy Framework (section 6). After “Reject”, or until you choose, we do neither; error reporting without personal data remains. To change your choice, clear the site data in your browser — the banner will appear again.
We do not use analytics, advertising or marketing cookies. The app contains no advertising networks, social media buttons or embedded third-party content that would track you.
13. What we do not do
- We do not sell personal data and do not pass it on for third-party marketing purposes.
- We do not make automated decisions producing legal or similarly significant effects for an individual (Art. 22 GDPR). We carry out profiling only to the limited extent described in section 3.4 (matching job requests with profiles and withdrawing inactive profiles from the directory); the choice of surveyor is always made by the client.
- We do not process special categories of personal data (health, biometrics, political or religious beliefs), and the platform is not designed for entering them. If you enter such data into project content, you do so as a controller and at your own responsibility.
- The platform is not intended for persons under 18. It is a professional tool; we do not knowingly open user accounts for minors.
14. Changes to this policy
We may update this policy from time to time, where the operation of the platform, the set of processors or the applicable legislation changes. We will notify you of material changes by e-mail or through a notice in the application at least 15 days before they take effect; minor corrections (wording, clarifications) take effect on publication. The date of the last update is stated at the top of this document.
15. Change history
| Date | Change |
|---|---|
| 12 Jun 2026 | First published version. |
| 10 Sep 2026 | Added electronic signing of proposals, the evidence record, its 5-year retention and the limitation of the right to erasure under Art. 17(3)(e). |
| 1 Oct 2026 | The controller is BuildPoint d.o.o. Added: the controller/processor distinction, the audit trail, the trial record, public Marketplace pages, sharing a bill of quantities with a person without an account, account closure and anonymisation, personal data breach notification (72 hours), self-service exercise of rights, statements on profiling and the age limit, and the notice period for changes to this policy. For the provider Sentry, automatic error reports, session recording on error and the feedback form (name, e-mail address, message and a screenshot you attach yourself) are described separately. Added: data in the surveyor marketplace, the purpose of operating the marketplace, public marketplace pages among the recipients of data, and the retention of profile, job request and review data. |
| 29 Oct 2026 | Marketplace: public publication of a profile is based on consent (switched off by default, withdrawal just as easy); limited profiling acknowledged (job request matching, withdrawal of inactive profiles) and automated decisions under Art. 22 excluded; only the average rating is public, not individual reviews; on every deletion path the review text is removed and the numbers stay; deletion of review text at the author's request; 3-year retention of review text; handling of reviews and the profile on account closure; separate deletion of a personal account. The e-mail delivery provider is named. Sign-up source: when you register through a link from one of our campaigns, we store the campaign label (utm_*, section 3) with the organisation. |
| 3 Nov 2026 | Website: the “Notify me” form for module release notifications (consent, retention until you unsubscribe or the module is released, one-click unsubscribe) and the “Write to us” form on the Contact page (legitimate interest or pre-contractual steps, 12-month retention, undelivered message 30 days). |
| 10 Nov 2026 | Cloudflare, Inc. (USA) is no longer among the processors: the BuildPoint domain no longer runs through its network. The only transfer to the USA remains with the provider Sentry. |
| 22 Nov 2026 | Section 12 “Cookies” now describes precisely which cookies we use and for how long: the website and the Marketplace use none; the app uses only those needed for signing in. The interface language is now kept only in the browser's local storage (previously also in a cookie); the temporary session when signing in with Google or Microsoft lasts only until you close the browser. Added what “Accept all” turns on. Processing is not extended. The marketplace is at buildpoint.si/trznica/; the controller's VAT ID is stated. We keep the e-mail address from the “Notify me” form for no longer than 24 months from your consent (section 7). |