Skip to content
inSigner

Workflow

overview Product overview From PDF preparation to final proof arrow_forward route Prepare & route Fields, recipients, roles, and signing order arrow_forward timeline Track every step Opens, signatures, reminders, and completion arrow_forward

Scale

content_copy Templates & campaigns Reuse repeatable signing workflows arrow_forward groups Teams & RBAC Organizations, permissions, folders, and tags arrow_forward workspaces Use cases HR, legal, sales, real estate, and vendors arrow_forward

Extend

api Developer platform REST API v1, keys, scopes, and webhooks arrow_forward hub Integrations Connect signing to the systems around it arrow_forward qr_code_2 Public verification Check the completed agreement record arrow_forward

Essentials

verified_user Trust Center Security, privacy, providers, and review material arrow_forward shield Evidence & controls Review signing evidence and security controls arrow_forward workspace_premium PAdES lifecycle B-B, B-T, and the path to B-LTA arrow_forward verified Public verification Validate the sealed record without an account arrow_forward

Regional context

🇺🇸 United States ESIGN Act · UETA arrow_forward 🇪🇺 European Union eIDAS · eIDAS 2.0 arrow_forward 🇬🇧 United Kingdom UK eIDAS context arrow_forward

Regional context

🇧🇷 Brazil MP 2.200-2 · ICP-Brasil context arrow_forward 🇲🇽 Mexico Commercial Code · NOM-151 context arrow_forward 🇨🇴 Colombia Law 527 context arrow_forward

Country guidance is educational, not legal advice.

Developers Pricing

Learn

edit_document Product See the complete signing workflow arrow_forward security Security Evidence, controls, and regional context arrow_forward sell Pricing Unlimited, Developer, and Enterprise arrow_forward

Build & operate

terminal Developers API building blocks and webhook events arrow_forward menu_book API documentation Guides, endpoints, and examples arrow_forward monitor_heart Service status Live platform availability arrow_forward

Company & access

info About inSigner Why evidence belongs in the product arrow_forward contact_support Contact sales Contracts, SLA, deployment, and review arrow_forward verified_user Verify a document Open the public verification service arrow_forward
Log in Get started
  • EN English
  • ES Español Soon
  • PT Português Soon
  • FR Français Soon
  • DE Deutsch Soon
  • IT Italiano Soon
Log in Get started
Home / Legal / Acceptable Use Policy

Legal center

Acceptable Use Policy

Rules that protect signers, customers, documents, identities, communications, and the inSigner platform from abuse.

calendar_today Last updated August 18, 2026 business Nubesti LLC

Company

Nubesti LLC United States hi@insigner.co

On this page

  1. 1. Purpose
  2. 2. Fraud and impersonation
  3. 3. Illegal or harmful content
  4. 4. Communications
  5. 5. Platform security
  6. 6. Privacy and identity data
  7. 7. API and automation
  8. 8. Enforcement
  9. 9. Reporting abuse
On this page expand_more
  1. 1. Purpose
  2. 2. Fraud and impersonation
  3. 3. Illegal or harmful content
  4. 4. Communications
  5. 5. Platform security
  6. 6. Privacy and identity data
  7. 7. API and automation
  8. 8. Enforcement
  9. 9. Reporting abuse

All policies

  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Acceptable Use Policy
  • Billing & Cancellation
  • Electronic Signature Notice
  • Subprocessors
  • Security Overview
  • Data Processing Addendum
  • Legal Notice

This Acceptable Use Policy forms part of the inSigner Terms of Service. It applies to every account, organization, user, signer, API client, integration, and document workflow.

1. Purpose

inSigner is built to help people create trustworthy electronic records. You must use the service lawfully, respect other people’s rights, and avoid conduct that harms recipients, customers, third parties, or the platform.

You are responsible for activity under your account, organization, API keys, public campaign links, templates, integrations, and credentials.

2. Fraud, forgery, and impersonation

