Privacy Policy

This Privacy Policy explains how 2All collects, uses, stores, and shares information when you visit our website, create an account, use the CRM or HR2All Team app, use face-attendance features, or connect an external service. It also explains the choices and rights available to you.

Organizations using 2All decide what customer and business information their users enter into the CRM. For that information, the organization is responsible for providing appropriate notices and having a lawful basis to process it. 2All processes that information to provide the service to the organization.

Depending on the features you use, we may collect:

• Account information such as name, work email, phone number, company, role, and login credentials.
• CRM records such as leads, contacts, accounts, deals, tasks, follow-ups, notes, and activity history.
• Files and business records such as proposals, quotations, identity or KYC documents, and uploaded documents.
• Billing and operational records such as subscription selection, wallet entries, and transaction references. We do not treat CRM wallet balances as bank deposits.
• Integration data such as connected-account email addresses, encrypted OAuth tokens, configuration details, and user-initiated actions.
• Face-attendance data described in Section 3, when your organization enables that feature.
• Technical data such as IP address, browser and device information, authentication cookies, page URLs, timestamps, and security logs.
• Support messages and other information you choose to send us.

3.1 What face data we collect

If your organization enables face attendance, the HR2All Team app uses the device camera to capture frames for face detection and liveness checks. A numerical face template (also called an embedding) is generated on the device and sent to our server. We store that template and an enrollment selfie. At check-in or check-out, we also receive a newly generated template and a small selfie, and may store the resulting similarity and liveness scores with the attendance record.

This feature uses the ordinary device camera. It does not use Apple Face ID, the TrueDepth camera system, or Apple's Face ID authentication data.

3.2 Why we use face data

We use face data only to enroll an authorized employee, confirm that the person checking in or out matches the enrolled employee, perform liveness checks intended to reduce spoofing, and maintain the related attendance record. We do not sell face data, use it for advertising or marketing, or use it to train general-purpose artificial intelligence models.

3.3 Processing, access, and sharing

Face detection, liveness analysis, and initial template generation occur on the device. The server compares the submitted template with the enrolled template. Attendance selfies and results may be viewed by the employee and authorized users of the employee's organization, according to role-based permissions. Face templates are not returned through ordinary employee profile APIs.

We may use infrastructure providers to host and operate the service, subject to contractual and security controls, and may disclose information when legally required. We do not share face data with advertisers, data brokers, or marketing analytics providers.

3.4 Storage and security

Face data is transmitted using encrypted HTTPS connections and stored in access-controlled database and file storage. Stored selfie files use generated filenames, and access to attendance photos is restricted by organization membership and user role. No method of storage or transmission is completely secure.

3.5 Retention and deletion

The enrollment template and enrollment selfie are retained while face verification remains enrolled for an active employee. They are deleted when an authorized administrator resets the employee's face enrollment or deletes the employee account. Check-in and check-out selfies form part of the attendance record and are retained according to the employer's HR and legal retention requirements; they are deleted when the related attendance record or employee account is deleted. Some attendance information may need to be retained where employment, tax, audit, or other law requires it.

Employees can ask their organization's administrator to reset face enrollment or delete eligible records, or contact us at admin@pay2allservices.com. We will assist the organization with verified deletion requests where appropriate.

3.6 Choice and consent

Before first enrollment, the app explains that the face is used to verify check-in and check-out. Capture begins only after the user taps Start face scanand grants the operating system's camera permission. A user may decline camera access. If an employer requires face attendance, the employee should contact that employer about any available alternative attendance method.

• Provide, operate, maintain, and secure the CRM and its public pages.
• Authenticate users, enforce roles and permissions, prevent abuse, and troubleshoot incidents.
• Store and organize business records, generate documents, and carry out actions requested by users.
• Connect user-selected services such as Gmail and Google Drive.
• Respond to support requests and send essential service communications.
• Improve reliability and functionality using aggregated operational information.
• Comply with applicable law and enforce our agreements.

Gmail is optional. When you choose Connect Gmail, 2All requests permission to identify the connected Google account and send email through that account. The requested Gmail permission is gmail.send. We do not request permission to read, search, download, or delete your Gmail inbox.

We store the connected email address and encrypted OAuth access and refresh tokens so the connection can work. When you direct the CRM to send an email, the recipient, subject, message, and any selected attachment or secure proposal link are transmitted to Google for delivery. The CRM may record the recipient, subject, delivery event, and linked CRM record in its activity timeline.

Google user data is used only to provide the user-facing Gmail sending feature. We do not sell Google user data, use it for advertising, use it to determine creditworthiness, or allow people to read it except when necessary for security, support with your consent, legal compliance, or service operation. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

You can disconnect Gmail from CRM settings at any time, which deletes the stored connection tokens from the CRM. You can also revoke access from your Google Account security settings. Revocation does not remove emails already sent or ordinary CRM activity records retained by your organization.

If your organization enables an AI provider, the CRM may send the instructions and relevant deal, customer, company, product, or pricing context needed to generate a requested draft. AI-generated proposals remain editable and should be reviewed before use. Your organization selects and configures the provider, and that provider processes the data under its own terms and privacy policy.

We may share information only as needed with:

• Your organization, its administrators, and users according to configured permissions.
• Hosting, database, email, file storage, authentication, monitoring, and support providers working for us.
• Integrations you or your organization deliberately enable, including Google and configured AI or payment providers.
• Authorities or other parties when reasonably necessary to comply with law, protect rights and safety, or investigate fraud and abuse.
• A successor in connection with a merger, financing, reorganization, or sale, subject to appropriate confidentiality protections.

We do not sell personal information or Google user data.

We retain information while an account or organization is active and as needed to provide the service, satisfy legal and accounting requirements, resolve disputes, prevent abuse, and enforce agreements. Retention can vary by record type and organization settings. Authorized users may delete many CRM records and disconnect integrations in the product. For an account or privacy request, contact us at admin@pay2allservices.com.

We use safeguards designed to protect information, including encrypted transport, protected authentication cookies, role-based access controls, secret encryption, and access restrictions. No service can guarantee absolute security. Keep your credentials confidential, use available multi-factor authentication, and notify us promptly of suspected unauthorized access.

Subject to applicable law, you may request access, correction, deletion, restriction, portability, or objection regarding your personal information, and may withdraw consent where processing relies on consent. If an organization controls the CRM record, contact that organization first; we will assist it where appropriate.

You can manage integration permissions in CRM settings, revoke Google access through your Google Account, and control browser cookies through browser settings. Blocking essential authentication cookies may prevent the service from working.

The service is intended for businesses and authorized adult users. It is not directed to children, and we do not knowingly collect personal information directly from children through account registration.

We may update this policy to reflect changes to the service, law, or our practices. We will update the date at the top and provide additional notice when appropriate. Questions, complaints, and privacy requests can be sent to admin@pay2allservices.com.