Previous version of the Privacy Policy, in force from 19 November 2026 to 25 December 2026.
Privacy Policy
This policy explains how NC Labs GmbH handles personal data in wesign.now and on our websites. It follows the Swiss Federal Act on Data Protection (FADP) and, where it applies, the EU General Data Protection Regulation (GDPR).
At a glance
- European first. Our database runs in Ireland and each workspace stores its document files in the EU, Switzerland, the United Kingdom or the US. Where a provider outside Europe is involved, we name it below.
- For documents, signers and viewers of shared documents, the workspace that sends or shares is responsible and we process the data on its behalf.
- We never sell personal data, show no ads, and never send your documents or signer data to an AI service.
- No third-party tracking or advertising cookies. Statistics run without cookies and never receive document links.
- Questions and requests: support@wesign.now.
1.Who is responsible
In short:We are responsible for accounts and our websites; the sending workspace is responsible for its documents and signers.
NC Labs GmbH, Maneggstrasse 83, 8041 Zurich, Switzerland, support@wesign.now.
- We are the controller for account and login data, billing, support requests and bug reports, sales inquiries, job applications, newsletters, the referral programme and our websites.
- The workspace (our customer) is the controller for the documents it uploads and shares and for the data of its signers, contacts, recipients and the viewers of its shared documents. We are its processor and use that data only to provide the service, as agreed in our terms and, where concluded, a data processing agreement.
2.What data we process
In short:Account data, the documents you send, signer details and the evidence of each signature.
| Account | Name, email address, phone number if given, company, role, sign-in data (one-time codes, passkeys; name, email address and profile picture of your Google account if you sign in with Google), settings, your saved signature |
|---|---|
| Workspace and billing | Organisation name and address, plan, invoices, billing contact; card data is handled by Stripe, not by us |
| Documents | The files you upload or create, templates, field values, documents sent to a workspace through its request form |
| Google Drive imports | The file you pick in Google Drive, its name and the time it was last changed; for a template made from a Google Doc, the doc’s ID, see section 9 |
| Signers and contacts | Name, email address, phone number (for SMS verification), company and function if the sender states them, the signature image |
| Evidence (audit trail) | What happened when: sent, opened, SMS code entered, signed; IP address in shortened form (its last part removed), browser, time |
| Viewers of shared documents | What the sharing workspace asks for before opening (for example name, email address, phone number), pages viewed and for how long, see section 6 |
| Technical | Server and error logs, the API log of a workspace’s calls (with shortened IP), a masked replay of the page when an error occurs, embedded signing sessions, webhook deliveries with their content, delivery reports of our emails, SMS sent per workspace (count) and verification attempts |
| Website and campaigns | Pages visited (without access codes), the campaign and referring page that brought you, newsletter subscription and its consent record |
| Inquiries, applications and support | What you send us through a contact, demo, offer, non-profit, job, support or bug-report form, see section 7 |
3.Why we process it
In short:To run the service, prove signatures, bill, keep things secure, and email you about the service.
- Providing the service — accounts, sending, signing, sharing, storing and delivering documents (contract; GDPR Art. 6(1)(b)).
- Evidence — the audit trail and seal that record what was signed, when, and through which email address or phone number (the customer’s and our legitimate interest, Art. 6(1)(f); legal obligations, Art. 6(1)(c)).
- Security and stability — preventing abuse, bots and shared or misused logins, finding and fixing errors, telling senders when an email did not arrive (legitimate interest, Art. 6(1)(f)).
- Billing and accounting — invoices and records we must keep by law (Art. 6(1)(b) and (c)).
- Inquiries and offers — answering you and preparing an offer (steps before a contract, Art. 6(1)(b); legitimate interest, Art. 6(1)(f)).
- Improving our websites and the app — statistics without cookies, and knowing which campaign brought a new account (legitimate interest, Art. 6(1)(f)).
- Service and account emails — invitations, receipts, security and important service notices (contract, Art. 6(1)(b)).
- Product news and offers to customers — we may email account holders, in particular those of paying workspaces, about features, tips and offers of our own service (legitimate interest, Art. 6(1)(f); Swiss UWG Art. 3(1)(o)). You can object at any time with the link in every such email or in Settings → Communications.
- Getting-started emails — after a workspace is opened, its owner receives a few short emails with tips for sending the first document (at most five, at least two days apart; they stop once the workspace has sent its first document), and one when its first document is fully signed. We see which of their links was used when it is opened while signed in to the app; they carry no tracking pixels. You can unsubscribe with the link in every such email or in Settings → Communications (legitimate interest, Art. 6(1)(f); Swiss UWG Art. 3(1)(o)).
- Newsletters to everyone else — only with your consent; you can unsubscribe in every email (consent, Art. 6(1)(a)).
- Referral programme — crediting the workspace that referred a new customer (contract with the referrer; legitimate interest, Art. 6(1)(f)), see section 8.
We do not use personal data for our own advertising and never sell it. We publish aggregate figures such as milestones, never personal data. Engagement statistics in Present are run for the workspace that shares the document, on its instructions (see section 6).
4.Where your data is stored
In short:European by default. Document files stay in the region your workspace picks.
- Document files (uploaded, converted and signed PDFs) are stored in the region the workspace has chosen, on every plan. A change of region applies to new documents.
- The database — accounts, signers, signatures, the audit trail and Present viewer records — runs in 🇮🇪 Ireland for all regions. Our application runs in 🇮🇪 Ireland too; static pages are delivered through Vercel’s global network.
- Page images of documents, images in templates, logos and avatars are kept in one central store in 🇬🇧 London, independent of the workspace region.
We prefer European providers and European regions wherever one meets our needs. Email delivery, error monitoring, document conversion and AI run in European regions, even where the provider is a US company. Some providers process data in the US — for example one-time SMS codes, payments, sign-in with and imports from Google, bot protection and website statistics (see the list below). The United Kingdom, where our central image store runs and where a workspace can keep its document files, has an adequacy decision from both Switzerland and the EU. For transfers outside Switzerland and the EU/EEA we rely on an adequacy decision (such as the Swiss-US and EU-US Data Privacy Framework, where the provider is certified) or on the EU Standard Contractual Clauses with the amendments required by Swiss law.
5.Service providers
In short:These companies help us run the service. Those that process data on our behalf may use it only on our instructions.
Flags show where the data is processed as we have set it up; where the provider’s company is based elsewhere, that is shown in brackets. With the providers that process personal data on our behalf we have a data processing agreement that binds them to confidentiality and data protection. Providers acting under their own responsibility (such as Stripe and Google) and services your browser loads directly are covered by their own terms. We update this list when it changes.
Process your workspace’s data on our behalf
| Provider | What for | Data | Where |
|---|---|---|---|
| Supabase | What for:Database and sign-in | Data:Customer data: signers (name, email, phone), contacts, signatures, audit trail, Present viewer records. Our own: accounts and workspaces; its sign-in logs may include the full IP address | Where:🇮🇪(company 🇺🇸) |
| Vercel | What for:Hosting of the application and its servers; request logs; routing of AI requests through its AI Gateway where we use it | Data:All data, customer data included, passes through while it is processed; request logs with full IP address | Where:🇮🇪(company 🇺🇸) |
| Vercel Blob | What for:Storage of document files in the region the workspace chooses, and a central store for images | Data:Customer data: uploaded, converted and signed PDF files in the workspace region (Frankfurt, Zurich, London or Washington, D.C.); page images of documents, images in templates and logos in the central store in London. Our own: members’ avatars | Where:🇩🇪🇨🇭🇺🇸🇬🇧(company 🇺🇸) |
| Resend | What for:Sending emails (invitations, reminders, completed documents, account and service emails, newsletters) and reporting their delivery | Data:Customer data: recipient name and email, document title, attached signed PDF and audit trail, delivery reports (delivered, delayed, bounced). Our own: account and service emails, newsletters, CVs sent through our careers page | Where:🇪🇺(company 🇺🇸) |
| Sentry | What for:Error monitoring; a masked replay of the page when an error occurs; server logs we forward from our hosting | Data:Technical error data, IP address, browser, also from signing and shared-document pages (customer data); on-screen text and inputs are masked | Where:🇪🇺(company 🇺🇸) |
| TwilioOnly when the feature is used | What for:One-time SMS codes that confirm a signer’s phone number (advanced signatures) | Data:Customer data: the signer’s phone number and the one-time code. Never documents, names or signing links. | Where:🇺🇸 |
| CloudConvertOnly when the feature is used | What for:Converting Word files and images to PDF, repairing or compressing PDFs, rendering templates | Data:Customer data: the content of the document, including filled-in values | Where:🇩🇪 |
| Vercel BotIDOnly when the feature is used | What for:Bot protection on public forms (sign-up, Present access and access requests, document request forms, contact, abuse-report and NGO forms) | Data:Browser and device signals, IP address, also of the viewers of a workspace’s shared documents (customer data) | Where:🇺🇸 |
| AnthropicOnly when the feature is used | What for:AI assistant and translation in the template editor; checking NGO applications. Called directly or through Vercel’s AI Gateway | Data:Customer data: the text you give the assistant or the template being translated. Our own: for NGO applications the organisation’s details, including the contact email. Never your documents or signer data. | Where:🇪🇺(company 🇺🇸) |
| ExpoOnly when the feature is used | What for:Push notifications, when you use our mobile app | Data:Customer data: notification text (document and signer name). Our own: the device token of your app | Where:🇺🇸 |
Process only our own data
| Provider | What for | Data | Where |
|---|---|---|---|
| Vercel AnalyticsOnly when the feature is used | What for:Statistics on our websites and in the app, without cookies | Data:Page views, with access codes and query strings removed from the address; browser, country | Where:🇺🇸 |
Act under their own responsibility
| Provider | What for | Data | Where |
|---|---|---|---|
| StripeOnly when the feature is used | What for:Payments and invoices | Data:Billing contact, workspace name; card data goes to Stripe directly. Stripe is its own controller for payments | Where:🇺🇸 |
| GoogleOnly when the feature is used | What for:Sign in with Google and imports from Google Drive, if you choose them | Data:Name, email address and profile picture of your Google account; the file you pick in Google Drive. Google provides these from your own Google account, under its terms with you | Where:🇺🇸 |
| European Commission DSS validation serviceOnly when the feature is used | What for:A second opinion on /verify when our own check cannot decide | Data:The PDF uploaded for checking | Where:🇪🇺 |
Loaded by your browser
| Provider | What for | Data | Where |
|---|---|---|---|
| Google Fonts | What for:Fonts in the template editor | Data:IP address and browser of the person using the editor | Where:🇺🇸 |
| DuckDuckGo and Google favicon services | What for:Small company logos next to contacts and when detecting a logo | Data:The web domain of a contact’s email address or company website | Where:🇺🇸 |
| Google (profile pictures) | What for:Showing the profile picture of members who sign in with Google | Data:IP address and browser of the person viewing the app | Where:🇺🇸 |
| unpkg | What for:A fallback copy of the PDF viewer, on the signing page and in document viewers, only when our own copy cannot be loaded | Data:IP address and browser of the person viewing the document (never the document) | Where:🇺🇸 |
| Sentry (replay code) | What for:Loading the code for the masked error replay | Data:IP address and browser | Where:🇺🇸 |
Each completed document is time-stamped by an independent timestamp authority (RFC 3161), currently DigiCert, with freetsa.org as a fallback. It receives only a hash (SHA-256) of the signature data, never the document or any personal data.
Emails people send to our own addresses (such as support@wesign.now), and job applications forwarded to them, are kept in our email inboxes.
If a workspace connects its own systems (webhooks, API, integrations), data goes to the destinations it configures; that is the workspace’s responsibility.
6.Shared documents (Present)
In short:A workspace that shares a document can see who opened it and which pages they read. It is responsible for that data.
- When a workspace shares a document through a Present link, it may ask viewers for their name, email address, phone number or other details before they can open it, or limit access to people it has approved (access requests and confirmation emails).
- For each viewer we record which pages were viewed and for how long, when, the referring page and campaign, browser, country and a shortened IP address. A cookie on the viewer’s device (30 days) keeps the access and links later visits to the same viewer.
- The workspace sees this, can receive alerts when a document is opened and weekly summaries, and may add viewers to its contacts.
- The workspace is the controller; we process this data on its behalf. Please send requests about it to the workspace that shared the document.
7.Inquiries, applications and support
In short:What you send us through a form is used to answer you, and nothing else.
- Sales, demo and enterprise inquiries, custom offers and non-profit applications — your details, your message, the campaign that brought you and your approximate country (from your IP address), to answer you and prepare an offer.
- The chat on our website and in the app sends what you enter in it (or, when you are signed in, your account’s name, email address and workspace), with the page you wrote from, the same way and for the same purpose, straight to our own team: no third-party chat service is involved.
- Support and bug reports — messages you send us through the app or the signing page, with the page address, browser and app version and, from a signing page, the document it concerns, so we can help and fix problems.
- Job applications — if you apply through our careers page, we receive your name, email address, the role, your links, your message and your CV by email, and use them only for the application process.
8.Referrals
In short:A workspace that refers a new customer can be credited for it. It sees only its own contacts, never your account details.
- Invitations. A member can invite up to 25 people at a time by email. We send each one invitation in the member’s name, with the member’s or its workspace’s reply-to address, and keep the address so the invitation is not sent twice and the referral can be credited.
- Referral link. If you follow a referral link, a cookie (
ls_ref, 60 days) remembers the code so that the workspace you open can be credited to the referrer. - Attribution. When the referral programme is active for a referring workspace, a new workspace is credited to it if you followed its link, typed its referral code, used its discount code at checkout, or — when none of these applies — if, in the 12 months before you open a workspace or first subscribe, you signed or received as an observer a document sent by that workspace. For this last rule we compare your email address with the signer and observer records of the referring workspaces. Only one workspace is credited.
- What the referrer sees. A list of the people it has itself exchanged documents with, as it recorded them (name, company, number of documents, last exchange, whether it invited them), with a note when one of them joined through it and whether that earns it a reward. It also sees how many of its contacts have no account with us, as a total only and never when the number is small. Beyond that, it never sees your plan, your account details or anything about workspaces it did not refer.
- Rewards. To credit rewards and prevent abuse, we record the referred workspace’s first payment and compare a one-way hash of the payment card fingerprint on both sides of a referral.
9.Importing from Google Drive
In short:Only when you ask: the one file you pick in Google Drive, used once to make your template, document or contacts import. We keep no access to your Drive.
When you choose “Google Drive” as a source in wesign.now, Google asks you to let us see the files you pick (Google’s drive.file permission). We never see the rest of your Drive.
- What we read. The one file you picked: its name, type, size, the time it was last changed, and its content. A Google Doc comes to us as a PDF or as HTML, and a Google Sheet picked for a contacts import as CSV, each produced by Google; a PDF, Word or CSV file comes as stored.
- What we do with it. We turn it into the template or document you asked for, in your workspace, exactly as if you had uploaded the file. A sheet or CSV file picked for a contacts import is shown to you as a preview first; only the contacts you confirm are saved. For a template made from a Google Doc we also keep the doc’s ID, name and last-changed time, so the template can show where it came from.
- What we do not keep. The access Google gives us is a short-lived token. We use it for that one import and do not store it; we hold no lasting access to your Google account. You can remove wesign.now’s access at any time at myaccount.google.com/permissions.
- Limited Use. wesign.now’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, do not sell it, do not use it to train AI models, and do not let people read it except with your permission, for security reasons, or where the law requires.
The file you import is then stored and processed like any other upload, as described in the sections above.
10.AI and automated decisions
In short:AI helps only in the template editor and with non-profit applications — never with your documents or signers.
- The AI assistant and translation in the template editor run only when you start them. They receive the text you give them or the template to translate.
- Non-profit applications for our NGO plan are checked automatically with AI using the details the organisation submits, including the contact email. A clear case can be approved or declined automatically; unclear cases are always decided by a person.
- Automated decisions. If your application was declined automatically, you can ask for a person to review the decision and state your point of view by writing to support@wesign.now. No other decision with legal or similarly significant effect on you is made automatically.
- Uploaded documents, signed documents, shared documents and signer data are never sent to an AI service.
- We use a European AI provider wherever one meets our needs. For these features none does today, so we use Anthropic (a US company), with processing in 🇪🇺 Europe, under terms that do not allow it to train its models on this data. We will update this policy when that changes.
12.How long we keep data
In short:Documents stay until the workspace deletes them; evidence and most records stay as long as the workspace exists.
| Signing links | Expire after the period the sender sets: 21 days by default in the app (1–90 days); through the API 14 days by default (up to 90 days, or 180 days for documents created from templates) |
|---|---|
| Documents | Until the workspace deletes them. A workspace can switch on automatic deletion (Settings → Signing; off by default): it deletes the signed PDF after the set period, and the document of an expired or declined request. The original upload, page images and the audit trail are kept until the document or the workspace is deleted |
| Audit trail and signer records | As long as the workspace exists, also after the files are deleted — they are the evidence of the signature |
| Shared documents (Present) | Viewer records until the workspace deletes the shared document; access confirmation links 7 days after they expire; declined access requests 180 days |
| API log | 30 days |
| Webhook deliveries, email delivery reports, SMS counts | As long as the workspace (or, for webhook deliveries, the webhook) exists; on request we delete them earlier |
| Account data and campaign attribution | As long as the account exists. To close your account, write to support@wesign.now; we then delete your account data, except records we must keep by law or that are evidence of a signature |
| Inquiries, offers, support tickets and bug reports | As long as needed to handle them and any contract that follows; on request we delete them earlier |
| Job applications | For the application process; on request we delete them earlier |
| Referral invitations and attributions | As long as the inviting or referring workspace exists; on request we delete an invitation earlier |
| Newsletter consent record | As long as you are subscribed, and afterwards as long as we need it to prove the consent and respect your unsubscription |
| Invoices and accounting records | 10 years, as Swiss law requires |
| Error monitoring and hosting logs | For a limited period set by the provider, then deleted automatically |
13.Security
In short:Encrypted in transit and at rest, shortened IP addresses in our own logs, access only where needed.
Data is encrypted in transit (TLS), and every file is encrypted at rest by our storage providers (AES-256). Signed PDFs and audit certificates, PDFs sent through our API or a workspace’s request form, PDFs made from images, and the copies our servers make of an upload (converted, repaired or compressed) are additionally encrypted with our own key (AES-256-GCM) before they are stored. Files uploaded directly from your browser, Google Drive imports, documents created from a template until they are signed, template files, shared-document (Present) copies and page images have the storage provider’s encryption only; page images are kept at unguessable addresses.
In the audit trail and in the logs we keep ourselves (API log, Present access logs), IP addresses are stored in shortened form (the last part removed). Our hosting, sign-in and error-monitoring providers keep full IP addresses in their technical logs for a limited period, for security and troubleshooting. Access within our team is limited to what a task requires. Details are in our security documentation.
14.Your rights
In short:You can ask what we hold about you, and have it corrected or deleted. Email us.
You have the right to access your personal data, to have it corrected or deleted, to restrict or object to processing, to receive it in a portable format, to withdraw a consent at any time, and to have an automated decision reviewed by a person. Write to support@wesign.now; we answer within 30 days. We may ask you to confirm your identity.
You can also complain to a supervisory authority: in Switzerland the Federal Data Protection and Information Commissioner (FDPIC), in the EU the authority of your country.
15.If you received a document to sign
In short:The organisation that sent you the document is responsible for it and for checking who you are. Contact them first; we help.
If you received a document to sign, the sender’s workspace decides what is done with the document and your data. Please send requests about it to the sender. If you contact us, we forward your request to them and support them in answering it. A signed document and its audit trail are evidence for everyone who signed it, so they may need to be kept even if you ask for deletion.
The audit trail records how you were reached and what happened through your link: the email address and phone number recorded for you, when you opened and signed, a shortened IP address and your browser. It shows that someone used your link (and, if one was asked for, your SMS code), not who that person was; we do not check identity documents. Anyone who has your link and code can sign in your name, so keep your inbox and phone secure, do not forward the link, and tell the sender at once if a document shows a signature you did not make (see our terms).
If the sender takes part in our referral programme and you open your own workspace with us or first subscribe within 12 months of signing or observing one of its documents, we use that record to credit the sender for referring you, and the sender sees that you joined through it (see section 8).
If you tick the box to receive our news at the end of signing, we use your email address for our newsletter on the basis of that consent, and keep a record of it (time, where you gave it, the wording, a shortened IP address). You can unsubscribe in every email.
16.Changes to this policy
In short:We update this policy when our processing changes and show the date at the top.
We update this policy when we change how we process data or which providers we use. The date at the top shows the current version. We inform workspace owners by email about important changes.