Services Privacy Policy

• FACEIO is a cross-browser facial authentication framework that can be used through the hosted Service or through an on-premises deployment. Application owners create applications in the FACEIO Console ↗ and integrate fio.js, REST APIs, webhooks, ID verification flows, and related service tools.
• The Service is designed to help application owners add passwordless facial authentication, liveness detection, account recovery, fraud prevention, and optional online identity verification to their products. The application owner decides the user journey, notice text, consent flow, legal basis, selected facial recognition engine, region, security controls, and retention settings.
• The selected facial recognition engine, not FACEIO service surfaces, is responsible for the underlying biometric template or biometric hash storage used by a customer application. Application owners are responsible for choosing the engine, configuring cloud region or on-premises deployment, managing encryption keys, retention, deletion, opt-out, fallback access, and compliance with applicable biometric privacy laws.
• FACEIO does not provide legal advice and does not decide whether a customer's implementation is lawful in any jurisdiction. Customers must evaluate their own obligations before production use.

• This policy covers information processed by FACEIO for account management, console access, support, billing, service security, service operation, service telemetry, and limited processing performed on behalf of customer applications.
• FACEIO does not provide services directly to individual end users of customer applications. If you enrolled or authenticated through a website or application powered by FACEIO, contact that application owner for privacy notices, consent withdrawal, deletion, access, or other rights requests concerning that application.
• For end-user personal data processed through a customer application, the application owner is generally the controller or business, and FACEIO may act as a processor or service provider depending on deployment and configuration. FACEIO is the controller for its own account, billing, support, service security, and business contact data.
• This policy does not replace the customer's own privacy policy. If you are an end user of a FACEIO-powered application, the application owner's privacy notice should explain why facial authentication or identity verification is used, what lawful basis applies, how long data is retained, how to withdraw consent where available, and how to request deletion or fallback access.
• For on-premises deployments and customer-controlled AWS Rekognition configurations, the customer may control biometric processing and storage through its own infrastructure or AWS account.
• Where a customer enables ID verification, the customer remains responsible for deciding whether identity document capture, live selfie capture, face matching, document scanning, retention, deletion, and review are appropriate for its users, product, jurisdiction, and risk model.

• Data minimization: We aim to collect and store only the minimum amount of account, service, security, and operational information needed to provide, secure, support, troubleshoot, bill, and improve the Service.
• No FACEIO biometric hash database: FACEIO service surfaces, including this website, fio.js, embedded widgets, REST APIs, webhooks, and the Console, do not operate a centralized biometric hash database and do not persistently store, index, sell, or independently access end-user biometric templates or biometric hash signatures.
• No sale of biometric data: We do not sell end-user biometric data, identity document data, customer API data, or customer application data. We do not use customer end-user biometric templates, face captures, or identity document data for advertising or independent marketing.
• Controller and processor roles: FACEIO acts as a controller for its own account, billing, support, security, and business-contact data. For end-user data processed through a customer application, FACEIO may act as a processor, service provider, infrastructure provider, or software component depending on the selected deployment model and written agreement.
• Legal bases: Depending on the context, processing may rely on contract performance, legitimate interests such as security and fraud prevention, legal obligations, consent, or the lawful basis established by the application owner for its own users. Customers are responsible for documenting and communicating the lawful basis for their own applications.
• Customer instructions: Where FACEIO processes end-user data on behalf of a customer, we process that data to provide the requested Service, follow applicable customer configuration, support deletion workflows where available, maintain security, comply with law, and enforce the Services Terms of Service.
• Sensitive data: Biometric data, identity documents, government IDs, and similar information may be considered sensitive data. Customers must obtain required notices, consent or lawful basis, age-related permissions, retention schedules, and safeguards before using the Service for such data.
• Customer responsibility and liability: Application owners are responsible for their users, customers, notices, consent flows, selected facial recognition engine, AWS account, PixLab Insight deployment, on-premises infrastructure, application index, encryption keys, retention rules, deletion workflows, support flows, and account-recovery decisions. FACEIO and PixLab | Symisc Systems are not responsible for claims, losses, complaints, access disputes, identity disputes, consent failures, deletion failures, key-management failures, region-selection choices, storage choices, retention choices, or biometric-processing claims caused by a customer application, customer configuration, selected engine, customer infrastructure, user misuse, unlawful use, unauthorized use, or non-compliant use of the Service.

