Skip to content
Legal

Security and Compliance

The measures BidIndex applies today to protect your data, where the data lives, which assurances we do not have yet, and how to report a security issue.

Last updated: November 04, 2026

Scope and status

This page covers the bidindex.eu website, its API and the server side used by the BidIndex Jobs mobile app. The service is operated by Core Engineering Kft..

What follows are measures in operation today, not promises or goals. We do NOT yet have an independent security audit or certification (e.g. ISO/IEC 27001, SOC 2) or a third-party penetration test report, and we do not present ourselves as having one.

Where the data lives

The application, database, queue and primary backups run on netcup GmbH — server location: Vienna, Austria, i.e. in the EU.

The off-site copy of the database backup and error reports are held in Microsoft Azure's Sweden Central region (EU).

When you use AI features, the relevant text goes to the providers named in the Privacy Policy (Anthropic, Microsoft); some of them are outside the EU and the basis for the transfer is explained there. If you do not use those features, no text belonging to your account is sent.

Protection in transit and at rest

All connections are encrypted with TLS. The server tells browsers to connect to the site over HTTPS only (HSTS, one year, including subdomains).

Passwords are hashed with bcrypt, never stored in plaintext and cannot be read by anyone.

The off-site backup copy is kept encrypted in Azure Blob storage (the provider's default encryption, with TLS 1.2 or higher required to connect).

Sessions and access control

The web session lives in an httpOnly cookie that JavaScript cannot read and that is sent over HTTPS only in production; SameSite protection guards against cross-site requests.

When you change your password or sign out of all devices, earlier sessions are invalidated on the server.

Record endpoints are tied to a subscription and a user identity; labels, notes, decisions and watchlists can be read only by their owner. Administrative endpoints appear as a non-existent address (404) to everyone who is not an administrator.

Rate limits apply to the sign-in, sign-up and password-reset endpoints and to the API as a whole.

Two-factor authentication for user accounts is not offered yet.

Server and network

The server is reachable only on ports 22 (SSH), 80 and 443 (firewall). Administrative access uses keys, not passwords, and repeated failed attempts are blocked automatically (fail2ban).

The database and cache run on an internal network that is not reachable from the internet; the cache is password-protected. Services run in separate containers with memory limits.

Operating system security updates are applied automatically.

The web application sends a content security policy (CSP), blocks MIME sniffing, uses a restrictive referrer policy and protects against framing.

Features that download from an address supplied from outside (news extraction, tender document download) pass through a filter that blocks access to internal network addresses; redirects are checked by the same filter. Webhook destinations are limited to Slack, Microsoft Teams and Discord addresses.

Backup and recovery

The database is backed up every day; backups are kept for 7 days on the server and monthly for 12 months. Each backup is automatically checked for readability.

A copy of each day's backup is uploaded off-site to Azure; for 13 days nobody can delete or modify this copy (even if the server were compromised), it is cleaned up after 14 days, and a deleted copy can be recovered for 14 more days.

The same backup is restored into a separate database every day as a test: we do not assume the backup works, we demonstrate it daily.

Monitoring and incident handling

Services are checked on the server every 15 minutes and externally by an uptime monitor; data ingestion and backups go through daily checks and an email alert is sent if something is wrong.

Error reports go to Azure Application Insights; email addresses and session tokens are masked before they are sent.

Server access logs (including IP addresses) are kept for at most 7 days and then deleted automatically.

In case of a breach affecting personal data we notify the supervisory authority within 72 hours and inform you directly where the risk is high (GDPR Art. 33–34).

AI and your data

Under the commercial API terms of Anthropic and Microsoft, content sent to them is not used to train models (details: Privacy Policy).

The CV file and its raw text are not kept; only the extracted profile is stored, and you can delete it from your account page. What you type into the support assistant is neither stored nor logged.

AI output is assistive and can be wrong; it does not replace legal assessment.

Personal data and your rights

You can download the data linked to your account as a machine-readable file with “Download my data” on your account page, and delete your account yourself. See the Privacy Policy for details and your other rights.

If you are a company that processes personal data under your own responsibility with BidIndex and you need a written data processing agreement under GDPR Art. 28, you can use our Data Processing Addendum (DPA) template.

Reporting a vulnerability

If you believe you have found a security vulnerability, write to info@coreeng.eu with the subject “Security” and give enough detail for us to reproduce the issue.

For issues reported in good faith, found without accessing user data or disrupting the service, we commit to fixing them and not to taking legal action against the reporter. We do not run a bug bounty. We answer email on business days.

Please do not access other people's data, load-test the service, or disclose details publicly until the issue is fixed.

Preparation of this statement

This page is based on our own internal assessment of our systems. It is updated when a measure is added or removed.

Prepared and last reviewed on: 2026-11-04