Wicket

What does Wicket do to protect user privacy?

Wicket does several things to ensure user privacy. To name a few, Wicket: Designed use of the program to be opt-in only Creates embeddings (a series of numbers) to protect the user identities and ensures face photos aren't stored on edge devices Does not own customer data; customers own their user data Does not sell or monetize PII data to third parties Strong infosec program with regular 3rd-party evaluation To see our entire privacy framework, visit the Privacy & Security page.

What does opt-in only mean?

Opt-in only means just that. To use Wicket facial authentication, all users must explicitly opt in prior to uploading an image into our system. Wicket does not take pictures of users for enrollment without user knowledge; users take and submit their own selfie and provide Wicket with permission to use it to give them access to facial authentication-enabled features, such as facial ticketing, facial payments, and facial access.

Is facial authentication data secure?

All PII is directly provided by the Customer or User. PII is then translated from an image to a mathematical representation of the face for identification. When we receive user PII, we use encryption (at rest and in transit) to ensure the information is safe, and any images and data captured at the actual event are automatically deleted from all systems within a timeframe determined by the organizer.

Who owns the facial data?

Wicket acts as the Data Processor with the Customer as the Data Controller. Customers exclusively own the database that holds the information, and all Personally Identifiable Information (PII) is stored in the cloud, with a strong security framework that prevents 3rd-party access or sharing.