• Account and console data: email address, account identifiers, application identifiers, billing status, plan information, support tickets, security settings, and operational configuration.
• Technical and service telemetry: IP address, browser and device information, request metadata, error logs, timestamps, API usage, widget instantiation data, webhook delivery status, security events, abuse-prevention signals, and diagnostic information generated when the Service is used.
• Customer-provided service data: application configuration, support communications, webhook configuration, selected engine settings, security settings, billing information handled by payment providers, and data intentionally submitted through Console or API workflows.
• Biometric authentication flow data: during an explicit user-facing enrollment or authentication flow, face captures, liveness signals, match scores, authentication status, and related technical results may be generated or transmitted as needed to complete the requested operation. Persistent biometric templates, face vectors, embeddings, or biometric hash signatures are created, stored, retained, or deleted by the selected facial recognition engine and deployment configuration, not by a centralized FACEIO biometric database. FACEIO service surfaces do not sell or use customer end-user biometric templates for advertising, independent marketing, surveillance, or mass identification.
• ID verification data: when a customer enables ID Match, the flow may process a live selfie, identity document image, document face, document metadata, extracted fields, quality checks, liveness result, document scan result, and face match result. ID document scanning is powered by PixLab DOCSCAN components, while face detection, liveness, and face verification are powered by FACEIO technology and the customer's selected deployment configuration. Customers are responsible for telling users how this data is used, reviewed, retained, and deleted.
• Payment and transaction data: paid plans may require transaction records, billing contact details, tax information, invoice identifiers, payment status, and subscription metadata processed by payment providers and merchant-of-record services. FACEIO does not store full payment card numbers.

• Provide, operate, secure, monitor, maintain, troubleshoot, and improve the Service.
• Enroll users, perform facial authentication, evaluate liveness, compare faces, return verification outcomes, deliver webhooks, support account recovery, and provide identity verification results where those features are enabled by the application owner.
• Authenticate account holders, manage applications, process subscription status, deliver support, process billing, respond to inquiries, and send administrative notices.
• Detect abuse, investigate security incidents, enforce policies, comply with legal obligations, and protect the rights and safety of users, customers, FACEIO, PixLab | Symisc Systems, and third parties.
• Create aggregated or de-identified operational information that does not identify a person and is used for service analysis, security, capacity planning, abuse prevention, and product improvement.
• Maintain auditability for console activity, API usage, billing records, support interactions, security events, and service health where needed for operation, compliance, dispute resolution, or enforcement of the Services Terms of Service.

• We do not sell end-user biometric data. We do not use customer end-user biometric templates, face captures, or identity document data for independent marketing or advertising.
• We may disclose account, support, billing, security, service telemetry, and operational information to service providers and sub-processors that help us provide hosting, infrastructure, payment processing, customer support, service analytics, communications, legal, security, logging, abuse-prevention, and related services under confidentiality, security, and data-transfer obligations.
• When a customer enables ID Match, identity document scanning and document checks may be processed by PixLab DOCSCAN components. Customers are responsible for telling their users that document images, document metadata, live selfies, liveness checks, and face match results may be processed as part of that verification flow.
• We may disclose information where required or appropriate to comply with law, legal process, security investigations, enforcement of our agreements, fraud prevention, or protection of rights, property, and safety.
• When a customer configures AWS Rekognition with its own AWS account and credentials, processing through AWS is governed by the customer's AWS account, AWS region, AWS terms, and AWS privacy and security obligations. When a customer deploys PixLab Insight on-premises, biometric processing occurs in customer-controlled infrastructure.
• We may transfer information in connection with a merger, acquisition, financing, reorganization, bankruptcy, asset sale, or similar transaction, subject to applicable law and any contractual restrictions that apply to customer data.

