Privacy Policy

Attendify Vision is operated by Attendify Vision Technology Solutions L.L.C – S.P.C ("Attendify Vision", "we", "us", "our"), a company registered in Abu Dhabi, United Arab Emirates under commercial licence CN-6081654 issued by the Abu Dhabi Registration Authority (ADRA). The same company operates collectflows.com.

This is the legal entity you contract with when you subscribe, the entity named on invoices, and the counterparty to any data processing agreement.

When a company uses Attendify Vision to record its workforce's attendance, that company is the data controller. It decides which workers are enrolled, which sites are monitored, and whether optional features such as face matching are switched on.

Attendify Vision acts as a data processor for that content: we process it on the customer's instructions and do not use it for our own purposes. For our own account, billing and website data we act as a controller.

The categories of data we hold depend on the role of the person involved.

Attendance, location and verification data are processed to deliver the service the customer has subscribed to: recording attendance evidence associated with a worker and site, calculating configured hours, and supporting human review and payroll handoff. A capture is not proof of continuous presence or a legal/payroll determination.

Location is captured at the moment of check-in and check-out only. Attendify Vision does not track a worker's movements between those events, and there is no continuous location logging in the product.

Face matching is disabled by default and is enabled only for companies that have specifically requested it. Where it is in use, the worker is shown a notice and must give affirmative consent before any template is created. We record which version of that notice they accepted and when.

The enrollment reference is a mathematical descriptor; accepted attendance selfies are stored separately. The reference is held in a table that authenticated client applications cannot query, scoped to the customer's tenant. A company administrator can see whether a worker is enrolled but cannot retrieve the template itself.

An administrator can erase a worker's biometric profile at any time. Doing so deletes the stored template, revokes the consent record, and requires fresh consent and re-enrolment before that worker can be matched again.

Kiosk identification, where a shared device recognises a worker from their face without them first claiming an identity, is a separate processing purpose with its own controls and is gated independently.

Confirm retention arrangements for attendance records, accepted selfies, templates, logs and backups before deployment. A universal customer-configurable retention schedule is not currently promised. An active biometric profile can be reset to remove its template; rejected matching attempts store outcome metadata rather than the rejected selfie on the server. Device-side rejected captures can be removed during terminal synchronization failure.

We do not sell personal data. We share it only with infrastructure providers necessary to run the service — hosting, database, object storage, payment processing, email delivery and, where the optional assistant is enabled, AI analysis by Google Gemini — each under contract and processing only on our instructions. The exception is the advertising measurement and website analytics described below, where Google receives limited website data and processes it under its own policies. Worker records, attendance, location and biometric data are never shared for advertising.

Our website and web dashboard use the Google tag for Google Ads conversion measurement, so we can tell whether a visit from one of our Google ads led to a company creating a workspace and starting its free trial. When a workspace is created we send Google a conversion event carrying an internal workspace identifier, used only to avoid counting the same signup twice. Google also receives standard technical information from the browser, such as IP address, browser details and the pages visited on our site. The mobile worker app does not include this tag.

We also use Google Analytics on our website to understand how visitors find and use it — for example which pages are visited, how visitors arrived and whether they started a free trial. Google Analytics does not run in the mobile worker app, and we have not enabled Google signals, so visits are not linked to visitors' Google accounts. Until you choose "Allow analytics" on our website banner, Google Analytics and Google Ads run without cookies and receive only limited, cookieless signals.

To attribute and measure conversions, Google may set or read cookies and similar device identifiers in your browser. Google processes this data in accordance with its own policies, including the Google Privacy Policy (policies.google.com/privacy) and its description of how it uses information from sites that use its services (policies.google.com/technologies/partner-sites).

Separately from Google, our website keeps its own record, in your browser's local storage, of how you first and most recently arrived at our site: the page you landed on, the website that linked to it (without its query string), any campaign tags in the link and any advertising click identifier. If you then create a workspace, that record and your optional answer to "How did you hear about us?" are stored with the workspace so we can understand which channels bring us customers. We do not share this record with Google or anyone else, and we keep it only while the workspace exists. If you do not create a workspace it never leaves your browser.

We do not currently use Google's enhanced conversions, so we do not send names, email addresses, phone numbers or other customer details, hashed or otherwise, to Google.

Where applicable, you can block or delete cookies through your browser settings, and manage how Google personalises ads for you in Google's My Ad Center (myadcenter.google.com). The dashboard needs its own sign-in cookies to work, so blocking all cookies will stop you from signing in.

Depending on where you live, you may have rights to access, correct, delete, restrict or port your personal data, and to object to processing. Where consent is the applicable basis for processing, withdrawal rights must be addressed. The appropriate grounds and conditions depend on the actual deployment and jurisdiction.

Workers should direct requests to their employer as the controller in the first instance. Where we receive a request directly, we will pass it to the relevant customer and support them in responding.

Questions about this policy or a company’s use of the service can be sent to mudasar@collectflows.com, or in writing to Attendify Vision Technology Solutions L.L.C – S.P.C, Abu Dhabi, United Arab Emirates.