You may not use inSigner to:

  • Forge, falsify, backdate, alter, or misrepresent a document, signature, timestamp, seal, or audit record.
  • Impersonate another person or organization, or claim authority you do not have.
  • Obtain a signature through deception, coercion, concealed terms, or a misleading document.
  • Bypass or manipulate consent, authentication, KYC, access-code, OTP, or approval controls.
  • Create false evidence or present a verification result as proving more than it actually proves.
  • Use stolen credentials, identity documents, payment methods, phone numbers, or email accounts.

3. Illegal or harmful content

You may not upload, send, sign, store, or link to content that:

  • Violates applicable law, sanctions, court orders, or regulatory requirements.
  • Infringes intellectual property, confidentiality, privacy, publicity, or other rights.
  • Facilitates fraud, money laundering, trafficking, exploitation, harassment, or credible threats.
  • Contains malware, ransomware, destructive code, phishing content, or credential-harvesting mechanisms.
  • Contains child sexual abuse material or unlawfully exploits or endangers a minor.
  • Is designed to evade law enforcement, regulatory review, or legally required recordkeeping.

High-risk or regulated documents are not automatically prohibited, but you must have the authority, lawful basis, safeguards, and professional review appropriate to the use case.

4. Email, SMS, and WhatsApp communications

You may contact a recipient only when you have a lawful reason and have provided any required notice or obtained required consent. You may not use inSigner for spam, purchased recipient lists, abusive reminders, phishing, or unrelated marketing.

Document titles, messages, and templates must accurately identify the sender and purpose. Recipients must have a reasonable way to identify the sender and report an unexpected request. Carrier, WhatsApp, and communications-provider rules also apply.

5. Platform and service security

You may not:

  • Probe, scan, or test vulnerabilities without prior written authorization.
  • Attempt unauthorized access to accounts, documents, systems, networks, or provider infrastructure.
  • Disable, evade, or overwhelm rate limits, authentication, logging, encryption, or abuse protections.
  • Introduce malicious code or use the service to attack another system.
  • Interfere with service availability or consume resources in a way that harms other customers.
  • Reverse engineer protected parts of the service except where that restriction is prohibited by law.

Good-faith vulnerability reports should be sent privately to hi@insigner.co before public disclosure.

6. Privacy, sensitive data, and identity checks

You must collect and process personal data only with an appropriate legal basis and must follow applicable notices, consent, minimization, security, retention, and data-subject-rights requirements.

Do not require KYC, biometric checks, government identity documents, health information, financial information, or other sensitive data when a less intrusive method is sufficient. Do not use identity or authentication results for unrelated profiling, discrimination, or automated decisions that are unlawful.

7. API, webhooks, and automation

API keys and webhook secrets must be kept confidential. Automated use must follow published limits, respect recipient consent, validate webhook signatures, handle errors responsibly, and avoid duplicate or excessive requests.

You may not resell, sublicense, scrape, mirror, or create a competing dataset from the service unless a written agreement or applicable open-source license permits it. Public campaign links must not be used to collect data deceptively or distribute unlawful content.

8. Enforcement

We may investigate suspected violations and may restrict a feature, block a message or integration, remove content, rotate credentials, suspend an account, or terminate service. Action may be immediate when needed to protect people, evidence, infrastructure, or comply with law.

Where appropriate, we will consider context, severity, recurrence, cooperation, and risk. We may preserve relevant records, notify affected customers, providers, or authorities, and respond to valid legal process. Fees are not refunded for service terminated because of a material violation, except where required by law.

9. Reporting abuse

Report suspected fraud, impersonation, phishing, unlawful content, or an unexpected signing request to hi@insigner.co. Include the signing link or document reference, sender information, and a concise description, but do not email identity documents, passwords, one-time codes, or unnecessary sensitive data.

arrow_back Back to legal center
inSigner

Sign Smarter. Not Harder.

Compliance-first electronic signatures for Europe and LATAM.

Product OverviewSecurityTrust CenterDevelopersPricingUse cases
Access Log inCreate accountVerify a documentContact sales
Legal Legal centerPrivacyTermsCookiesAcceptable use

© 2026 Nubesti LLC. Securely Architected.

Open source — coming very soon

cookie

Privacy by default

Cookies, kept simple.

This website only stores your dismissal choice. The inSigner app uses essential cookies for secure sessions and preferences. No advertising or analytics cookies.

Read the Cookie Policy