Trust & Safety
What verification means on Authobek
Authobek makes two separate decisions, and they answer different questions. Developer verification answers who published this? Application verification answers is this exact package the one Authobek checked? A listing can have one without the other.
Developer verification
A developer asks to be verified and submits their legal name, whether they are publishing as an individual or an organization, their country, a contact email and any supporting information such as a website or organization registration. A platform reviewer reads the request and records a decision. There is no automated approval and verification cannot be purchased.
Verification is about identity and accountability. It means Authobek knows who stands behind the software and can act against a real account if something goes wrong. It is not a statement that the developer's software is good, secure or suitable for you.
Are you a developer seeking verification?
The verification request form lives inside your developer dashboard. Signing in is required.
Go to developer verification (sign-in required)Application verification
Application verification applies to a specific release, not to the developer. Before a version can be published, Authobek inspects the uploaded package, confirms it is signed, records its signing certificate fingerprint, computes and stores a SHA-256 digest, and runs it through the security scan pipeline. A human reviewer then approves publication.
Because the digest is stored per version, the file you download can be checked against the record Authobek holds. That check is public: request /api/public/verify/<app>/<version> and compare the returned SHA-256 with the file you received.
Every new version repeats the whole process. Verification is never inherited from a previous release.
What a verification decision does not mean
- It is not an endorsement, a quality rating or a recommendation to install.
- It is not an audit of the application's source code or of the developer's internal practices.
- It is not a guarantee about how the application handles your data — that is the developer's Data Safety declaration.
- It is not permanent: verification can be suspended by a governance decision.
- It cannot be bought, and paying for promotion never affects a review outcome.

