Verification

For security and privacy reasons, some third parties require a rigorous verification process to demonstrate that your business has a legitimate use case. Make tries to support customers as much as possible in this process. That said, many of the requirements are beyond the scope of Make's control. In general, the verification process may involve the following:

  • Rejection

    • Sometimes third-party feedback provides the specific required changes. Sometimes waiting several months and reapplying is successful. In general, you might be at the whims of the individual reviewing your verification.

  • One month or more to get approval depending on the third party

  • Ongoing compliance to maintain verified status

  • Unexpected changes by third parties

  • Screencasts to demonstrate the user experience and use of user data and why you need the scopes and permissions you're requesting.

  • Publicly accessible privacy policy and/or similar notices

  • Independent security audits of your platform

  • Granting end-user level access to your instance for review purposes

Because the verification can sometimes take months, we recommend starting at your earliest convenience.

Google

Google flags your app as unverified until you complete their process. This means that your end users see a warning that your app is unverified. Here are some helpful links:

Meta

Meta's App review process requires you to demonstrate legitimate and responsible use of end-user data. Business verification, a separate process that confirms the authenticity of your company, may be required as well. Our recommended best practice is to use your company's business Facebook/Meta account for creating and developing your app in Meta.

Microsoft

Microsoft's Publisher verification lets users outside of your MS Azure organization use MS apps on your instance.

Last updated