• Depending on the context, you may have rights to access, correct, delete, restrict, object to processing, withdraw consent, lodge a complaint with a supervisory authority, and receive a portable copy of personal data. These rights may be subject to limitations under applicable law.
• For FACEIO account, billing, console, and support data, contact us at privacy@faceio.net. We may ask you to verify your identity before responding, and we may retain records needed for security, fraud prevention, billing, dispute resolution, or legal compliance.
• For biometric, ID verification, or other end-user data processed through a customer application, contact the application owner first. FACEIO may not control that data, especially where the customer uses its own AWS account, selected AWS region, or an on-premises PixLab Insight deployment.
• If GDPR, UK GDPR, Swiss FADP, or similar laws apply and FACEIO acts as a processor, processing is governed by a Data Processing Addendum available upon request. Customers are responsible for documenting their lawful basis, notices, consent records, retention schedule, transfer assessment, and data-subject request workflow.

• To the extent FACEIO collects personal information as a service provider or processor for a customer application, California users should contact the application owner for requests about that application.
• For FACEIO account, billing, console, and support data, California residents may contact privacy@faceio.net to exercise applicable access, deletion, correction, portability, limitation, and opt-out rights.
• FACEIO does not sell end-user biometric data and does not disclose California personal information to third parties for their own direct marketing. FACEIO does not knowingly share end-user biometric data for cross-context behavioral advertising.
• Some information processed by the Service, such as biometric information, government identity document data, account credentials, or precise security logs, may be considered sensitive personal information under California law. Customers are responsible for providing any required sensitive-information notices for their own applications.

• Persistent biometric processing and storage may include face geometry, derived face vectors, templates, embeddings, or hashes depending on the selected facial recognition engine. FACEIO service surfaces do not persistently store, index, sell, lease, trade, or otherwise profit from end-user biometric templates or biometric hash signatures.
• FACEIO service surfaces, including this website, the FACEIO Console, fio.js, embedded widgets, REST APIs, and webhooks, are integration, configuration, and orchestration layers. They do not operate a centralized cross-customer biometric hash database for surveillance, mass identification, or independent biometric lookup.
• Facial templates may be represented by a selected recognition engine as vectors, embeddings, or arrays of floating point values, sometimes described in FACEIO materials as biometric hashes. These values are not raw face photographs and are not intended to be reverse engineered into a human-readable face image, but they may still be biometric data or personal data under applicable law and must be protected accordingly.
• Application owners must obtain required notices and legally valid consent before enrolling or authenticating users, including explicit consent where required by biometric privacy or data protection laws.
• EU, EEA, UK, and Swiss customers must use AWS Rekognition with their own AWS account, AWS access keys, selected AWS region, IAM permissions, and customer-controlled AWS configuration, or deploy PixLab Insight on-premises in customer-controlled infrastructure. The customer is responsible for AWS notices, AWS terms, region selection, transfer assessments, deletion instructions, or on-premises security and retention controls.
• Biometric retention and deletion are the responsibility of the application owner and the selected engine configuration. Where FACEIO provides deletion endpoints, console controls, REST APIs, or workflows, the application owner is responsible for invoking them when required by law, user request, consent withdrawal, opt-out request, or the customer retention schedule.
• Each FACEIO application is designed to operate with a separate application index. Application owners are responsible for managing their application index, safeguarding any encryption key they generate, download, store, or use through the FACEIO Console, controlling administrator access, and honoring valid deletion, opt-out, or removal requests.
• Facial authentication, liveness detection, face matching, anti-spoofing checks, ID verification, and fraud signals are probabilistic technical outputs. Customers are responsible for deciding whether automated results require fallback authentication, manual review, account recovery, additional evidence, or human intervention under applicable law.
• For laws such as Illinois BIPA and similar biometric statutes, customers are responsible for written notices, consent, retention schedules, destruction requirements, and any other implementation-specific compliance duties.

