Privacy policy

Information under Articles 13 and 14 GDPR.

Last updated: 19 Nov 2026 · Version 3.16

1. Controller

The controller for the processing of personal data on this platform within the meaning of Art. 4(7) GDPR is:

Controller
PackCert GmbH, Am Steinfeld 15, 2511 Pfaffstätten, Österreich
Email
office@pack-cert.at
Telephone
Matthias Zelina +43 664 5079950, Linus Schwalm +43 650 2518900, Sebastian König +43 664 5079951, Sven Olin +43 664 2112445

No data protection officer has been appointed. Art. 37 GDPR does not require one: we are not a public authority, and our core activities consist neither of regular and systematic monitoring of individuals on a large scale nor of processing special categories of personal data on a large scale.

2. Contact for data protection matters

For access, rectification, erasure and any other request under Chapter III GDPR, please write to office@pack-cert.at. Requests are answered in German and English.

3. Processing activities in detail

The following list names every processing activity with its data category, purpose and legal basis. The corresponding retention periods are in section 8.

User account
Name, email address, role, language preference, time of the last sign-in and a checksum of the password. Purpose: providing the account. Legal basis: Art. 6(1)(b) GDPR.
Company data
Company name, company type, VAT identification number, address, country, website and contact email. Purpose: attributing items and documents to the responsible economic operator and, for paid plans, invoicing. Legal basis: Art. 6(1)(b) GDPR.
Feature wishes
Companies on a paid plan can wish for features. The wish — title, description and, if given, the hoped-for benefit —, the person and the company who made it, its status and our answer with the times are stored. Only the company itself and the provider’s team see the wish. It is emailed to the team, and the person is informed in the application and by email about status and answer, each through the email provider named in section 6. Purpose: developing the platform and answering the company. Legal basis: Art. 6(1)(b) GDPR.
Public company profile
Every company has an address on the platform and a profile behind it. If it is public, anyone sees the company name, the type of company, city and country, the website, a short description written by the company, an uploaded logo, the time of registration and — only if the company switches it on — the contact email; for suppliers also the packaging items and documents the viewer may see. Address lines and VAT identification number never appear. Suppliers' profiles start out public, customers' profiles do not, and an account as a consumer has no public profile and a random address instead of a name. A company's previous addresses are stored so that they redirect and are not given to anyone else. Purpose: making the company and its evidence findable. Legal basis: Art. 6(1)(b) GDPR; where the contact email is a personal address, Art. 6(1)(f) GDPR — it is shown only at the company's express request.
Sign-in and session
A checksum of the session key, the network part of the IP address, the browser identification and the expiry time. The session key itself is stored only in the cookie, never in the database. The IP address is stored shortened to its network, because the network is enough to notice unusual access. Purpose: keeping the sign-in alive and detecting unauthorised access. Legal basis: Art. 6(1)(b) and (f) GDPR.
Security log
Sign-ins and failed sign-in attempts, creation and modification of accounts and companies, uploading and changing documents and revisions, publications, data exports and administrative operations — each with a timestamp, user identifier, browser identification and the IP address shortened to its network. Purpose: defence against abuse and traceability of who filed which revision. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest lies in the security of the platform and in being able to evidence changes to compliance documentation.
Document retrievals
Time of retrieval, the revision retrieved and — for signed-in people — the user and company identifier. Purpose: building the customer’s document archive and the supplier’s retrieval reporting. Legal basis: Art. 6(1)(b) GDPR.
Records of consent
Time, language version, version number and a checksum of the text actually displayed, plus IP address and browser identification. Purpose: evidencing which wording was agreed to. Legal basis: Art. 6(1)(c) GDPR in conjunction with Art. 7(1) GDPR.
Contract records
On entering a paid plan: plan name, price, currency, billing period, and the versions of the terms, privacy policy and withdrawal notice in force at that moment. Purpose: evidencing the agreed contract. Legal basis: Art. 6(1)(b) and (c) GDPR.
Notifications
Notices about new document revisions and about expiring or expired documents, linked to the user identifier. Purpose: performing the user agreement. Legal basis: Art. 6(1)(b) GDPR.
Content filed by suppliers
Packaging master data and uploaded document files. These generally contain no personal data; where a supplier includes such data in a document, the supplier is responsible for it. Legal basis: Art. 6(1)(b) GDPR.
Releases of private items
Suppliers on a paid plan can mark items as private and release them to individual companies, one by one or through a category they name themselves. For this the releasing and the receiving company, the person who gave the release and the time are stored. Once a company has accepted an invitation from the supplier, it stays connected with them: the supplier can release further items to it without a new invitation, including by entering the address of a person at that company. Purpose: controlling who may see a private item. Legal basis: Art. 6(1)(b) GDPR towards the supplier; towards the receiving company Art. 6(1)(f) GDPR — the legitimate interest lies in making the documents intended for it accessible to it.
Personal offers
When we send a company a personal offer for a plan at a reduced price, we store the email address it goes to, the plan offered, the discount and how long it lasts, an optional personal message, an internal reason for the offer, a checksum of the offer link and the times of sending, expiry, acceptance or withdrawal; on acceptance also the accepting account and its company. The offer is sent through the email provider named in section 6; on acceptance the discount is set up as a coupon with the payment provider named in section 6. Only an account under exactly that address can accept it. Purpose: preparing and concluding a subscription on the offered terms. Legal basis: Art. 6(1)(b) GDPR.
Invitations to private items
When a supplier invites a company by email, the invited email address, the inviting person, the items or categories concerned, a checksum of the invitation link and the times of sending, expiry, acceptance or withdrawal are stored; on acceptance also the accepting account and its company. The invitation is sent through the email provider named in section 6. It can only be accepted with an account under exactly the invited address. Purpose: giving a release to the company the supplier means. Legal basis: Art. 6(1)(b) GDPR towards the supplier, Art. 6(1)(f) GDPR towards the invited person.
Secret links to private items
A supplier can generate a link to a private item that opens it without a user account. A checksum of the link, an optional note by the supplier, the generating person, the expiry time, any withdrawal, and how often and when the link was last opened are stored — not by whom. Whoever opens the link receives a cookie (see section 5). Purpose: access to a private item for persons the supplier gave the link to. Legal basis: Art. 6(1)(b) GDPR towards the supplier, Art. 6(1)(f) GDPR towards the person opening the link.
Declarations of conformity from the declaration generator
The details entered in the form — name and address of the economic operator and, where applicable, the authorised representative, details of the packaging, confirmed obligations and applied standards, and the place, name and function of the signatory, and when signed on screen the signature drawn there as an image — and the PDF generated from them with its checksum, together with the user account that created it, the time of issue and the method of signing. The drawn signature is stored only as an image and placed into the PDF; it is not analysed and not used to identify anyone. The PDF is stored rather than regenerated on each retrieval, so that it remains retrievable exactly as it was issued. Purpose: creating the declaration, its renewed retrieval by the supplier, and proof of which version was issued and charged. If the supplier puts a declaration on its public profile, anyone who sees the profile can download the PDF — including the name and function of the signatory and, where applicable, the signature they drew; without that decision by the supplier no declaration is public, and the supplier can take it off the profile at any time. Legal basis: Art. 6(1)(b) GDPR; where the signatory is not a contracting party themselves, Art. 6(1)(f) GDPR — a declaration of conformity has to carry the name and function of the person signing it on behalf of the economic operator.
Backups
A copy of the database and of the stored files, that is, of the data listed above. Backups are kept encrypted on the operator’s own storage media; only the operator holds the key to open them. Purpose: recovery after data loss or errors. Legal basis: Art. 6(1)(f) GDPR; the legitimate interest lies in the ability to restore data that Art. 32(1)(c) GDPR requires.

