Refine has completed its SOC 2 Type 1 examination
Refine has completed its SOC 2® Type 1 examination and received its first SOC 2 report — an important step in our ongoing commitment to protecting researchers and their work.
An important milestone
Protecting the work researchers entrust to Refine has been a priority from the beginning. Today, we are pleased to share that we've reached an important milestone in that journey: Refine has completed its System and Organization Controls (SOC) 2® Type 1 examination and received its first SOC 2 report.
Why it matters
Researchers may upload unpublished papers, early-stage ideas, and other work that is not yet ready to be shared publicly. We understand the trust involved in submitting that material to Refine, and we take the responsibility seriously.
The examination evaluated the design of the controls we have in place to protect our systems and the information processed through the Refine platform. For our customers and institutional partners, the report provides independent assurance that security is being built into the way Refine operates.
What's next
Completing our SOC 2® Type 1 examination is an important milestone in our ongoing commitment to security. We will continue investing in the systems, policies, and practices that help protect our customers and their work.
We're grateful to Prescient Security for conducting the examination and supporting us throughout the process.
For additional information about Refine's security practices, visit our Trust Center.
About the author
More posts
Your Document Doesn't Exist in a Vacuum. Now Your Refine Report Doesn't, Either.
With Context, attach referee reports, response letters, data outputs, and prior analyses to any Refine review — and have your document checked against everything it depends on, up to 100,000 words.
A Structured Benchmark for AI Paper Review
Refine won 90.4% of 1,349 head-to-head matches against single-shot LLM reviewers and scaffolded review systems on 150 economics preprints.
How jemalloc cut our production memory by 47%
A FastAPI service sat pinned at its 1 GiB memory cap. The cause was glibc fragmentation under bursty async load; swapping the allocator to jemalloc cut average production RSS by 47%.