Terms
Last updated: 9 October 2026
These terms apply to all use of Vink. With an account you accept them on behalf of your organisation. After the terms, you'll find how we handle your data.
Who we are and what Vink does
Vink is provided by Everblaze, the sole proprietorship (eenmanszaak) of Rob van Baaren, Zilverschoon, 7577 CB Oldenzaal, the Netherlands. Chamber of Commerce (KvK) number: 57288135. In these terms that's "Vink" or "we".
Vink reads PDFs, emails and photos, typed, scanned or handwritten, and puts the values into the fields of your forms. People check what's uncertain. Then Vink sends the values to the systems you connect.
"You" and "the customer" is the organisation that has an account with Vink. Whoever signs up confirms they may represent that organisation.
For businesses only
Vink is only for businesses, organisations and self-employed people acting for their trade or business. Vink is not meant for consumers. Consumer rules, such as the right of withdrawal, therefore don't apply.
Other general terms, including the customer's, don't apply. Other agreements apply only when we put them in writing, for example with a Custom plan.
Your account
Keep your sign-in details secret. What happens through your account is your responsibility. Notice misuse? Report it at once, see Reporting a problem.
An Admin manages the organisation: members, forms, Integrations and the retention period. The customer decides who is an Admin.
Free credits and plans
The first organisation you create gets 200 free credits. They need no payment, and they don't expire.
A plan gives a number of credits per month. With annual billing you also get the credits per month. Unused credits lapse at the end of each month. The plans, prices and what an upload costs in credits are on the Pricing page.
Doesn't a new upload fit in your remaining credits? Then Vink refuses it, unless an Admin turned on extra usage. With extra usage, Vink charges extra credits up to the maximum the Admin chooses, at the price per extra credit on the Pricing page.
With a Custom plan we make our own agreements on volume, price, paying by invoice and a service level. We put those in writing. What they don't cover, these terms do.
Prices and payment
All prices are in euros and exclude VAT. VAT is added where it applies.
You pay in advance, monthly or annually, through Stripe. A plan renews automatically for the same period until you cancel. You pay for extra credits afterwards: one invoice after each month.
If a payment fails, Stripe tries again a few times. If it still fails, your plan stops. Your organisation then keeps only the free credits it has left.
We may change our prices. We email you at least 30 days before a new price applies to you. A new price applies from your next period. If you don't want it, you can cancel before that date.
Amounts paid are not refunded, also not when you stop early or don't use your credits. This doesn't apply where these terms or the law say otherwise.
Cancelling and ending
An Admin can cancel the plan at any time in the app, under Settings. The plan then runs to the end of the current month or year. After that you pay nothing more, and you can carry on with the free credits you have left.
You can delete your account yourself in the app, from the account menu. An Admin can delete the whole organisation under Settings, in the Danger Zone. Everything is then gone at once, except what the law requires us to keep, such as invoices. Doesn't that work? Email [email protected] and we delete it within 30 days.
We may block your access or end the agreement if you don't pay, or if you breach these terms seriously or repeatedly. Where possible, we warn you first.
Vink may refuse a sign-up, and may end or suspend an account at its own discretion, for example when use conflicts with the law, these terms, or Vink's interests. If Vink ends an account through no fault of yours, we refund the amount you paid in advance for unused periods of your plan.
If we stop offering Vink, we tell you at least 3 months in advance. We refund what you paid in advance for the time after the end date.
What you may and may not do
Put only documents into Vink that you may process. You need your own legal basis for that, as the GDPR requires. You may not:
- upload documents that are unlawful, or that you may not share;
- use Vink to infringe the rights of others;
- try to get around the security, or view another organisation's data;
- overload Vink, for example with requests above the API's limits;
- copy Vink, or reverse engineer the software beyond what the law allows;
- resell Vink or offer it as your own service without our written permission.
Found a security problem? Tell us, see Reporting a problem.
Your data
Your documents, the values read and your forms remain yours. You give Vink only the right to use them to provide the service.
Vink doesn't train AI models with your documents. The parties we use are listed under Subprocessors, with what they receive.
How long we keep your data and how you delete it is under How long we keep it. Keep your own copy of what you want to keep, for example through an Integration.
We may use usage figures to improve Vink, such as the number of credits used. They contain no document content and no personal data.
Processing personal data
Your documents can contain personal data, for example names, addresses and contact details of your customers and suppliers. For that data the customer is the controller and Vink the processor. This section is the data processing agreement between us, as Article 28 of the GDPR requires. It applies for as long as the agreement runs.
- Vink processes the data only on your instructions: these terms and what you set in the app, such as forms, the retention period and Integrations. If the law requires Vink to do otherwise, we tell you in advance where the law allows it.
- Everyone at Vink who can see the data is bound by confidentiality.
- Vink takes appropriate security measures. They are listed under Access and accounts and In transit and at rest.
- You give Vink general authorisation to use subprocessors. The current list is under Subprocessors. When a new subprocessor is added, we email the Admins at least 30 days in advance. If you have a reasonable objection to that party, you can cancel before the change takes effect. Vink imposes the same obligations on subprocessors and remains responsible for them.
- Transfers outside the EU happen only on a valid basis, such as the EU-US Data Privacy Framework or standard contractual clauses.
- Vink helps you, as far as reasonable, with requests from data subjects, with a data breach and with a data protection impact assessment (DPIA).
- If Vink discovers a data breach involving your data, we tell your organisation's Admins without undue delay, and within 48 hours. You report it to the supervisory authority yourself.
- After the agreement ends, Vink deletes the data within 30 days, unless the law requires it to be kept.
- Vink gives you the information you need to show that Article 28 is met. An audit is possible once a year, at your own cost and with reasonable notice.
Don't put special categories of personal data into Vink, such as health data, unless we agree to it in writing.
Checking the result
Vink reads documents with AI, and AI sometimes makes mistakes. Vink flags the values it is unsure about, but can't guarantee that every value is right.
Check the result before you rely on it. If you turn on Auto-Send, Vink sends documents without a human check. That is your own choice and your own risk.
Availability and changes
We do our best to keep Vink available at all times. We don't guarantee a particular availability, unless we agree on a service level (SLA) in writing.
For maintenance, Vink can sometimes be unavailable for a short time. We announce major maintenance in advance where possible.
We may improve and change Vink. If we remove an important feature, we tell you in advance.
Vink works with other parties' services, such as Google, Microsoft and Stripe. If those change or stop, an Integration may stop working.
Liability
Vink is liable only for direct damage. Liability is limited to the amount the customer paid Vink in the 12 months before the damage.
Vink is not liable for indirect damage, such as consequential loss, lost profit, missed savings, lost data and business interruption. Nor for damage from values you didn't check, or from documents Auto-Send sent.
These limits don't apply in case of intent or deliberate recklessness on Vink's part.
Report damage in writing, as soon as possible and at most 12 months after you discovered it. After that, your right to compensation lapses.
The customer indemnifies Vink against claims from others that arise because the customer breaches these terms or the law, for example with documents the customer wasn't allowed to process.
Force majeure
If force majeure keeps us from delivering, we are not liable. Force majeure includes an outage at a provider, an internet or power outage, a cyberattack or a government decision. If it lasts longer than 30 days, either of us may end the agreement.
Intellectual property
The software, the website and the name Vink are ours. You may use Vink while the agreement runs. That right is non-exclusive and non-transferable.
We may use feedback and ideas you share to improve Vink.
Changes to these terms
We may change these terms. For a change to your disadvantage, we email the Admins at least 30 days before it takes effect. If you don't agree, you can cancel before the change takes effect. If you keep using Vink after that, the new version applies.
If a provision is invalid, the others still apply. We replace that provision with a valid one that comes as close as possible to its purpose.
If the Dutch and English texts differ, the Dutch text prevails.
Law and disputes
Dutch law applies to these terms and the agreement. The UN Convention on Contracts for the International Sale of Goods (CISG) does not apply.
Disputes go only to the District Court of Overijssel (Rechtbank Overijssel). Let's first look for a solution together: email [email protected].
Where your data lives
- The app runs in Finland (Hetzner, Helsinki).
- The database is in Ireland (Convex, AWS eu-west-1). It holds everything except the files.
- Files (PDFs, photos, spreadsheets, Word files and emails with their attachments) are stored in Cloudflare R2 with EU jurisdiction.
- Reading happens with Vertex AI, in Google Cloud's EU multi-region.
Matching the read text to your Fields, and checking values on a scanned page or photo, happens at TypeSafe in the United States, sign-in emails go through Resend in the United States, and payments go through Stripe in the United States. See Who processes it.
How long we keep it, and deletion
- 30 days after sending by default. Your Admin can set anywhere from 1 to 365 days.
- Submissions never approved are deleted 90 days after upload.
- Rejected Submissions are deleted 30 days after rejection.
- Unsaved Form Proposals are deleted after 7 days, with their sample file.
- Deletion removes the file, what Vink read, all values and the Payload.
- We keep a short record (file name, who uploaded and approved it, dates, delivery status), never the file. We keep the values only when Keeping data is on.
- When an Admin turns on Keeping data, Vink keeps the values of every approved Submission as a Row. Data retention does not apply to Rows. They stay until an Admin deletes them or deletes the Organisation.
An Admin can delete any Submission right away, approved ones included. Pending retries for it are cancelled.
You delete your account yourself from the account menu. An Admin deletes the Organisation under Settings, in the Danger Zone. Everything is then gone at once.
Subprocessors
Every party that handles your data, what for, where, and what it receives.
| Name | Purpose | Region | Data |
|---|---|---|---|
| Hetzner | Hosting the app | Finland (EU) | Passes through all traffic |
| Cloudflare | Proxy and protection for the site and the app | Worldwide, nearest data centre | All traffic passes through it |
| Convex | Database and backend | Ireland (EU) | Everything except the files |
| Cloudflare R2 | File storage | EU | PDFs, photos, spreadsheets, Word files and emails with their attachments |
| Google Cloud Vertex AI | Reading the file | EU | The file or the email |
| TypeSafe | Matching read text to your Fields and checking it on the page | United States | The read text, and the page image of a scan or photo. |
| Resend | Emails from Vink: sign-in, invitations, plan and notices | United States | Email address and those emails |
| Cloudflare Email Routing and Workers | Receiving emails sent to an Intake Address | Worldwide, nearest data centre | Emails sent to an Intake Address, with their attachments |
| Stripe | Payments, subscriptions, invoices and VAT | United States | Your organisation's name and ID, the payer's email address, and the billing address, VAT number and payment details you enter at Stripe. Partly a controller itself, under its own privacy policy. |
| Google Analytics | Website statistics, only after your consent | United States | Which pages you view, your device, your browser and your country. Not in the app. |
Transfers to the United States rely on the EU–US Data Privacy Framework or Standard Contractual Clauses.
Access and accounts
Each Organisation only sees its own data. Every request is checked against a Membership, and this is covered by automated tests.
There are three roles: Admin, Editor and Member. An Editor does what a Member does. An Editor also changes existing Forms: Fields, General Instruction, Guidelines and Review Threshold. Only Admins can:
- invite and remove members, and change roles
- create, archive and delete Forms, and turn Auto-Send and Agent Approval on or off
- add, change and remove Integrations, and see their secrets
- change the Organisation's name and retention period
- delete Submissions and send failed Deliveries again
Auto-Send is off by default. An Admin turns it on per Form, and it only sends Submissions with no unsure values.
Sign-in is by email link, which expires after 5 minutes, or by password. Sessions last 7 days.
In transit and at rest
- HTTPS only, with HSTS.
- Links to a file expire after 5 minutes.
- Integration endpoints must use HTTPS.
- Integration secrets are encrypted (AES-256-GCM) with a key kept outside the database.
- Data at rest is encrypted by the providers.
- Payloads are signed with HMAC-SHA256, with one secret per Integration and a timestamp against replays. See Verify the signature.
- A test-send only sends example values or an approved Submission.
What we don't have yet
- No SOC 2 or ISO 27001 certification yet.
- No two-factor sign-in or SSO yet.
- No separate data processing agreement to sign yet. The processing terms are part of these terms, under Processing personal data.
Reporting a problem and contact
Found a security problem? Email [email protected]. We read every report and reply to you directly. Our security.txt has the same details.
Questions about privacy, or need the DPA? Contact us.