Security
Security, in plain words.
How to tell us about a security problem, what to include, and what happens next. If you are not sure it is a security problem, tell us anyway.
Reporting a problem
If you have found a way into an account, a hole in the protection, or data somewhere it should not be, write to security@oakenmesh.com and put “security report” in the first line, so it is not read as a support question. A person reads every message that arrives there.
What to include
- What you did, step by step, and what happened instead of what you expected.
- Where you saw it: the site or the app, and the page or screen.
- When you saw it: the date and the time.
- What you think it would let someone do.
What happens next
We aim to acknowledge a report within a few days, to keep you informed while we work on it, and to publish a detailed account within 90 days of the report. The 90 days is what we aim for, not a promise: if a fix needs longer, we will say so and say why.
What we ask
- Do not take data. Show that something is reachable with your own test account and the smallest step that proves it, and delete anything the bug handed you.
- Do not test against a real family or an account you do not own — real households use this app. Make your own family, or ask us for a test account.
- Do not overload the service. The availability of the protection is the point of the product.
- Do not reach people through the bug, and give us time to fix it before you publish the details.
No bounty
There is no bug bounty. A report is a favour everyone using the app gets the benefit of. If you would like to be named in the published detail, we will credit you, and we will tell you what we did with your report either way.
Thank you
It takes real work to report a problem properly. Everyone using the app gets the benefit of it.