Privacy Notice
Vidima is built so your invoices and customer data stay on your computer. This page describes — in plain language — exactly what leaves your device, what we store on our servers, and your rights.
TL;DR
Your invoices, customers, settings, and signing keys live on your device. By default they never leave it; if you enable optional Pro or Studio sync, they leave only as an end-to-end encrypted blob we cannot read.
Seven things leave your device when Vidima is online: license activation (to enforce the device allowance included in your tier; it carries the Vidima version and the operating system, so we can help you if you write to us), update checks (so we can tell you when there's a new version), the email address you start the trial with (for the 30-day trial, its emails and the occasional Vidima announcement), payment (when you buy, handled by Stripe), the import from bexio, only if you start it yourself (the token and the requests go straight to bexio, not to us), the connection to your bank, only if you set it up yourself (it goes straight to your bank, not to us), and an anonymous usage notice (that the app was used and for how long, in bands; without your email address, your license, your computer or anything from your invoices; you can turn it off in Preferences).
What we don't do: follow what you do inside the app (which screens you open, which buttons you press, what you search for), ads, third-party cookies or crash reports. The app's only measurement is the anonymous usage notice described in section 3.
1. Who we are
This privacy notice is issued by Helvecraft Technologies LLC, registered in New Mexico (USA), developing from Switzerland. Helvecraft is the data controller for the limited data described below.
- Phone: +41 44 505 42 28
- Contact: info@helvecraft.com
- Products covered: the Vidima desktop application (Windows and macOS) and the websites
vidima.chandverify.vidima.ch
2. What stays on your device
Everything you create or import in Vidima — and we mean everything — is stored on your own computer in a folder under your user profile (on Windows: %APPDATA%\com.helvecraft.vidima). That includes:
- Customers, suppliers, products and services
- Invoices, credit notes, payment reminders, drafts
- VAT settings (effective or flat-rate, AFC rates)
- Your signing key for the cryptographic seal on PDFs
- The connection to your bank (EBICS), if you set it up: your keys, your contract details and what you download from the bank
- Automatic local snapshots (every ~6 hours) and any backups you export
- Your language and UI preferences
We have no readable copy of any of this. If you enable the optional sync (Pro/Studio), we hold only an end-to-end encrypted blob we cannot decrypt — see section 3. If your device fails and you have no backup or sync set up, that data is not recoverable from us — there is nothing readable for us to recover.
3. What leaves your device when you use online features
License activation and heartbeat — our license activation service
To enforce the device allowance included in your tier, Vidima sends, on activation and periodically thereafter:
- The complete signed key, transmitted over TLS for validation; the activation record retains only its hash. For delivery, resend or redemption, the signed key may also be retained in restricted operational purchase and redemption records.
- An opaque device identifier (derived locally with SHA-256). Versions currently in distribution may also transmit an optional device name; the service discards it and does not retain it.
- The Vidima version and the operating system; on activation, on a license transfer, when moving to a higher plan or when checking the trial's features, also the app's language, so we can write to you and show you pages in your language.
- If you paste a short code instead of the key, the app sends that code with the device identifier to redeem it for your key.
Why: to count bound devices against the tier limit and offer a transfer when all seats are in use. The date of each device's last connection also tells us whether a license is still in use; we look at it to see whether a customer may need help. It is a single date that is overwritten: we keep no history.
Stored: Cloudflare D1 database (vidima-activations), one row per bound device containing the key hash, opaque device identifier, and activation and heartbeat timestamps.
Device register: for licenses with the transfer limit in §4 of the EULA, for every device that receives, loses or releases the seat we also keep a pseudonymous fingerprint of the key and of the device (SHA-256, from which neither the key nor the identifier can be recovered) with the last date it held the seat. It is used only to count the license's distinct devices and is deleted one year after that date.
Transfer notices: with every transfer, and when a device takes the seat released by another, we write to the license's email address (through Resend, Inc., United States), so that you know if someone else is using your key.
Moving to a higher plan: when you ask for it in the app, Vidima sends the key and the chosen plan to open the payment page. After payment the new key receives the device seats of the previous one; the previous key's seats stay until that device is released. We keep the change (both plans, the dates, the payment and both keys) to deliver the new key and to be able to undo or refund it.
License features and the trial: licenses bought during a trial started before the new plans, or within 30 days after it ended, include every feature (§1 of the EULA). To know this, at payment the service looks up the trial of the payment email; if the license is under another email, the app sends the key, the device identifier and the trial email: the one the app itself sent when the trial began on that computer or, if you started the trial with another email or on another computer, the one you type in “Enter the trial email”. We note in the trial which license it was used for, so that it counts only once.
Vidima Connect: this subscription is not on sale yet, but the app already asks our license service whether your license has it, even if you have not set up the connection to your bank: shortly after every start, when your license gets a new key and when you check it yourself in the Bank section. It sends only your license key; nothing from your bank.
Legal basis (nFADP / GDPR Art. 6(1)(b)): performance of the licensing contract you accept when you activate Vidima.
Update checks — our update service
When Vidima starts (at most once a day, or sooner if the last check failed) and whenever you check manually, it asks our update server whether a newer version is available. The request includes:
- Your current Vidima version
- Your operating system and architecture
Why: so the app can tell you that 1.1.1 is out and offer the download.
Stored: the response is computed on the fly. The request itself is logged by Cloudflare for security and abuse prevention (typical edge-log retention, IP truncated).
Opt-out: you can disable the auto-updater in the app's settings. When you install Vidima from the Microsoft Store, the updater is disabled automatically (the Store handles updates).
30-day trial — the email address you enter in the app
To start the trial, the app sends the email address you enter, the language, the operating system and the Vidima version to vidima.ch; if there is no connection at that moment, it tries again the next time it starts. We store this data in the Cloudflare D1 database, together with the country the request comes from, the trial's start and end dates, its status (running, expired, converted to a purchase or closed after unsubscribing) and when we wrote to you. We use it for your trial and to send you the welcome email, the trial emails and, now and then, an announcement about Vidima, such as news or price changes, through Resend, Inc. (United States). Every email has an unsubscribe link; how long we keep this data is in section 7.
Multi-device sync — optional, end-to-end encrypted (Pro & Studio)
Sync is off by default and available only on the Pro and Studio tiers. If you turn it on, here is exactly what happens to your data:
- Vidima derives an encryption key on your device from a secret only you hold (and your recovery code). That key never leaves your devices and is never sent to us.
- Your data is encrypted on the device before it is uploaded. What reaches our relay is an opaque encrypted blob — we store the content only as ciphertext.
- Because we never have the key, not even we can read your data (zero-knowledge). The relay's only job is to pass that encrypted blob between the devices on your own license.
- Your other devices download the blob and decrypt it locally with the same key, so they stay up to date automatically.
Why: to keep your invoices and configuration in step across your machines without ever handing your readable data to anyone — including us.
Stored: encrypted blobs on Cloudflare R2. D1 holds the minimum pseudonymous protocol metadata needed to coordinate them: a license hash, opaque device IDs, a server-generated network generation, the designated primary device, version and timestamps, ciphertext size and integrity hash, and short-lived operation leases. We store no plaintext, decryption key, device name, raw IP address or User-Agent for sync. A keyed HMAC used for abuse rate-limiting expires within about 10 minutes. With several companies, each company has its own network with the same metadata, plus a small descriptor encrypted with the data key, holding the company's identity and name, which is used to show you the companies on the network and which we cannot read. Of the data key we keep only a check fingerprint, from which the key cannot be derived.
Even if you don't turn sync on: the app contacts the relay, sending only the license key and the device identifier, in two cases: when you transfer the license to this device, to find out whether there is a sync network (the usual one or the open company's; if there is, the app closes all your license's networks, as it warns you before you confirm), and, if you have several companies, when you view sync for a company other than the main one, to find out which networks your license has. Every request to the relay, with sync on or off, carries your license key and the device identifier, to check that the network is yours; in D1 we keep only the key's hash.
Your controls: leaving sync off uploads nothing. Disconnecting one device removes that device's active binding but keeps the shared encrypted network for your other devices. The primary device's separate, double-confirmed “End synchronization” action deletes all encrypted blobs and active network/device/operation metadata. A content-free termination receipt is retained for up to 180 days so retries from older app versions cannot affect a newly created network.
Import from bexio — only when you start it
Vidima can import your data from bexio. This is a separate connection that only opens when you start the import yourself. You paste a connection key (token) that you create in bexio. The app sends it, together with the requests that read your data (contacts, invoices, expenses and accounting), straight to bexio (api.bexio.com), without going through our servers. The app only reads: it changes nothing in bexio.
What we see: nothing. During the import, the token and your bexio data do not pass through us: we neither see nor store them. The token stays in the app's memory for this import only and is not saved anywhere, not even on your device. What comes from bexio stays on your device, with the rest of your data (section 2). If you have turned on sync, this data travels to and is stored on our relay like the rest of your data: end-to-end encrypted, so we cannot read it.
For what bexio does with your data, bexio's own privacy policy applies; bexio is not one of our sub-processors.
Connection to your bank (EBICS) — only if you set it up
Vidima can connect to your bank via EBICS, the channel Swiss banks offer to businesses, to download your account statement and credit notifications and to send payment orders. You need an EBICS contract with your bank. The connection starts when you click “Connect to my bank”, or when you load onto this device a copy of the signature or a backup that contains it. When you click the button, the app creates your keys on your device and sends their public part to the bank, together with your contract details (the bank code, your customer number and your user number) and your company's name and country, which go into the certificates.
Everything goes straight to your bank's EBICS server (the address given in your contract), over HTTPS, without going through our servers. Apart from the first request (which EBICS versions the bank uses, carrying only the bank code) and the messages that hand over your public keys, every message is signed with your keys; statements, notifications and payment orders are also encrypted under EBICS.
- Statement and notifications: when you click “Fetch the statement” or “Fetch the notifications”, the app asks the bank for your account's transactions (camt.053 and camt.054) and decrypts them on your device.
- Payment orders: when you click “Send to the bank”, the app sends the order (pain.001) with what you put in it: your name and IBAN and, for each payment, the payee's name, address and IBAN, the amount and the reference or message. It never goes out on its own, and the bank does not execute it until you approve it in your e-banking.
- What the app does on its own, while it is open: while you wait for the bank to enable your access, the app checks with the bank every 6 hours whether it has done so. And with Vidima Connect, a subscription that is not on sale yet, it fetches the statement by itself at most once every 20 hours; if an attempt fails, it tries again 2 hours later.
What we see: nothing from your bank. Your keys, your contract details, the statements and the payment orders do not pass through us: we neither see nor store them. They stay on your device, with the rest of your data and the same protection (sections 2 and 10), and the bank connection does not travel with sync. What does travel, if you have turned sync on, is what goes from the statement into your invoices and your accounting, whether you record it or the app does with Connect: the amount, the date, the reference, the identifiers the bank gives the transaction and the statement, your account's IBAN, the transaction text or the payer's name and, sometimes, their IBAN. It travels end-to-end encrypted, like everything else. Your private keys only leave your device in copies: with “Save a copy of the signature”, an unencrypted file you save wherever you choose, and inside the encrypted backups, both the ones you make and the ones the app makes by itself in the folder you chose (a USB stick or a cloud folder, for example).
The app prepares the letters for the bank (INI and HIA) and the contract request on your device; you send them yourself. For what your bank does with your data, your contract and your bank's privacy policy apply; your bank is not one of our sub-processors.
App usage — an anonymous notice
To know whether Vidima is used and how much, the app counts, on your computer, the minutes during which you have it in front of you and are using it. When you reach a band in a day (used, more than 15 minutes, more than 1 hour, more than 3 hours), it sends a notice to vidima.ch. That is at most four notices per day of use.
Each notice carries only this:
- the week of the year (not the day or the time);
- whether it is a trial, a license or someone looking at the app without having given an email address;
- for trials, which week of the trial it is;
- the band reached;
- whether it is the first day of use that week;
- a fixed number that indicates the format of the notice (always the same).
It does not carry your email address, your license key, any identifier of the computer or of the installation, or anything from your invoices, customers, amounts, bank or bexio. Nor which screens you open or what you do. Because it carries nothing that links one notice to another, we cannot follow an installation from one day to the next or tell who is who.
What we keep: only weekly totals (for example, “4 trials used Vidima this week; 2 for more than an hour”), in our Cloudflare D1 database. We do not keep a row per notice, the IP address, the country or the time. The IP address arrives with the request, as with any web page, and is used only at that moment and in memory to curb abuse: we do not write it anywhere.
How it is turned on and off: if your business is in Switzerland, it is on by default. If your business is outside Switzerland, it is off by default, and the app only counts and sends if you turn it on yourself. Until you have entered the country of your business, it counts as Switzerland. Either way you can change it whenever you like under Preferences → “Anonymous usage statistics”; you can also see there what was last sent. When you turn it off, the app deletes what it had counted.
Legal basis: in Switzerland, our interest in knowing whether the program is used, for statistical purposes and without identifying anyone (Art. 31(2)(e) nFADP); outside Switzerland, your consent, which you can withdraw at any time (GDPR Art. 6(1)(a)).
PDF verification — verify.vidima.ch
Every invoice PDF you generate carries a small QR code in the footer that points to verify.vidima.ch. When your customer (not you) scans it, the verifier shows them: who issued the invoice, when, the amount, and whether the PDF is authentic.
What goes into that QR: only what you put there — issuer, date, amount, and the ECDSA signature. No customer-side data is collected when someone verifies; the QR contains its own payload.
Stored: nothing about the verifier visit is retained beyond standard edge logs.
Payment — Stripe
When you buy a Vidima license by card, you are redirected to a Stripe-hosted checkout page. Your card data goes directly to Stripe — Helvecraft never sees it. Stripe is our sub-processor for payments.
What we receive from Stripe afterward: your email, your invoice address (for the tax receipt) and the fact that payment succeeded. We use that to issue your license key. See Stripe's privacy policy for what Stripe does with your data.
Payment by QR invoice
If you pay by QR invoice, you enter your company or full name, street and number, postcode, town, country, email and, if you wish, your VAT or UID number and your purchase order reference directly on vidima.ch. We keep the order (email, language, plan, amount, reference and the country it was placed from) in the Cloudflare D1 database. The billing details do not go into the database: they reach Helvecraft by email through Resend, Inc. (United States), as does the confirmation we send you, and we keep them with the invoice for Swiss bookkeeping obligations (typically 10 years). Nothing goes through Stripe with a QR invoice.
Email from the download page
If you leave your email on the download page, we keep it with the page language, the country and, from a computer, the system (Windows or macOS), to send you the quick-start guide or, if you are on a phone, the link to download Vidima on your computer. The email is sent through Resend, Inc. (United States) and we do not use your address for advertising. Every email has an unsubscribe link; how long we keep the address is in section 7.
Website measurement — first-party and aggregated
On vidima.ch we keep daily aggregate counts for a small funnel: landing, pricing view (and whether a visit stays on the prices for a minute), download intent and redirect, whether the download page is opened on a phone or tablet and whether the link is requested by email from there, trial lead and app activation, checkout, paid or complimentary license, Store link, feedback sent, and whether a site invitation is seen, clicked or closed. For downloads and payments we also count the page through which the visit arrived (always a vidima.ch page, never another site's).
- No Google Analytics, advertising tracker or third-party analytics script is loaded.
- No raw IP address, user-agent, email, feedback message, full referrer URL or browser session identifier is stored in the measurement tables.
- A random identifier exists only in your tab's
sessionStorage. The server uses it transiently to create an HMAC deduplication key, then discards it; that key expires after 48 hours. - Campaign and referrer data is reduced to an allowlisted category. A random checkout-attempt reference is retained for at most 90 days only to reconcile the Stripe session.
- Browser-side measurement honours Global Privacy Control and Do Not Track. Necessary server records for an explicit trial, payment, license activation or support action still apply.
- In your browser, for the site invitations: if you close one, it remembers for 7 days that you don't want to see it, and it stores the time of the last one shown to you, so that no other appears within 12 hours (in
localStorage). While the tab is open, it also remembers which page the visit arrived through, whether an invitation has already been shown and whether the guide's QR code reader was used (insessionStorage). Of all this, only the entry page leaves your device, with the download or payment, to be counted as described above.
Instant notices: when a visit from Switzerland or Liechtenstein opens checkout, clicks download on a computer or stays on the prices for a while, we receive a notice with no personal data: what happened (the plan, if checkout was opened; the system, for a download), the page language, the country and where the visit came from (which search engine, direct or another source). It carries no IP address, identifier or anything that says who you are, and we do not store it in our databases: it reaches us as a message through the same messaging service as the chat and stays there until we delete it. To avoid two notices about the same visit, or more than two a day from the same connection, we use 48-hour deduplication keys like the one described above, derived from the tab identifier and from an HMAC of the IP address; the IP address is not stored. With Global Privacy Control or Do Not Track no notice is sent.
Chat on vidima.ch
On vidima.ch you can write to Helvecraft through the chat. A real person answers, not a bot: within minutes if we are online, otherwise as soon as possible; if you have left the page, the reply reaches you by email.
- What we keep: what you enter in the form before you start (name, email address and topic), the messages and images in the conversation and our replies, the language and the page you wrote from. We do not keep your IP address or browser user-agent: abuse limits use an HMAC of the IP with a daily key that is deleted after two days.
- Images: if you attach an image, your browser shrinks and re-encodes it before sending it, so it no longer carries the data a photo usually holds (EXIF, such as the GPS location or the phone model). We keep it in private Cloudflare storage (R2) in the European Union, and only whoever has the conversation open in their browser can see it.
- What for: only to answer you and continue the conversation. We do not use it for advertising or newsletters. For the email address you enter, our licensing system tells us only whether it belongs to a Vidima license, its plan and whether the license dates from before the new plans, so we can reply within that plan's support time. We see this in the conversation alert, which goes through the messaging service (see “Who receives them”); it is not stored in the chat.
- Automatic translation: so that we can answer you in your language, messages are translated automatically with Workers AI, the translation service of our infrastructure provider, Cloudflare, Inc. (United States). Cloudflare does not keep the texts once they are translated and does not use them to train models.
- Who receives them: so that your messages reach Helvecraft, the conversation (name, email address, topic, language, page, messages with their translation, images and, if the email address belongs to a license, its plan) passes through the messaging service we use to run the chat. That provider is based in the United Arab Emirates, outside Switzerland and the EEA.
- Email: if you leave the page before reading our reply, it reaches you by email, sent through our email provider, Resend, Inc. (United States). The email may include your first name, your last message and the images in the reply.
- In your browser: the chat stores a random conversation identifier in
localStorageso you can find the conversation when you come back; no cookies. The form data and your first message stay in the tab'ssessionStorageuntil the conversation has started. - How long: messages, their translations and images are deleted automatically after 90 days, and the whole conversation (name, email, topic, language and page) 90 days after its last activity. We delete the copies held by the messaging service by hand once they are no longer needed for your request, or when you ask us to.
- Deletion: to have your conversation deleted sooner, write to info@helvecraft.com from the address you used in the chat, or ask in the chat itself. We delete it from our database, from the image storage and from the messaging service.
Legal basis (nFADP / GDPR Art. 6(1)(b)): answering the request you make. Sending the conversation to the messaging service, outside Switzerland, is directly connected with your request about buying or using the software (Art. 17(1)(b) nFADP; Art. 49(1)(b) GDPR). If you prefer not to use the chat, you can also write to us at info@helvecraft.com.
Partner program — helvecraft.com/partner
At helvecraft.com/partner anyone can apply to become a Helvecraft sales partner, and accepted partners have a private area.
- If you apply to become a partner: name, email, languages, area and the businesses you know, plus the language of the form. We use them only to review the application and reply to you. We receive a notification in the messaging service we use for the chat.
- If you are a partner: the same details and your start date. To enter the partner area you receive a link by email (no password), and your browser keeps a technical session cookie for 30 days. We store the customers you name, the currency you want to be paid in and the commissions paid.
- If a partner named you to us: the partner gave us your company name, email and, if they added it, the contact person. We match that email against licenses only to calculate the commission. The partner who named you first sees whether you bought a license after being named, the plan and the date; nothing else: no amounts, no billing details, no app usage. Basis: our legitimate interest in paying commissions correctly. You can object by writing to info@helvecraft.com.
- Partners outside Switzerland: partners can work from any country. If a partner is in a country that Switzerland does not recognize as safe for personal data, what we show them about the customers they named is covered by standard contractual clauses in the partner agreement.
- Light or dark theme: if you choose one, a cookie remembers it for a year. It holds only “light” or “dark”, no personal data.
4. What we do not collect
- The readable contents of your invoices, customers, products, or any document (if you enable sync, what we hold is end-to-end encrypted ciphertext we cannot read)
- What you do inside the desktop app: which screens you open, which buttons you press, what you search for, what time you start and finish. Nor raw browsing clickstreams on the website (the instant notices in section 3 are one-off messages, with nothing that identifies you). The app's only measurement is the usage notice described in section 3, in totals.
- Crash reports (Vidima ships with no third-party analytics service)
- Third-party advertising trackers
- Cookies for behavioural profiling (the websites use only strictly necessary state)
5. Sub-processors
We rely on the following third parties to run the online parts of Vidima:
- Cloudflare, Inc. — Workers, R2, D1, Pages and CDN for our infrastructure, and Workers AI for automatic translation in the chat. Cloudflare may log request metadata for security and abuse prevention.
- Stripe Payments Europe Ltd. — payment processing.
- Messaging service (United Arab Emirates) — delivery of vidima.ch chat messages and instant notices to Helvecraft (see section 3).
- Resend, Inc. — sending emails, such as the chat reply when you are no longer on the page.
The Vidima desktop app itself has no other network calls than the ones listed above. If you turn on multi-device sync (optional, Pro and Studio only), the app also contacts our relay to send and receive your data as end-to-end encrypted text that we cannot read; even with sync off, it contacts the relay in the two cases described in section 3, sending only the license key and the device identifier. And if you import from bexio, the app contacts bexio directly (api.bexio.com; see section 3), which is not one of our sub-processors. Likewise, if you connect your bank via EBICS, the app contacts your bank's EBICS server directly (see section 3); your bank is not one of our sub-processors either.
6. Where the data is stored
- Your device data: on your device. We have no readable copy.
- Sync data (only if you enable it on Pro/Studio): end-to-end encrypted blobs on Cloudflare R2/D1. We store ciphertext only and hold no decryption key, so we cannot read it.
- License activation records: Cloudflare D1, replicated across Cloudflare's global edge network.
- Payment data: Stripe's infrastructure (EU/EEA-based processing for European customers).
- vidima.ch chat: Cloudflare D1 (
vidima-chat) and, for images, Cloudflare R2, in the European Union; to reach Helvecraft, the messaging service we use to run the chat. - Partner area: Cloudflare D1 (
helvecraft-partner) in the European Union; emails via Resend.
7. How long we keep things
- License activation row: while the device remains bound. It is deleted when that device is deactivated or displaced by a transfer; after moving to a higher plan, the previous key's row stays until that device is released.
- License device register: one year from the last date the device held the seat; it is then deleted automatically.
- Plan changes: like payment records, for accounting obligations.
- Update-check requests: not persisted by us. Cloudflare may keep edge logs for a short period per their policy.
- Optional sync: encrypted blobs and active protocol metadata remain while the network exists. “End synchronization” deletes them; its content-free retry receipt expires within 180 days. Operation leases and HMAC rate-limit entries expire within about 10 minutes. Abandoned empty networks with no active device are removed after 30 days.
- App usage: anonymous weekly totals for up to 24 months. Nothing per notice or per installation.
- Payment records: retained by Stripe per their policy and by us for Swiss bookkeeping obligations (typically 10 years for tax records).
- Signed key and redemption record: for the validity of the license and for as long as needed for delivery, recovery, revocation and support.
- Download and trial leads: deleted within 30 days after unsubscribing; otherwise no later than 24 months after the last interaction.
- Website measurement: anonymous daily aggregates for up to 24 months; transient deduplication keys for 48 hours; checkout-attempt and feedback receipts for up to 90 days; instant notices are not stored in our databases, and the message stays in the messaging service until we delete it.
- Support emails: as long as needed to resolve your request, plus reasonable archival.
- vidima.ch chat: messages, translations and images for 90 days; the whole conversation for 90 days after its last activity; copies in the messaging service for as long as they are needed for your request or until you ask us to delete them.
- Partner program: applications not taken further, 6 months; partner and named-customer data, for the duration of the collaboration and as long as needed to pay commissions earned; commissions paid, like payment records (10 years). Sign-in link: 30 minutes (welcome link, 7 days); session: 30 days.
8. Your rights
Under the Swiss Federal Act on Data Protection (nFADP, in force since 1 September 2023) and, where applicable, the EU General Data Protection Regulation (GDPR), you have the right to:
- Access — ask us what data we hold about you
- Rectification — ask us to correct anything inaccurate
- Erasure — ask us to delete your data (we can delete your license activation row; the data on your device is yours to delete from your own machine)
- Portability — receive your data in a portable format (your invoices already are: they live as JSON on your device and Vidima has built-in export)
- Object — ask us to stop processing in certain circumstances
- Lodge a complaint with the Swiss Federal Data Protection and Information Commissioner (FDPIC / edoeb.admin.ch) or your local EU supervisory authority
To exercise any of these rights, email info@helvecraft.com. We aim to respond within 30 days.
9. Children
Vidima is a professional invoicing tool intended for businesses and self-employed adults. It is not designed for, marketed to, or intended to be used by anyone under 18.
10. Security
Your data on your device can be protected by an optional session PIN, after which Vidima encrypts your state file at rest with AES-GCM. The keys of your bank connection are always stored encrypted on your device, even if you do not use that protection: they are sealed with a key from your computer which, on Windows, is tied to your account. Our infrastructure runs on Cloudflare with TLS in transit and minimal stored data. We store only key hashes for activations; the complete signed key may be retained in operational purchase and redemption records when needed for delivery, recovery, and support.
If a security incident affecting your data occurs and the law requires it, we will notify you promptly.
11. Changes to this notice
If we change this notice, we'll bump the "Last updated" date below. Changes are published on this page.
12. Contact
Questions, requests, or just want to understand something better:
- Email: info@helvecraft.com
- Phone: +41 44 505 42 28
- Postal address: Helvecraft Technologies LLC, 1209 Mountain Road Pl NE, Ste R, Albuquerque, NM 87110, USA
Last updated: 2026-11-12
Effective: 2026-11-12
Version: 1.5
idima