E-Signature
Skribble
UK / wider Europe Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Skribble AG · www.skribble.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Skribble at a glance
- Vendor
- Skribble AG
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Default not stated; pages mention Germany and Switzerland source, captured 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Starting price
- “Starter Für einzelne Signaturen und den Einstieg – rechtssicher, ganz ohne Abo. Ideal für Einzelunternehmen. ab € 0 ohne MwSt., 1 Nutzer” (vendor’s words) source, captured 13 Oct 2026
- Panel verdict
- The AI panel rates Skribble 2/5, the mean of 6 judges. Skribble is an e-signature service from Skribble AG of Zurich, with Skribble Deutschland GmbH, offering simple, advanced and qualified signatures under ZertES and eIDAS. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Skribble is an e-signature service from Skribble AG of Zurich, with Skribble Deutschland GmbH, offering simple, advanced and qualified signatures under ZertES and eIDAS. The bench scored it strongest on integration and API, at 5-6: an open REST API with immediately testable demo keys covers all three signature levels end to end, alongside connectors for Microsoft 365, Google Drive, SAP and Salesforce. Its weakest area is pricing transparency, scored at 2: the captured pages show the plan ladder — Individual, Team and Pro, one user on the entry plan, up to 20 on Team and Pro — but no price figures, and qualified signatures, seals, identification packages and the switching fee are each quoted separately. Evidence and retention scores 2-3, with no public information on an audit trail, completion certificate or retention periods. Sovereignty, at 3-4, is held back by unnamed identification partners and an unnamed qualified trust service provider, and the captured pages give different figures for hosting — Switzerland with ISO 27001, Germany, or either.
Speaks for it
- Open REST API with immediately testable demo keys supports all three signature standards end to end.
- Prebuilt connectors for Microsoft 365, Google Drive, SAP and Salesforce, with signing directly from those systems.
- SES, AES and QES are each labelled with their identification method and an example document, with QES under both eIDAS and ZertES.
- External signers sign in the browser with no login and no app, including a QR-code entry.
- Simple signatures are unlimited in every plan, with a no-subscription pay-per-signature option and a free trial that requires no credit card.
Held against it
- No price figures appear on the captured pages, so the cost of a qualified signature cannot be computed.
- We found no public information on an audit trail, completion certificate, timestamp source or retention periods.
- The qualified trust service provider behind the signatures and the identification partner are unnamed on the captured pages.
- The captured pages give different figures for hosting: Switzerland with ISO 27001, Germany, or either country.
- We found no public information on a subprocessor list, a data processing agreement or ownership.
Best for
- You need to embed signing in your own application or sign from inside Microsoft 365, Google Drive, SAP or Salesforce.
- Your signers are external parties who should sign in a browser without creating an account.
- You need qualified electronic signatures under both Swiss and EU law from one product.
- You send mostly simple electronic signatures and want unlimited volume pooled across seats.
Avoid if
- You must compute your total signing cost from published prices before committing.
- You need documented long-term evidence — an audit trail, completion certificate and retention periods — for records that must be provable years later.
- You need a named trust service chain and a subprocessor list for compliance sign-off.
- You need API or integration access on the entry plan, where it is listed as not available.
The scores
| Criterion | Panel median |
|---|---|
| eIDAS levels & trust services | 2.5 of 5 |
| Signer identification | 2 of 5 |
| Signing workflow & signer experience | 2.5 of 5 |
| Evidence, validation & retention | 1 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 1 of 5 |
eIDAS levels & trust services
Show reasoningHide reasoning
How this is scored
Which signature levels the platform offers — simple, advanced, qualified, and qualified seals — through which qualified trust service provider on the EU Trust List, for which countries and legal regimes (eIDAS, ZertES), and on which plans.
0 — No signature level named; the platform calls its signature "legally binding" without saying which kind it is.
3 — Simple signatures by default with "advanced" or "qualified" mentioned as available, but no trust service provider named and no statement on which plan or country offers which level.
5 — SES, AdES and QES offered and labelled in the product, the qualified trust service provider named, and which documents need which level explained for at least Germany or the EU.
8 — Every level documented with the plans and countries it is available in, the QTSP's entry on the EU Trust List linked, QES under eIDAS (and ZertES where relevant) stated, qualified electronic seals for company documents, and the signature level printed in the signed document and audit trail.
10 — Levels are an explicit product decision: the provider is or contracts a named QTSP with its conformity assessment published, level selection per document type or template, remote QES without a separate account, EUDI wallet support stated with a date, and the legal effect per level documented for the main EU markets.
The Legal Counsel
All three levels are labelled with their method and an example document, the pages state QES under both eIDAS and ZertES with a BGB written-form claim, and even seals appear as a purchasable extra. What I cannot sign off on is the trust chain: the captured pages name no qualified trust service provider, referring only to a signature created by a certified service or trust service provider plus a Swisscom partnership mention, and we found no link to the EU Trust List or a country-by-plan mapping of levels. 2 5 6 8 14
The HR Operations Lead
Simple, advanced and qualified signatures are each labelled with their identification method and a document example, valid under eIDAS and ZertES with the German written-form requirement named, and every plan carries all three standards — which covers my fixed-term contracts on paper. However, I found no public naming of the qualified trust service provider behind the qualified signature and no link to the EU Trust List, and seals appear only as a purchasable extra in the terms rather than a documented product level. 2 5 6 8 14
The Revenue Operations Lead
Simple, advanced and qualified signatures are each labelled with their authentication method and a worked example document, QES is unlockable under both eIDAS and ZertES, and even the no-subscription option carries all three standards. The trust service provider behind the qualified signature is never named though — the terms refer only to a certified service or trust service provider generically, and the frequently stated Swisscom partnership is never stated as the trust service — and we found no public information on an EU Trust List entry or the signature level being printed in the signed document. 5 6 8 9
The Integration Engineer
All three levels are labelled in the product with a document example each and a downloadable guide on which standard fits which document, and both eIDAS and ZertES are stated, with identification selectable per legal regime and every plan including all three standards. But we found no public information naming the qualified trust service provider behind the signatures — a Swisscom partnership is mentioned on several pages without any statement of what it covers — nor a Trust List reference, and seals surface only as a separately billed item in the terms. 2 5 6 8 9 12
The Data Protection Officer
SES, AES and QES are each labelled with an identification method and a document example, seals are purchasable, and identification can run under ZertES, eIDAS or both, with QES offered for Swiss and EU law. But the terms say only that the qualified signature is created by "einen zertifizierten Service oder Vertrauensdiensteanbieter" and identification is performed by partners — no trust service provider is named on the captured pages, and we found no public information on an EU Trust List entry or on the signature level printed in the signed document and its evidence. 2 5 6 8 9
The Skeptic
All three levels are labelled with their method and a worked example, QES is stated for both eIDAS and ZertES, seals can be purchased on top, and every plan carries all three standards. But the qualified trust service that actually creates the QES is never named — the terms route it to "a certified service or trust service provider" and the privacy policy to unnamed "partners" — leaving only a "Swisscom partnership" marketing line, and we found no public link to a trust-list entry. 5 8 9 6 15
Signer identification
Show reasoningHide reasoning
How this is scored
How the signer is identified for each level: email and SMS codes, video ident, eID card (Online-Ausweis), bank ident or EUDI wallet — who performs it, in which countries it works, and what happens to the ID data afterwards.
0 — Email link only; no statement on how signers are authenticated.
3 — Email plus SMS or access code, with "ID verification" mentioned as an add-on but no methods, provider or countries named.
5 — Identification methods for AdES and QES listed by name (for example video ident, eID, bank ident), the identification provider named, and the countries or ID documents they accept stated.
8 — Methods documented per level and country, automated and agent-based ident distinguished, reuse of an identification for later signatures explained, retention and deletion of ID data stated, and the ident provider listed as subprocessor.
10 — Identification is transparent end to end: every method with its countries, assurance level and failure rate or completion guidance, EUDI wallet and national eID supported, ID data minimisation and retention committed, and the signer-facing privacy notice published.
The Legal Counsel
Methods are published per level — email for the simple signature, mobile number for advanced, and ID scan with selfie video, live video call, on-site visits or the Swiss eID for qualified — with identifications purchasable under ZertES, eIDAS or both. The identification partner itself stays unnamed outside one customer case, and we found no public information on accepted ID documents and countries, on reuse of an identification, or on retention and deletion of ID data. 3 5 6 7 8 9
The HR Operations Lead
For the qualified level the methods are described by name — video identification with trained partner staff, a self-service ID scan with a selfie video, and on-site visits — with a choice of Swiss or EU law for the identification, and a one-time check unlocking the qualified level for later signatures, which suits repeat hiring. But the identification partner is never named, and I found no public information on which countries or ID documents are accepted or on retention and deletion of ID data, which is exactly what I need to know when applicants hold unpredictable passports. 3 6 8 9 13
The Revenue Operations Lead
Methods are mapped to each level by name — email access for simple, mobile number for advanced, and ID scan plus selfie video, live video ident with staff, self-identification or an on-site visit for qualified — and the buyer chooses identification under Swiss law, EU law or both. But the identification provider is only ever "our partner", and we found no public information on accepted ID documents and countries, or on retention and deletion of the ID data afterwards. 3 5 6 8 9
The Integration Engineer
Methods are named per level — email for the simple signature, mobile number for the advanced one, and for the qualified one a self-service ID scan with selfie video, a staff-guided live video call or an in-person visit — with automated and agent-guided paths distinguished and a one-time identification that unlocks QES in the signer's profile for later use. The identification partner, though, is only ever referred to as our partners, and we found no public information on accepted ID documents, on retention or deletion of ID data, or on the swiyu eID, which appears only as a question heading without a captured answer. 3 5 6 8 13
The Data Protection Officer
Methods are listed per level — email address for SES, mobile number for AES, and for QES an ID scan with selfie video, a guided live video call, on-site identification or the swiyu eID — with Swiss or EU law selectable and an identification reusable by unlocking QES in the profile. The identification provider stays "unsere Partner" without a name, and we found no public information on which ID documents are accepted, on retention and deletion of ID data, or on the identification provider appearing as a subprocessor. 3 6 8 9 13
The Skeptic
Methods are named per level — email for the simple signature, mobile number with SMS for advanced, ID scan plus selfie video, a staffed live video call or an on-site visit for QES — with a ZertES/eIDAS framework choice and identification packages sold per scope. We found no public information naming the identification partner, the countries or ID documents it accepts, or any retention or deletion commitment for ID data beyond self-service account deletion. 5 8 6 3 9 13
Signing workflow & signer experience
Show reasoningHide reasoning
How this is scored
Getting a document out and back signed: templates and form fields, signing order and roles, bulk sending, reminders and delegation, signing without an account or app, mobile signing, and accessibility for signers.
0 — Single-recipient signing of an uploaded PDF; no templates, order or reminders.
3 — Multiple signers and basic templates, but no signing order, no bulk send, and signers must create an account.
5 — Templates with field placement, sequential and parallel signing order, automatic reminders and expiry, signing without an account on mobile, and a status overview for the sender.
8 — Roles and conditional fields, bulk sending, delegation and substitute signers, team and approval workflows, branded signer experience, signer languages listed, and signer accessibility addressed.
10 — The workflow is complete and documented: web forms and self-service signing links, mixed signature levels within one process, in-person and remote signing, a published accessibility conformance statement, and team administration with shared templates and audit of sender actions.
The Legal Counsel
Signing order, automatic reminders at admin-chosen intervals plus manual reminders open to every customer, browser signing without account or app including QR entry, and continuous status tracking are all documented. We found no public information on templates and field placement, bulk sending beyond a claimed use case, delegation or substitute signers, expiry, and signer accessibility. 2 7 10 11 14
The HR Operations Lead
Signers complete everything in the browser with no login, no app and even a QR-code entry — precisely the ten-minute phone experience I want — and signing order, automatic reminders with configurable frequency, manual reminders for every customer, status tracking and branding are documented. I found no public information on templates, field placement or bulk sending; bulk processes appear only as a stated use case, which leaves my two hundred contracts a year without a documented production line. 2 7 11 14 15
The Revenue Operations Lead
This is close to what I run deals on: signing order is settable, automatic reminders fire every 3 days, weekly or every 2 weeks once an admin switches them on (manual reminders for everyone else), signers sign in the browser with no login and no app, invitations arrive by email or link with a QR option, and the sender tracks status — with branded sending and four signer languages on top. We found no public information on templates, bulk sending beyond a use-case mention, delegation or substitute signers, or signer accessibility. 2 4 7 10 11 14 15
The Integration Engineer
Signing order, browser signing with no login and no app, email or link delivery including a QR option, and automatic reminders with admin-set intervals are all evidenced, and the API exposes signer order and status tracking. We found no public information on templates with field placement, expiry, delegation or signer accessibility, and bulk sending appears only as a marketed use case rather than a documented feature. 2 7 11 14 15
The Data Protection Officer
Signing order, signing in the browser without login or app, QR-code access, invitations by email or link, and manual plus admin-activated automatic reminders with configurable intervals are documented, with external signers needing no account and status trackable via the API. We found no public information on templates and field placement, expiry, bulk sending, delegation or signer accessibility. 2 7 10 11 14
The Skeptic
Signing order, reminders (manual for every customer, automatic once an admin enables them, at intervals from every 3 days to every 2 weeks), browser signing without login or app, and QR-code opening are all documented, in four signer languages. We found no public information on templates, field placement, document expiry, bulk sending, delegation or signer accessibility. 2 7 10 11 14
Evidence, validation & retention
Show reasoningHide reasoning
How this is scored
What proves a signature years later: the audit trail and certificate of completion, qualified timestamps, long-term validation (PAdES-LTV), validation reports, and how long signed documents and evidence are kept — and whether they can leave the platform.
0 — A signed PDF and nothing else; no audit trail, no statement on storage or deletion.
3 — An audit trail or completion certificate exists, but its contents, the timestamp source and the retention period are unstated.
5 — Audit trail with signer events, IP addresses and authentication method embedded in or attached to the signed PDF, timestamps applied, documents downloadable, and the retention period stated.
8 — PAdES signatures with long-term validation, qualified timestamps from a named provider, a validation tool or report, configurable retention and automatic deletion, and bulk export of documents with their evidence.
10 — Evidence outlives the subscription: LTV and archive timestamps documented, validation verifiable with independent tools such as the EU DSS validator, export to a DMS or archive with evidence intact, and post-termination access and deletion committed in the terms.
The Legal Counsel
For a contract disputed in eight years the pages offer an E-Signature validator tool, AATL conformity on all plans, and validation and conversion services sold on an annual fee. We found no public information on an audit trail, a certificate of completion, qualified timestamps, long-term validation, or how long signed documents and their evidence are kept. 2 5 12
The HR Operations Lead
Signatures are described as conforming to the Adobe Approved Trust List in every plan, a public signature validator tool exists, and validation services can be bought on an annual fee, so some evidentiary tooling is real. But I found no public information on an audit trail or its contents, the timestamp source, long-term validation, or how long documents and evidence are retained — a serious gap for employment records that must be provable years later. 2 5 12
The Revenue Operations Lead
There is evidence tooling — signatures stated as AATL-conform on all plans, a public E-Signature-Validator and paid validation and conversion services — plus self-service account deletion. But we found no public information on an audit trail or completion certificate, its contents, the timestamp source, or how long signed documents and their evidence are kept, so I cannot tell procurement what proves this signature in five years. 2 3 5 12
The Integration Engineer
What the pages show is an E-Signature-Validator tool, purchasable validation and conversion services on an annual fee, and AATL conformity on all plans — useful, but thin for archiving. We found no public information on an audit trail or completion certificate and its contents, the timestamp source, long-term validation, retention periods, or export of documents together with their evidence, which is exactly what I need to archive signed contracts in our DMS. 2 5 12
The Data Protection Officer
AATL conformity in every plan, an E-Signature-Validator, and validation and conversion services at a contract-fixed annual fee are the evidence-related items we found; we found no public information describing an audit trail or certificate of completion, timestamps, long-term validation, retention periods, or export of documents together with their evidence. The privacy policy places the infrastructure in ISO 27001-certified Swiss data centres, but the captured pages give different figures for hosting — Germany, Switzerland, or either one. 2 3 5 12 15
The Skeptic
What the pages do show is AATL conformity on all plans, a public signature validator tool, and self-service account deletion. We found no public information on an audit trail, a completion certificate, the timestamp source, PAdES long-term validation, or how long signed documents and their evidence are kept. 2 12 3 5
Integrations & API
Show reasoningHide reasoning
How this is scored
Signing from inside the systems where contracts are made: a documented API with webhooks and a sandbox, embedded signing, and connectors for Microsoft 365, CRM, HR, DMS and ERP systems.
0 — No API and no integrations; everything happens in the vendor's web app.
3 — A few named integrations or a Zapier connector, and an API mentioned without public documentation.
5 — A documented REST API with webhooks and a sandbox, plus connectors for Microsoft 365 or Google Workspace and at least one CRM or HR system named.
8 — Embedded signing in the customer's own application, API access to every signature level, versioned API with rate limits published, SDKs, and connectors for named DMS, ERP or HR systems with their scope.
10 — Integration is a product: white-label and embedded flows documented, API parity with the web app, a status page with incident history, deprecation policy, and a marketplace of integrations with stated maintainers.
The Legal Counsel
An open REST API with published documentation and instantly usable demo keys covers all three signature standards, and signing runs inside Microsoft 365, Google Drive, SAP and Salesforce, with API access beginning on the higher plans. We found no public information on webhooks, embedded signing in the customer's own application, SDKs, rate limits or API versioning. 2 8 14 15
The HR Operations Lead
There is a documented open REST API with immediately testable demo keys that supports all three signature standards, named connectors for Microsoft 365, Google Drive, SAP and Salesforce, clear plan availability for API and integrations, and a status page. I found no public information on webhooks, embedded signing or SDKs, so it sits at a solid documented-API level rather than a full integration product. 2 4 14 15
The Revenue Operations Lead
Signing where the deal lives is evidenced: a documented open REST API with immediately testable demo keys, connectors for Microsoft 365, Google Drive, SAP and Salesforce, all three signature standards reachable through the API, signing directly from integrated solutions, and a CRM contract-closing use case. We found no public information on webhooks, embedded signing in our own application, SDKs or published rate limits, and a status page is linked with no stated incident history. 4 8 14 15
The Integration Engineer
An open, documented REST API with immediately testable demo keys covers all three signature levels end to end — upload, signer order, initiation, status tracking — and prebuilt connectors exist for Microsoft 365, Google Drive, SAP and Salesforce, with a status page and SSO besides. But we found no public information on webhooks, API versioning, rate limits or SDKs, embedded signing in our own portal is only implied by the API-for-your-own-programs framing, and API access sits above the entry plan. 2 4 8 14 15
The Data Protection Officer
An open REST API with public documentation, a demo key usable immediately, API support for all three signature standards, and connectors for Microsoft 365, Google Drive, SAP and Salesforce are documented, and a status page exists. We found no public information on webhooks, SDKs, rate limits or embedded signing in the customer's own application. 4 14 15
The Skeptic
A documented open REST API with immediately testable demo keys, all three signature levels via API, a workflow of upload, signer order and status tracking, connectors for Microsoft 365, Google Drive, SAP and Salesforce, and a status page. We found no public information on webhooks, embedded signing, SDKs, rate limits or API pricing, and API and integration access begin only at the higher plans. 14 15 8 4 2
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity, the trust service provider and their owners are, where documents, audit trails and ID data are stored and processed, and who the subprocessors are. Independently sourced by the sovereignty pipeline.
0 — Non-EU contracting entity, no statement on where documents and signer data are stored, and subprocessors unnamed.
3 — An EU entity contracts, but documents or signer data are processed outside the EU by default without an explained safeguard, or the subprocessor list is absent.
5 — EU contracting entity and EU data storage stated, with a DPA, but the hosting, identification or trust service chain is non-EU-controlled without a stated safeguard.
8 — EU entity, documents, audit trails and ID data stored in named EU data centres, an EU qualified trust service provider, subprocessor list with locations published, and certifications (ISO 27001, ETSI conformity) published.
10 — Sovereign end to end and evidenced: European ownership, EU entity and EU QTSP, every processing location and subprocessor European, customer-selectable data residency, and certifications with their scope published.
The Legal Counsel
The terms contract German and other customers with the German entity and Swiss customers with the Swiss entity, and hosting is stated in ISO 27001-certified data centres in Germany or Switzerland with support drawn only from those two countries. We found no public information on ownership, the subprocessor list and their locations, a data processing agreement, or any choice of data residency for documents and identification data. 1 3 5 15
The HR Operations Lead
The captured pages give different figures for hosting — the privacy policy states Swiss data centres with ISO 27001, the homepage states hosting in Germany, and the API page states Germany or Switzerland — and the terms route Swiss customers to Skribble Schweiz while everyone else contracts with Skribble Deutschland. I found no public information on ownership, the subprocessor list, or a data processing agreement, so the trust and identification chain is not traceable from these pages. 1 3 5 15
The Revenue Operations Lead
The terms route contracting to Skribble Schweiz or Skribble Deutschland depending on seat and booking URL, and hosting is stated in certified data centres in Germany and Switzerland with ISO 27001 on the Swiss side — though the captured pages give different figures for the hosting country. We found no public information on ownership, the trust service and identification chain, or a subprocessor list with locations, so the chain behind the signature stays dark. 1 3 5 15
The Integration Engineer
German customers contract with the German entity and Swiss customers with the Swiss one, hosting is stated in certified data centres in Germany or Switzerland, and ISO 27001 is claimed for the Swiss centres. We found no public information on ownership, a subprocessor list with locations, the trust service chain, or a data processing agreement, and identification runs through unnamed partners. 1 3 5 15
The Data Protection Officer
The terms route contracts to Skribble Schweiz or Skribble Deutschland depending on the booking URL, and the privacy policy states ISO 27001-certified Swiss data centres — but the captured pages give different figures for hosting, naming Germany, Switzerland, and either one on different pages. Identification partners and the trust service provider appear without names, and we found no public information on a subprocessor list, a data processing agreement or ownership, so the chain carrying signers' ID data stays unverifiable. 1 3 5 15
The Skeptic
The contract goes to Skribble Schweiz or Skribble Deutschland depending on the customer's seat and booking URL, and hosting is stated as certified data centres in Switzerland or Germany with ISO 27001 for the Swiss ones — though the captured pages give different figures for the hosting region. We found no public information on ownership, a subprocessor list, a data processing agreement, or the identity of the unnamed partners performing identification and the qualified signatures. 5 3 1 15
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the cost of their signing volume from public pages alone — plan prices, envelope or document limits, the per-signature price of AdES and QES, identification fees, API pricing and overage.
0 — No public prices at all; every plan is a sales conversation.
3 — Plan prices published, but envelope limits, QES and identification fees are unstated — the cost of a qualified signature is unknowable.
5 — Plans with envelope or document limits priced, but at least one commonly incurred cost (per-QES fee, video ident, API access, overage) is missing or "on request".
8 — Every plan and limit priced publicly, AdES and QES priced per signature, identification fees and overage stated, API pricing published, and contract term and notice period given.
10 — Complete cost computability: the cost of a given monthly volume per signature level derivable from public pages, volume tiers published, and every add-on and price-change term on a public page.
The Legal Counsel
The plan mechanics are public — Individual, Team and Pro, unlimited simple signatures in every plan, signatures pooled across seats — but QES, seals, identification packages and validation services are all separately owed or quoted individually on request. We found no public figures for plan prices, per-signature QES or identification fees, or API access, so the cost of a signing volume cannot be computed from the captured pages; only a fourteen-day termination right against price increases is stated. 2 5 9
The HR Operations Lead
No monetary figure appears on the captured pages: plans and user limits are shown, simple signatures are unlimited in every plan and Starter is pay-per-signature, but qualified signatures, seals and identification packages are all separately owed and identifications are bought by contacting the vendor with the quantity and legal framework. I therefore cannot compute the cost of a single qualified employment signature before sending it, which is the number I most need; only the free trial without credit card and the fourteen-day termination right on price increases are concretely stated. 2 5 9 15
The Revenue Operations Lead
The plan architecture is public — Individual, Team and Pro with up to 20 users, a no-subscription pay-per-signature option, unlimited simple signatures in all plans — and the published terms give a 14-day termination right on price increases. But the captured pricing page shows structure and user limits with no price figures, and we found no public information on per-signature costs for advanced or qualified signatures, identification package fees (sold by contacting sales), or the separately quoted switching fee, so no monthly volume cost is computable. 2 5 9
The Integration Engineer
The plan ladder, user limits, unlimited simple signatures, a pay-per-signature entry option and purchasable advanced and qualified signature contingents are public, as is a 14-day termination right after notice of a price increase. But we found no public price figures at all, and qualified signatures, identification packages, validation services and the switching fee are each individually quoted or set in the customer contract — no volume cost is computable from public pages. 2 5 9
The Data Protection Officer
The captured pricing page shows plan names, user limits, unlimited simple signatures in every plan and pay-per-signature on the entry plan, but no price figures; FES and QES are billed individually "separat geschuldet", identification packages are bought by contacting Skribble, and validation services and the switching fee are each set individually. The cost of a qualified signature therefore cannot be computed from the captured pages. 2 5 9
The Skeptic
Plan names, user limits and unlimited simple signatures in every plan are stated, with a pay-per-signature no-subscription tier, signature pooling across seats, and a free trial without a credit card. We found no public price figures for any plan, the per-signature cost of advanced and qualified signatures, identification packages (quoted on contact), the API, validation services or the separately quoted switch fee — so the cost of a qualified signature cannot be computed from public pages. 2 5 9 15
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about Skribble
Is Skribble European?
Yes, though not from the EU. whats-best.ai classifies Skribble as UK / wider Europe.
Where does Skribble store data?
The default storage location for customer data is not stated on the vendor’s pages as of 13 Oct 2026. The vendor’s pages mention Germany and Switzerland as hosting locations, per the vendor’s page captured 13 Oct 2026.
Does Skribble have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Skribble?
As of 15 Oct 2026, the panel rates Penneo (2.5/5), Youtrust (Yousign) (2.5/5) and MOXIS (2.5/5) highest among the other 14 E-Signature products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Penneo (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Skribble alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 19 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 14 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 13 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.skribble.com Checked 13 Oct 2026 Details →
- 2 Pricing page www.skribble.com Checked 13 Oct 2026 Details →
- 3 Privacy policy www.skribble.com Checked 13 Oct 2026 Details →
- 4 Legal notice www.skribble.com Checked 13 Oct 2026 Details →
- 5 Terms of service www.skribble.com Checked 13 Oct 2026 Details →
- 6 EIDAS levels & trust services — found from sitemap www.skribble.com Checked 13 Oct 2026 Details →
- 7 EIDAS levels & trust services — found from sitemap www.skribble.com Checked 13 Oct 2026 Details →
- 8 Signer identification — found from sitemap www.skribble.com Checked 13 Oct 2026 Details →
- 9 Signer identification — found from sitemap help.skribble.com Checked 13 Oct 2026 Details →
- 10 Signing workflow & signer experience — found from sitemap help.skribble.com Checked 13 Oct 2026 Details →
- 11 Signing workflow & signer experience — found from sitemap help.skribble.com Checked 13 Oct 2026 Details →
- 12 Evidence, validation & retention — found from sitemap www.skribble.com Checked 13 Oct 2026 Details →
- 13 Evidence, validation & retention — found from sitemap help.skribble.com Checked 13 Oct 2026 Details →
- 14 Integrations & API — found from sitemap www.skribble.com Checked 13 Oct 2026 Details →
- 15 Integrations & API — found from sitemap www.skribble.com Checked 13 Oct 2026 Details →