4. Retrievals without a user account

Compliance documents can be retrieved without registering. Personal data is processed in that case too, as follows:

A checksum is derived from your IP address, salted with a secret key. Only that checksum is stored, never the IP address itself. It makes it possible to attribute repeated retrievals to the same access point without knowing the address.

The sole purpose is to prevent automated bulk retrieval. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest lies in protecting availability for all users. No profiling takes place, and the checksum is not combined with any other source of data.

5. Cookies and storage in the browser

Only strictly necessary cookies are set: a session cookie for signing in, a cookie for the language preference, a cookie that remembers whether you collapsed the sidebar of the application, and — only when you open a secret link to a private item — a cookie that remembers that link. There is no tracking and no audience measurement. Consent is therefore not required and is not obtained.

The cookie for secret links contains the opened links themselves, twenty at most, and nothing else. It is sent only to this platform, cannot be read by scripts on the page, and expires when the longest-valid link in it expires, after 365 days at the latest. Without it the item would no longer be reachable after the first visit, for example when downloading a document. A link that has expired or been withdrawn opens nothing, even with the cookie. You can delete it in your browser at any time.

The sidebar cookie contains only “collapsed” or “expanded”. It is set only when you collapse or expand the sidebar, and expires after one year.

The platform also keeps a few settings in your browser’s storage (local storage): the appearance you chose (light, dark or matching the system), that you acknowledged the notice about cookies, and for “Search everywhere” the shortcut you chose, when you last opened the search, when the hint about it last appeared and whether it should no longer appear. This information stays on your device: it is not transmitted to the platform and not linked to your account. You can delete it in your browser at any time, after which the defaults apply again.