Account, Console, support, billing, service telemetry, and operational information may be processed in countries other than where you are located. Where required, we use appropriate safeguards for international transfers. For EU, EEA, UK, and Swiss biometric deployments using a customer's own AWS account or on-premises PixLab Insight, the customer controls region, infrastructure, hosting location, transfer assessment, and any supplementary safeguards for biometric processing.

• You may update certain account information in the FACEIO Console or contact support for assistance.
• You may close a FACEIO account or request deletion of account-level information, subject to records that must be retained for billing, security, legal, fraud-prevention, dispute-resolution, or audit purposes.
• You may unsubscribe from non-essential service communications where available. Administrative, transactional, billing, security, support, and legal notices may still be sent.
• If you are an end user of a customer application, contact that application owner to withdraw biometric consent, request deletion, request a fallback login method, or exercise rights related to that application.
• Browser privacy settings, device permissions, camera permissions, and network security settings may affect how the widget loads or whether a user can complete enrollment, authentication, liveness detection, or ID verification. Cookie-specific controls for FACEIO websites are described in the Website & Cookie Policy.

We process rights requests according to applicable law and the role we play for the relevant data. If the data is controlled by a customer application, we may direct you to that application owner. To protect privacy, we may verify identity before fulfilling a request.

• For FACEIO-controlled account, console, billing, support, and security data, contact privacy@faceio.net.
• For application-user biometric data, identity document data, account-access decisions, or consent withdrawal inside a customer product, contact the application owner first because the customer usually controls that workflow and may use its own AWS account or on-premises infrastructure.
• We may decline or limit a request where permitted by law, including where fulfilling the request would compromise security, reveal another person's data, conflict with legal obligations, or prevent us from defending legal claims.

We retain account, billing, support, security, and operational information for as long as necessary to provide the Service, comply with legal obligations, resolve disputes, enforce agreements, maintain security, and support legitimate business purposes.

• Console and account records may be retained while an account is active and for a reasonable period after closure where needed for billing, support, fraud prevention, audit, or legal purposes.
• Operational logs, error reports, webhook records, abuse-prevention data, and security events may be retained for troubleshooting, availability, security, and incident investigation.
• Biometric retention for customer applications is controlled by the customer and selected facial recognition engine unless a written agreement states otherwise. Customers are responsible for configuring deletion, calling available deletion APIs, and honoring user or legal retention limits.
• ID verification records, if enabled, are retained according to customer configuration, applicable law, and any written agreement. Customers should avoid retaining identity document images or extracted fields longer than necessary for the verified purpose.

We build privacy and security controls into the Service by design and maintain administrative, technical, and organizational safeguards appropriate to the Service, including access control, monitoring, logging, abuse-prevention, operational-security measures, intelligence-backed security monitoring, and role-based internal access designed to protect account, support, operational, and service data. No system can be guaranteed to be fully secure, and we cannot guarantee that unauthorized access, disclosure, alteration, or destruction will never occur.

Customers are responsible for secure integration, API key handling, AWS credential handling, AWS IAM permissions, on-premises security, access control, network protection, webhook security, logging, monitoring, backup policies, and incident response procedures for their own applications and infrastructure.

The Service is not directed to children. Customers must determine whether their application is permitted to process children's data and must obtain any parental consent, age assurance, or other permissions required by law.

FACEIO does not knowingly operate customer applications, set customer age restrictions, or decide whether a customer may use facial authentication or ID verification for minors. If you believe a child submitted information through a FACEIO customer application, contact the application owner first and then contact us if you need assistance routing the request.

We may update this Privacy Policy from time to time to reflect changes in the Service, deployment models, legal requirements, security practices, third-party components, or customer-facing features. The effective date above indicates the latest version. Continued use of the Service after updates are posted means the updated policy applies from that date forward.

• Privacy and data protection: privacy@faceio.net
• Technical support: Use FACEIO Console support tickets or the Community Forum ↗.
• Customer application requests: if your request concerns enrollment, authentication, deletion, consent withdrawal, or ID verification inside a third-party application, contact that application owner first.