Protocols & Docs.

Comprehensive legal agreements, data retention policies, and API integration guidelines for the FakeYourID alternative infrastructure.

Acceptable Use Policy

The FakeYourID Alternative Platform (operating via our endpoints) is engineered exclusively as a Business-to-Business (B2B) Quality Assurance and software testing utility.

Authorized Applications

Our rendering engine is strictly authorized for use in the following environments:

  • Continuous Integration (CI): Automated pipeline testing for KYC (Know Your Customer) systems.
  • OCR Calibration: Providing mathematically valid MRZ and PDF417 structures for Optical Character Recognition calibration.
  • Sandbox Environments: Dummy data generation for internal financial or identity verification sandboxes prior to production deployment.

Zero-Tolerance Prohibitions

Any usage outside of software testing is a direct violation of our terms. We actively monitor endpoint behavior to prevent abuse. You are strictly prohibited from:

  • Generating assets intended to bypass real-world physical or digital identity verification systems (e.g., social media verification, crypto exchanges).
  • Attempting to print or manufacture physical representations of the generated digital assets.
  • Utilizing the API for fraudulent misrepresentation, identity theft, or deceptive practices.

Violating these terms will result in immediate API key revocation, IP bans across all nodes, and cooperation with digital compliance authorities if required.

Privacy Protocol

Unlike legacy generation tools, our infrastructure operates on a strict **Zero-Retention Architecture**. Data privacy is integrated at the compiler level.

Data Processing & Ephemeral Storage

When a payload containing test variables (Name, DOB, ID Number) is sent to our API or entered via the GUI dashboard:

  • The data is processed entirely in volatile memory (RAM).
  • The mathematical logic calculates the required PDF417 and MRZ checksums.
  • The asset is rendered and delivered via the API response or download prompt.
  • Immediately upon delivery, the data and the rendered asset are permanently wiped from our nodes.

We do not maintain databases of generated assets. We do not store input variables. We do not sell or analyze the dummy data you utilize for your testing pipelines.

Analytics and Telemetry

We only monitor endpoint telemetry (request frequency, error rates, and API key authentication) to ensure server stability and prevent DDoS attacks. No payload contents are logged during this process.

API Documentation

For enterprise developers, our REST API allows seamless integration into your existing CI/CD pipelines. All requests must be authenticated via a Bearer Token provided in your dashboard.

POST api.veriftools.is/v1/generate/kyc

Authentication Headers

Include your active API key in the request headers. Do not expose this key in client-side code.

HEADERS
Authorization: Bearer sk_test_51Nx...
Content-Type: application/json

Request Payload Example

The engine requires structured JSON to calculate the algorithmic barcodes correctly.

JSON
{
  "document_type": "us_driver_license",
  "variables": {
    "first_name": "JOHN",
    "last_name": "DOE",
    "dob": "1990-01-01",
    "id_number": "D12345678"
  },
  "output_flags": {
    "render_pdf417": true,
    "format": "base64"
  }
}

Contact Node

If you require enterprise API rate-limit increases, need to report a bug in the mathematical MRZ generator, or have compliance inquiries regarding our Zero-Retention policy, route your communications below.

Primary Support Gateway

[email protected]

Average response time: < 12 hours for active API token holders.