Security Lab

1. What is your project's name? *

We’ll use this name when we communicate with you about your proposal. You can use the name of the project you’re applying for, your own name, or a pseudonym or nickname.

See help guide for more information.

2. What is your name? *

Feel free to use a pseudonym or nickname.

3. What are your pronouns? *

4. Please provide a primary email. *

We will use this email address to communicate with you about your proposal.

5. Please provide a secondary email.

6. Are you proposing a security audit for your own project, or another project? *

My own project
Another project

7. Has this project received OTF support before?

If you're applying for a Security Lab engagement for a current OTF project, please skip to question 10.

8. Briefly describe the project. *

For example, what are its aims or mission? What tools or initiatives does it work on? You might want to include links to websites, apps, or social media.

9. Why is this project important for internet freedom? *

For example, how does it benefit people in repressive contexts or strengthen the internet freedom ecosystem?

10. Is there a Security Lab vendor you would prefer to work with?

We can't guarantee we'll be able to match you with your chosen vendor. All our vendors are highly qualified and have overlapping expertise.

11. Do you have an ideal timeline? *

If you're flexible, please indicate that in your response. Ideally though, we can have an idea of when you need the report prepared.

12. I will have time to coordinate the engagement directly with the vendor

We estimate 80 hours of work per engagement, which spans around four months from scoping to final report delivery. If you're applying to recommend a public safety audit, this doesn't apply to you.

13. What problems are you hoping to solve with this engagement - for users, your organization, or the internet freedom community? *

Try to focus your answer on why the app's privacy and security are important to internet freedom.

14. What are the main technical features or issues the engagement should focus on? If more than one, please explain what you'd like to prioritize. *

15. Email of technical contact

Audit engagements require coordination with your project's technical lead to ensure auditors have timely access to all necessary technical elements and a point of contact to answer questions as needed.

16. Please provide links to any helpful documentation or repositories

I acknowledge

I have read and understand OTF's Terms and Privacy policy.

Read the Terms and Privacy policy.

I understand that all intellectual property created with support for this application must be openly licensed.

OTF does not engage in any Non-Disclosure Agreements with projects

Public safety audit applicants

I want to be informed about the results for this public safety audit if approved.

You must have Javascript enabled to use this form.

Your cookie settings

This website deploys cookies for basic functionality and to keep it secure. These cookies are strictly necessary. Optional analysis cookies which provide us with statistical information about the use of the website may also be deployed, but only with your consent. Please review our Privacy & Data Policy for more information.

This Website uses cookies. Below you can select the categories of cookies to allow when you use our website and services.

Essential Cookies

Strictly necessary for the operation of a website because they enable you to navigate around the site and use features. These cookies cannot be switched off in our systems and do not store any personally identifiable information.

Always enabled.

Analytics Cookies

With these cookies we count visits and traffic sources with the sole purpose of improving the performance of our services through metrics, showing us how users navigate the application. The information collected is aggregated and contains no personally identifiable information. If you block these cookies, then we will not know when you have used our services.