1. Why We Publish the Bar
Briovela will send messages and move money for small businesses. Providers and carriers expect platforms to keep bad actors off shared infrastructure. We publish our qualification criteria so honest businesses know what to expect, and so reviewers can see that the bar is real. The full internal questionnaire and scoring remain internal (sender-onboarding control of record).
2. What Every Applicant Provides
- Legal business identity: who you are as a registered business
- Domain ownership: proof you control the sending / business domain
- Described use case: what you will send and why
- Consent-provenance attestation: how your contact lists were obtained (self-collected, provable consent only)
- Acceptable Use Policy acceptance: binding agreement to the AUP
New senders are subject to staged sending limits while reputation is established. Details of ramp schedules stay operational, not public.
3. What Triggers Manual Review
Higher-risk use cases, incomplete or inconsistent applications, unusual consent stories, and cases flagged by automated checks receive human review before bulk access is enabled. We may ask for additional documentation. We do not publish the exact triggers or scoring weights.
4. What We Refuse
- Purchased, rented, borrowed, harvested, or appended contact lists
- Restricted or illegal categories prohibited by law or by our providers
- Deceptive, evasive, or detection-evasion use cases
- Applicants who will not accept the AUP or cannot prove consent provenance
How continuous controls work after access is granted: Platform Safeguards. Abuse reports: security@briovela.com.
5. FAQ
- Is this the full internal questionnaire?
- No. We publish the criteria overview. The full internal questionnaire and scoring stay internal so they cannot be gamed.
- Can I use a purchased email or SMS list?
- No. Purchased, rented, borrowed, harvested, or appended lists are prohibited. Consent must trace to the person who gave it.
- Where do the rules live in writing?
- In the Acceptable Use Policy and Platform Safeguards pages, which this page complements.
Document version 2026-07-09.5