Get started

Trust and security

Trust

Trust depends on honest limits. This page explains how incola is designed and what the code enforces. It is not a certificate, and no outside firm has reviewed it.

How it works today

What protects your information, and what does not

On the way to us

Your connection uses TLS, version 1.2 or 1.3. Plain HTTP is redirected to HTTPS, and browsers are told to use HTTPS for a year. We do not publish a cipher name, because the cipher is negotiated per connection and yours may differ from someone else’s.

Your most sensitive identifiers

Your Social Security number, A-Number, USCIS online account number, passport number, and I-485 receipt number are each encrypted on their own with AES-256-GCM, under a key that belongs only to your account. The documents we generate for you are encrypted the same way.

What is not encrypted, and why we say so

Your name, date of birth, address, contact details, and place of birth are stored as ordinary text, as is the database itself. That is a stated limit of the design, not an oversight. Anyone claiming your whole record is encrypted would be overstating it, so we do not.

Backups

Backups are encrypted before they leave the server, and the server that makes them cannot read them back — it holds only the public half of the key. Copies are kept for 35 days and then expire. Delete an application and it leaves active storage at once; deletion is complete when the last backup holding it expires.

Files you upload

We check each file, attach it to the workspace record you are allowed to use, and verify later that it has not changed. We do not use your documents to give legal advice on their own. Files are removed from active storage immediately on deletion, and residual backup copies expire on the same 35-day schedule as the rest of your account.

We do not sell your information

incola does not sell, rent, or trade your information to anyone, for money or for anything else of value, and does not share it for advertising. No advertising network or analytics company receives it. That commitment is written into the Privacy Policy, which is where it is binding.

Who can reach the live system

People who run production are meant to hold the least access they need. That access is monitored, and may be used only for approved operational work. Our incident plan covers how we find an incident, contain it, tell you, put things right, and help you.

Read the Privacy Policy for what we collect, how long we keep it, and how to ask about your own data.

No unverified certifications

We do not claim what we have not earned

incola does not claim SOC 2, ISO, HIPAA, government approval, attorney-client privilege, or legal representation through this website.

Start safely

Tell us what you are trying to do.

We’ll check whether one of the forms incola supports fits your situation.