6. Processors

The following service providers process data on our instructions under a contract pursuant to Art. 28 GDPR:

Vercel Inc. (USA)
Running and executing the application, serving the website, scheduled tasks. Processing in: European Union (Frankfurt region, fra1).
Databricks, Inc. (Neon, LLC) (USA)
Running the database holding account, master, usage and log data. Processing in: Germany (Frankfurt am Main).
Cloudflare, Inc. (USA)
Storing the uploaded document files (R2 object storage). Processing in: European Union (storage bound to the EU jurisdiction).
IONOS SE (Germany)
Domain, name servers and email delivery for the pack-cert.com domain. Processing in: European Union.
Resend (Plus Five Five, Inc.) (USA)
Sending transactional email (password resets, invitations, notifications, contract confirmations). Processing in: Sending from the European Union (Ireland); account data, metadata and logs in the United States.
Stripe Payments Europe, Limited (Ireland)
Processing subscription payments: hosted checkout, payment methods, invoices and subscription management. Processing in: European Economic Area and the United States (Stripe, LLC).

The platform’s source code is managed at GitHub Inc. No personal data of users is transmitted there; GitHub is therefore not listed as a processor.

No analytics, tracking or advertising services are embedded. The application loads no external script and no external fonts whatsoever. No newsletter or CRM system is used.

7. Transfers to third countries

Where each service provider processes data is stated in the previous section. Several of them are companies established in the United States or pass data on to an affiliate there. Access from a third country is therefore not excluded even where the storage location is in the European Union. These transfers rest on the following safeguards:

Vercel Inc. (USA)
Safeguard under Art. 44 et seq. GDPR: Standard contractual clauses of the European Commission (Decision 2021/914), Module 2, as part of Vercel's data processing addendum (version of 31.03.2026). Vercel Inc. is additionally certified under the EU-U.S. Data Privacy Framework (as of 04.11.2026).
Databricks, Inc. (Neon, LLC) (USA)
Safeguard under Art. 44 et seq. GDPR: Adequacy decision of the European Commission on the EU-U.S. Data Privacy Framework (Implementing Decision (EU) 2023/1795). Databricks, Inc. is certified, and Neon, LLC is covered by the certification (as of 04.11.2026).
Cloudflare, Inc. (USA)
Safeguard under Art. 44 et seq. GDPR: Adequacy decision of the European Commission on the EU-U.S. Data Privacy Framework (Implementing Decision (EU) 2023/1795). Cloudflare, Inc. is certified (as of 04.11.2026); alternatively the European Commission's standard contractual clauses (Decision 2021/914), Module 2, under Cloudflare's data processing addendum.
Resend (Plus Five Five, Inc.) (USA)
Safeguard under Art. 44 et seq. GDPR: Standard contractual clauses of the European Commission (Decision 2021/914), Module 2, concluded on opening the account on 27.09.2026.
Stripe Payments Europe, Limited (Ireland)
Safeguard under Art. 44 et seq. GDPR: For the onward transfer to Stripe, LLC in the United States: the European Commission's adequacy decision on the EU-U.S. Data Privacy Framework (Implementing Decision (EU) 2023/1795). Stripe, LLC is certified (as of 04.11.2026); alternatively the European Commission's standard contractual clauses (Decision 2021/914) under Stripe's Data Transfers Addendum.

A copy of the safeguards can be requested at office@pack-cert.at.

8. Retention

The following retention periods apply to the individual categories of data:

