FAQ for admins

https://www.svipe.com/svipe_bot_privacy

https://www.svipe.com/svipe_bot_terms

We actually do better than humans who verify a doc 😉. We read the document content electronically (using NFC) and verify the digital signature of the content using the police certificate from the issuing country. So, to fool us with a fake document, you would need to breach the national security of the issuing country and get hold of their cryptographic keys. Expiration date is also checked and we also verify that the document has not been reported lost or stolen, when such services exist for the country where the document is issued.

We use state of the art face recognition and liveness detection to match the user in front of the phone to the biometric photo stored in the document chip.

This is indeed tricky as a user could ask a friend to scan the QR code during the verification and can indeed happen. The situation is however the same for any kind of age verification, online or even in the real world, including a teenager asking an older friend to buy beer for him ;-)

To mitigate this, we have set limits so that a given document can verify at most one Discord account. That account can then use the Svipe ID to verify again as many times as the users wish, on as many guilds as they want — but that Svipe ID cannot verify another Discord account.

We have also implemented age roll-back protection: if an account has been verified once with age x, it can never be verified again with a lower age. This means that by asking an older friend to do a verification, the user will essentially destroy his or her own ability to do future verifications for this account.

In case of doubts about the verification of one particular user, we recommend the admin to simply delete the roles from that user and suggest a new verification. While the first verification with Svipe ID requires scanning the document, a re-verification only takes seconds for a legit user, and is extremely cumbersome if the user indeed asked someone else.

Svipe ID requires a phone with NFC and a ICAO 9303 document (issued by 140+ countries). Without this, a user cannot verify with the Svipe verification bot.

However, you as a guild admin, are always the one taking the final decision and you can at any time overpower the bot and manually verify a user by assigning the corresponding roles.

It is on our roadmap to offer more personalizations to the bot. We will progressively increase the number of configurable parameters in the future. You are welcome to chat with us on our discord server and share your needs and use-case, and we’ll prioritize our dev work accordingly :)

Unfortunately, for the time being, all users will need to verify again after the change of configuration. We might offer a migration tool to facilitate this in the future, but we still need to investigate that in more detail before we commit to such a feature.

Nope. We do not keep track of this. As soon as a user has verified and the roles are assigned, the bot forgets everything about this.

The log_channel is meant to be a channel for you to keep an audit log of everything that has happened on your guild.

If this is not sufficient for your needs, we’d be more than happy to hear about your use case and we can certainly find a solution!

We’d love to hear about your use case!

The free version of the bot will be limited to “verified” and “18+”, but we are planning on Offering a lot more features in an upcoming premium version.

Take a look at our developper page to check what verified information Svipe can offer: https://developer.svipe.com/documentation#/oidc?id=scopes . The discord bot can access and use any of this for verification purposes (assuming the user consents sharing the data).