A specific policy for ID and selfie checks.

If you choose the Stripe Identity option, Stripe collects images of your government identification document and your face. Stripe may create and use facial measurements, a record of face geometry, or similar biometric information to compare the selfie with the photograph on the ID and to operate fraud and security controls described in Stripe’s notices.

HandyConnect receives and stores the Stripe VerificationSession identifier, status, outcome timestamps, error code when applicable, and an evidence record of the notice and consent presented to you. HandyConnect is not configured to request, download, or store the ID or selfie images or Stripe’s underlying facial measurements.

HandyConnect asks for this information only to confirm that the person completing the check is the person shown on the ID, reduce impersonation and fraud, and support an identity-verified trust signal on the marketplace. It is not used by HandyConnect to identify you in public places, infer personal traits, or advertise to you.

Collection begins only after you affirmatively check the standalone consent box and proceed to Stripe. The collection-and-use term ends when the identity check and any user-requested retry or review are complete. The retention and destruction schedule in Section 5 applies after that point.

Before HandyConnect creates or reopens a Stripe Identity session, we present a separate notice stating what will be collected, the purpose, the term, Stripe’s role, the destruction rule, and the manual alternative. The Stripe button remains unavailable until you check the specific consent box. The server also rejects a request that does not include the current policy version and affirmative consent.

The consent record is timestamped and includes the policy version, exact notice snapshot and hash, user account, IP address when available, user agent, and the Stripe session binding. You may decline by leaving the box unchecked or exiting the Stripe flow. Contact us if you want to withdraw a pending choice or request deletion; a completed verification outcome or legally required record may not be reversible in every circumstance.

Stripe, Inc. and its applicable subprocessors receive the ID, selfie, and related information to perform the requested verification. Stripe handles that information under its Privacy Policy and Identity notices. HandyConnect does not authorize disclosure to another party except with your consent, as necessary for the requested verification, or where required by applicable law, a valid warrant, or a valid subpoena.

HandyConnect does not sell, lease, trade, or otherwise profit from biometric identifiers or biometric information. We do not use them for marketing or targeted advertising.

HandyConnect’s automated deletion workflow normally makes a Stripe Identity VerificationSession eligible for irreversible redaction 21 days after it is connected to your consent record and targets confirmation of redaction by day 30. This short interval allows time for the verification result and a user-requested retry or review. A service-only job ledger records each attempt, retries temporary failures, confirms completion from Stripe’s signed webhook, and sends unresolved jobs for manual review. Stripe documents that redaction removes collected information from the session and related reports, events, request logs, and files and may take up to four days to complete after a request.

In every case, HandyConnect’s destruction deadline is no later than the earliest deadline required by applicable law. For information subject to the Illinois Biometric Information Privacy Act, that means permanent destruction when the initial purpose has been satisfied or within three years after the individual’s last interaction with HandyConnect, whichever occurs first. For information subject to Texas Business & Commerce Code Chapter 503, destruction occurs within a reasonable time and no later than one year after the purpose for collecting the identifier expires. A valid warrant or court-issued subpoena, an unresolved user-requested review, or a Stripe session that is still processing may require different handling. Those exceptions are restricted, documented, excluded from automatic deletion while active, and routed for follow-up; they do not authorize indefinite retention.

HandyConnect may retain the non-biometric consent record, policy snapshot and hash, Stripe session identifier, status, and timestamps only while reasonably needed to honor requests, demonstrate the transaction and consent, prevent duplicate use, comply with law, or resolve a claim. These records do not contain the ID image, selfie, or facial measurements and are deleted or deidentified when no longer needed for those purposes.