Security & data

Your files

• A file you send lives only in the memory of the request that reads it. Montek does not write it to disk, to object storage or to a database, and it is gone when the answer is sent.
• Answers are not kept either: Montek stores no copy of the fields it returns.
• Your documents are not used to train models.

What Montek keeps

For billing and support, one row per call: organization, project, key, model, units, whether it was within the plan, duration and status. No file name, no content, no extracted values. Logs follow the same rule.

Where it runs

Requests run on Cloudflare's network, close to the caller; the database of accounts, keys and usage is in the Asia-Pacific region. Traffic is HTTPS only (TLS 1.2+). Stored data is encrypted at rest.

Access

Accounts are by invitation and sign in with Google; Montek stores no passwords. API keys are stored as SHA-256 hashes and shown once. Each organization has an owner and roles of its own (new organizations start with admin, sales, billing and developer), and members work only in the projects they are given, so each person gets only what they need. Montek does not collect payment details: plans are invoiced and paid by bank transfer.

Personal information

Montek handles personal information under Japan's Act on the Protection of Personal Information (APPI). Details are in the privacy policy. For a security questionnaire, a data processing agreement or a dedicated deployment (VPC or on-premises), contact contact@montek.io.