Account and company data
until the account is deleted — needed continuously to operate the account.
Sessions
until they expire; expired sessions are deleted daily — they carry a network range and device identification and serve no purpose once expired.
Password resets
30 days from the request — makes a burst of requests against one account visible; the link itself is valid for one hour only.
Email address confirmation
30 days from the request — makes a burst of requests against one address visible; the link itself is valid for seven days.
Change of sign-in address
30 days from the request — holds the new address until it is confirmed and makes a burst of requests visible; the link itself is valid for 24 hours.
Enquiries sent through the contact form
12 months from arrival — serves the negotiation of a contract; if the enquiry leads to none, no purpose remains afterwards.
Company profile information and previous profile addresses
short description and logo until the company changes or removes them; previous addresses for as long as the company exists on the platform — a previous address has to redirect and must not fall to another company while links to it may still be in circulation.
Releases of private items and categories to companies
until the supplier withdraws the release or the item, the category or either company is deleted; the connection between supplier and company until the supplier ends it or either company is deleted — the release is the access itself and is needed for as long as that access is to exist.
Invitations to private items
30 days after the invitation is accepted, expires or is withdrawn — once accepted, the outcome is recorded in the release; the invitation itself is valid for 14 days.
Personal offers
not accepted: 90 days after expiry or withdrawal; accepted: the term of the contract plus 3 years — an accepted offer proves the agreed price; one not accepted still allows a query about it to be answered.
Secret links to private items
30 days after the link expires or is withdrawn — still allows a query about a passed-on link to be answered — whether and when it was opened; a link is valid for 365 days at most.
Feature wishes and our answers
while the wish is open; after “Done” or “Not planned” for another 24 months — the same wish often comes back, and the earlier answer should then still be readable.
Checksum derived from the IP address for retrievals without an account
7 days, then the field is cleared — serves abuse control only; the retrieval count is kept without any personal reference.
Retrieval records linked to a company
the term of the contract plus 3 years — they form the customer’s evidence archive and the supplier’s retrieval reporting.
Security log of sign-ins and failed attempts
12 months — defence against abuse; no purpose remains afterwards.
Security log of changes to items and documents
permanently; IP address and browser identification are removed 3 years after the account is deleted — chain of evidence showing who filed which revision — the event stays, the personal reference ends.
In-app notifications
24 months — of no further use to recipients beyond that.
Records of consent
the term of the contract plus 3 years — matches the general limitation period.
Declarations of conformity from the declaration generator
the term of the contract plus 3 years — the declaration is the company’s and stays retrievable and provable even after the signatory’s user account is deleted.
Backups
at most 12 months — the latest 30 backups, beyond that one per month — recovery after data loss; what is deleted in normal operation disappears from the backups only when they expire.
Invoicing and accounting data
7 years — statutory retention obligation under § 212 UGB and § 132 BAO.
Server logs held by the hosting provider
runtime logs at most 30 days, shorter depending on the Vercel plan — determined by the provider, not by this platform.

A daily clean-up enforces these periods. Expired sessions, log entries about sign-ins and sign-in attempts after twelve months, notifications after 24 months, and invitations and secret links to private items 30 days after they end, and closed feature wishes 24 months after they were closed are deleted automatically. The checksum derived from the IP address for retrievals without an account is removed after seven days; the retrieval record itself remains without any personal reference, because it carries the supplier’s reporting.

For retrieval records linked to a company, the document-change half of the security log, records of consent, and declarations of conformity, the period is "the term of the contract plus 3 years". These four are not deleted automatically at present, because the end of a contract is not yet recorded technically. We delete them on request under section 10.

After an account is deleted, security log entries remain, because they evidence who filed which revision of a document. The link to the user account is severed immediately. The IP address and browser identification are removed three years after the account was deleted; the event and its timestamp are kept permanently. Three years matches the general limitation period.

9. Automated processing

There is no automated decision-making, including profiling, within the meaning of Art. 22 GDPR. No person is scored, ranked or assigned probabilities.

The only automated operations are the following, all of which relate to packaging items and documents rather than to people:

  • Limiting the number of requests per access point to prevent automated bulk access.
  • Checking uploaded files for file format and file size.
  • Calculating a completeness score for the filed master data and documents.
  • Displaying a documentation status that describes only whether documents are filed, valid or expired.
  • Sending notices 90, 30 and 7 days before a document expires, and once after it has lapsed.

Marking a packaging item as non-compliant is never done automatically; it is always decided by a person.

10. Your rights

You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21 GDPR).

Where processing is based on Art. 6(1)(f) GDPR — the security log and abuse prevention — you may object to it on grounds relating to your particular situation.

Exporting your own data and deleting your user account are available at any time under "Account" in the application. For anything beyond that, please write to office@pack-cert.at.

11. Right to lodge a complaint

Without prejudice to any other remedy, you have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR). The competent authority is:

Authority
Österreichische Datenschutzbehörde
Address
Barichgasse 40–42, 1030 Wien, Österreich
Email
dsb@dsb.gv.at
Telephone
+43 1 52 152-0
Website
https://www.dsb.gv.at