Reporting a security problem

If you have found a way to reach data or take an action that should not be possible, write to security@launchwithlimn.com. Reports are read by the people who can fix them.

What to send. The address you were on, the steps that reproduce it, and what you saw. A screenshot or a short recording helps. If it involves an account, say which one you were signed in as.

You will hear back within two business days. That first reply confirms the report arrived and says whether it is already understood. A second message follows once the problem is fixed or once a date for the fix is set.

Please hold the details until there is a fix. A flaw described in public is a flaw anyone can use, on accounts belonging to businesses that had no say in it. Give the fix time to ship, and write about it afterwards with our thanks.

Test on an account you own. Use records you put there yourself, and stop at the point a flaw is proven. Every other account on the service belongs to a working business with customers in it.

Credit rather than cash. Anyone who reports a flaw can be named for it once the fix is out. Say in your message whether you would like that.

• Separate workspaces. Each workspace is separated from every other at the database, so a query can only return rows belonging to the workspace that asked.
• Encrypted connections. Every page and every request travels over TLS. The permissions a business grants when it connects a social, calendar or advertising account are encrypted before they are stored.
• Sign-in. Passwords are stored only as a one-way hash, and anyone who signs in with a password can add a second step, a code from an authenticator app or one texted to their phone. Repeated attempts are slowed down.
• Private files. Photographs, documents and recordings a workspace uploads are kept in private storage that no public address reaches. Each one is fetched through the app, which checks that the person asking belongs to that workspace.
• Cards. Card numbers are typed on the payment processor's own page and never reach Limn's servers.
• Error reports. When something breaks, the report that goes to our error-reporting provider has request contents, email addresses and account details removed first.
• Recovery. The database can be restored to any moment in the last 24 hours.
• A record of changes. Each workspace keeps an audit log of who changed what.

Every company that can see data held in Limn is listed on the subprocessors page.

For anything that is not a security problem — a question, an account, a bill — Support is the faster door.