App review guidelines
Last updated: October 20, 2026
We review the information developers submit to decide whether an app meets our review requirements. Verification reflects that review, at that time. It isn't a security audit, an endorsement, or a guarantee of an app's identity, performance, security or legal compliance, and you can't describe it as one.
A verified app shows a Verified by mailfloss badge on the mailfloss consent screen instead of a "not verified" warning. An unverified app can have up to 100 active OAuth connections, and more than one connection from the same account can count toward that limit. Verification removes that limit; rate limits, plan limits and our other controls still apply.
These guidelines are part of the mailfloss Developer Terms. Changes to them follow section 13 of the Developer Terms.
How review works
- In the mailfloss dashboard, open Developers → Your apps, open your app, then its Get verified tab.
- Fill in every section and submit. Your app can normally keep running during review, subject to the Developer Terms. Its settings are locked until the review is done, but you can still rotate its secret or delete it.
- We aim to finish each review within 5 business days, and we email the contact address you gave us with the decision:
- Approved: the badge appears and the unverified-app connection limit goes away.
- Changes requested: the email and the Get verified tab say what to fix. Edit the app and resubmit.
- Suspended: see Suspension.
Our review times are targets, not guaranteed deadlines. Missing one doesn't approve an app, approve a change or restore access. We decide whether to verify an app, and we may decline any submission. If a reviewer needs access to your app to test it, we ask by email. We never ask for your passwords.
What we check
Listing
- The name and logo are yours and don't imitate mailfloss or another company. Don't use "mailfloss" in your app's name in a way that suggests mailfloss made it or endorses it; "for mailfloss" or "with mailfloss" is fine.
- The logo is a square PNG, at least 512×512, readable at small sizes, uploaded in Your apps. mailfloss shows only uploaded logos.
- The summary (at most 90 characters) and description (at most 2,000) say plainly what your app does with a mailfloss account. No claims you can't back up, such as accuracy or deliverability figures.
- The website, support contact and privacy policy links work and are controlled by you or by a service provider you authorized. Your privacy policy says what mailfloss data you collect, how you use and share it, and how long you keep it.
Show how it works
- 2 to 8 screenshots of your app as it is today.
- A Loom or YouTube video that shows someone connecting a mailfloss account, approving the consent screen and using the feature that needs mailfloss. The video replaces a test account.
- Setup and testing steps a reviewer can follow.
- Use made-up data in screenshots, videos and test accounts. Don't submit real contact lists, credentials or other confidential customer information, and submit only material you have permission to share with us and with the service that hosts your video. Tell us which material is meant for a public listing.
Permissions
- Ask only for the scopes your app uses. We compare each scope with your reason and the video.
- Scopes that change data (write:integrations, write:erasures, write:account) always need a reason.
- verify spends the connected account's credits. Say when your app starts email verification, and never start it without the user's action or setting.
Company
The legal name, contact email and country of the person or organization responsible for the app. We use the contact email for review decisions and urgent notices, so keep it current.
Proof it works
At least one successful connection. Your own mailfloss account counts.
Behavior we expect
- Call the API only for features the user turned on, and respect rate limits.
- Store client secrets and tokens on your server, never in a browser or mobile app. If one may have leaked, rotate the secret, revoke the affected tokens and tell us.
- Revoke the token (POST /oauth/revoke) when a user disconnects or uninstalls your app, and delete the affected data within 30 days, as section 2 of the Developer Terms requires.
- Follow the Developer Terms.
Changes after verification
A new name, logo, redirect domain or permission goes to us for review. People keep seeing the approved version until we approve the change, and existing connections keep the permissions they approved. Removing a permission or a redirect URI, or adding a redirect URI on a domain we already approved, takes effect right away for new connections.
Tell us before you materially change what your app does, how it uses or shares mailfloss data, or who owns or operates it. We may require a new review before the changed app uses mailfloss data or keeps showing as verified.
Suspension
We may suspend an app, or withdraw its verification, if it breaks these guidelines or the Developer Terms, puts mailfloss users, their data or our systems at risk, misleads people, or if the law requires it. A suspended app can't connect new accounts, and the accounts already connected lose access at once. We email the contact address with the reason when we can share it.
If you think we made a mistake, reply to that email or write to [email protected]. We aim to reply within 5 business days; that's a target, not a guarantee. After we reconsider, our decision is final, subject to any rights the law gives you.
Common reasons we ask for changes
- The video doesn't show the mailfloss connection or the feature that uses it.
- A permission has no clear use in the app.
- The privacy policy doesn't mention the data the app reads from mailfloss.
- Screenshots show placeholder or another company's content.
- The support contact or a link doesn't work.
Contact
Questions about review: [email protected].