Certify Your Ring Application
Before your app can be published on the Ring Appstore, it must pass a certification review covering technical, security, and policy compliance. This guide walks through the submission flow and what to expect.
Prerequisites
- App configuration is complete (Configure phase)
- OAuth endpoints are deployed, accessible, and tested
- You have tested the account-linking workflow in the staging environment with both staging and production endpoints
Starting Certification
From your app's overview page, click the Certify section (step 4 in the app lifecycle). This opens the certification screen.
If a previous version was withdrawn, a banner at the top shows the withdrawn review details — version number, original submission date, and status. You can submit a new version whenever you're ready.
Submission Steps
The certification screen lists two items you must complete before you can submit:
1. Privacy & Legal Questionnaire
Click Complete questionnaire to open the questionnaire form. This helps Ring verify that your integration meets data protection and compliance standards.
The questionnaire is organized into five tabs:
| Tab | What it covers |
|---|---|
| General | Company overview (business description, location, years in operation) and business context (features provided through Ring, whether you serve users outside the US, whether the product targets children under 13). |
| Data processing | What Ring user data you collect, how each element is used, how you handle video metadata, data minimization practices, whether data is used for AI training, and any secondary uses beyond the core service. Also covers transparency disclosures — links to your privacy policy and terms of service, and how you communicate data practices to users. |
| AI governance | AI models in use, performance monitoring (drift, edge cases, consistency), version management, explainability of AI decisions, content and output controls, automated decision-making safeguards, and any law enforcement integrations. |
| Data protection | Security architecture (encryption, data flow diagrams, backups), security programs (pen testing, attestations, vulnerability management), access controls and monitoring, audit capabilities, employee training, compliance framework, rights management (consent, retention, DSARs, deletion), and privacy governance. |
| Third-parties | Which third parties access Ring data and why, vetting and monitoring processes, contractual safeguards, access revocation, audit trails, and whether users can restrict third-party sharing. |
Each tab contains a mix of free-text fields, radio buttons, and conditional follow-up questions. Fill in all required fields across every tab.
At the bottom of the questionnaire you have two options:
- Save draft — saves your progress so you can return later.
- Save and submit — finalizes and submits the questionnaire.
2. Add Notes for Reviewer
Click Add notes to open the reviewer notes form. These notes give the Ring certification team the context they need to test your integration end-to-end. The form has three fields (each 20–4000 characters):
- How can a Ring reviewer create an account on your platform? — Step-by-step instructions for creating a reviewer account, including any special credentials or signup links.
- How can a Ring reviewer perform account linking? — Describe the account linking process, including authentication steps and any Ring-specific OAuth flows.
- How can a Ring reviewer test the end-to-end integration with your app? — Explain how reviewers can test the full integration workflow, including test devices, sample scenarios, and expected outcomes.
Click Save when done.
Submitting for Review
Once both steps are complete, the acknowledgment checkbox at the bottom of the page becomes enabled:
"I have tested my app in staging environment. I was able to test the account-linking workflow with both my staging and production endpoints. I am ready for Ring's certification team to test my app with production endpoints for account linking."
Check the box, then click Start review process to submit your app for certification.
During Review
After submission, the portal shows your review status:
- Version and submission timestamp are displayed.
- Estimated completion: 1–2 business days.
- A Withdraw option becomes available 1 minute after submission if you need to pull the app back and make changes.
Review Outcomes
| Outcome | What happens next |
|---|---|
| Passed | Your app is certified and ready for the Publish phase. |
| Failed | Feedback is provided. Fix the issues, then resubmit (creates a new version). |
| Withdrawn | You pulled the submission. Resubmit when ready. |
Version History
Click Review version history from the certification page to see all submitted versions with their status (Certification Under Review, Deployment Pending, Certification Withdrawn) and last-active dates. The summary at the top shows total versions, the current live version, and the latest version number.
Developer FAQ & Certification Best Practices
For answers to frequently asked questions about account linking, nonce matching, device capabilities, and testing — as well as best practices for preparing your app for certification — see the Developer FAQ & Certification Best Practices page.
