akordion

Privacy Policy

Last updated: November 5, 2026

This policy explains how Akordion handles account, crew and job information, including location and optional punch photos. The employee notice gives workers a shorter explanation of the time clock.

1. Who handles your information

Akordion is a crew time-tracking service operated from Alberta, Canada, under the public-facing name Akordion Inc. Employers decide which workers, sites and business records to add and how to use those records for their employment and business purposes. Akordion processes that information to provide, secure and support the service. We also handle account and security information for our own service operations.

Alberta’s Personal Information Protection Act and other applicable privacy laws govern how information is handled. An employer’s responsibilities depend on its organization and activities.

2. Information in the service

Account information includes names, email addresses, password verifiers and company details. Employers may add worker names, optional email addresses, pay rates, job assignments, business contacts, site addresses and other information needed to use the available features.

Work records include clock-in and clock-out times, sites, break times, applicable rate snapshots, allowances, corrections and their audit history. Company clock notices and acknowledgement receipts may also be recorded.

Where location is available, a punch may include coordinates, distance from the site and reported accuracy. We retain the resulting location status and, where relevant, the technical reason the reading was unavailable or inconclusive, such as permission declined, timeout or imprecise location. This is only a short label; it is not a movement history.

If the employer enables punch photos, workers can add a photo at clock-in or clock-out. Photos are reviewed by people; Akordion does not perform facial recognition or create faceprints.

Security records include authentication, failed access attempts, acknowledgements and other security-relevant events. Application security events use an IP-derived hash rather than recording the raw IP address in that field. Hosting and other service providers necessarily process network requests as described below.

3. How location works

When a worker agrees to the clock notice, the browser may request location immediately. It may continue requesting and refreshing location while the authenticated clock menu is visible. These readiness readings remain in browser memory; they are not uploaded as a movement history. The location watch stops when the menu closes or the tab becomes hidden.

Clock-in, clock-out and site-switch actions may send one available reading with that action. A recent browser reading may be used. Starting or ending a break records its time without attaching coordinates or a photo.

The service compares usable location with the selected site to help an employer review a punch. A reading cannot establish how long someone worked. Missing or inconclusive location is recorded as unknown; an off-site or unknown result does not by itself stop a punch or determine whether time is payable.

Akordion does not provide continuous background route tracking or a live map of worker movements.

4. Why information is used

We use information to operate accounts and the crew clock, prepare time and job records, support employer review and corrections, generate reports and exports, secure the service and respond to support requests.

Password recovery and other service messages use the relevant email address. Optional activity summaries use counts and review flags rather than worker names, wages, exact punches or coordinates.

We do not sell personal information or use it for advertising. We do not build commercial data products from company information or use customer information to train an Akordion model. Optional AI provider processing is explained in Section 6.

5. Notice and choices

Employers must give appropriate notice and have a lawful, reasonable basis for collecting and using worker information. An acknowledgement in the app does not replace those responsibilities.

The clock requires acknowledgement of the current notice before location-capturing punch actions. Browser location permission is separate: declining it still permits a punch with location unknown after acknowledgement. Workers who do not wish to acknowledge the notice should ask their employer how to record their time another way.

The printable Employee notice explains these practices for workers. Employers should also explain their own purposes, authorized access and selected retention period.

6. Providers and processing outside Canada

Our provider list explains each provider’s purpose, information handled and location.

On a small screen, scroll the table to read every column.

ProviderPurposeData it touchesRegion
SupabaseDatabase (Postgres) — the primary data storeAll application data: accounts, workers, punches, GPS coordinatesCanada (AWS ca-central-1)
VercelHosting and serverless computeAll application request and response traffic in transitUnited States (global edge network)
Vercel BlobPrivate file storageReceipt images and clock-in/out punch photos. Stored privately — a file URL alone will not open one; every fetch is authenticatedUnited States
UpstashRate-limit store (Redis)Hashed IP addresses and hashed emails used as rate-limit countersUnited States
SentryError monitoringError reports and diagnostic context from app failuresUnited States
ResendTransactional emailRecipient email address and service-email content, including password-reset links and activity-only daily crew summaries when enabledUnited States
Zoho MailSupport mailboxSender and recipient addresses, support message bodies and attachmentsCanada (mailbox data centre)
OpenStreetMapAddress lookup (geocoding) when an account owner saves a job siteThe site address typed into the form, sent once to turn it into map coordinates. No employee data, no punches, no account identifiersEurope (OpenStreetMap Foundation)
OpenRouterOptional owner/admin AI explanations — job questions and, only when separately enabled, a weekly payroll-close briefA job question sends the on-screen job figures (customer name, service, quoted amount, profit, labour cost, budget burn) plus the typed question. A close brief sends only completed-period label, deterministic close status, worker and closed-punch counts, payable allowance-day count, and grouped exception counts. The close brief never sends employee names, identifiers, exact punches, hours, wages, allowance amounts, coordinates, photos or credentialsUnited States

The primary database is hosted in Canada. Some supporting processing occurs outside Canada, where information may be subject to local law and lawful access. Ask the Akordion privacy contact identified with your account for our practices concerning service providers outside Canada.

When an operator authorizes a support task, selected correspondence may be processed through Composio and OpenAI Codex. This is not automatic inbox monitoring. Message details and attachments needed for the task may be processed outside Canada, under the providers’ applicable account settings and retention and data-use terms.

Optional owner and administrator AI features send the information described in the table when the feature is used. Job questions can include customer and job figures plus anything typed into the question. The separately enabled weekly-close brief uses limited aggregate inputs. Workers do not have an AI feature in the time clock.

OpenRouter forwards requests to model providers. Provider handling depends on the applicable provider terms and configured routing; we do not promise that every provider request has no retention or training use. Avoid putting unnecessary personal information into a question, and check an answer before relying on it.

7. Retention and deletion

Time, payroll, business and audit records remain while the company account exists unless a supported deletion removes them. Employers should keep information only as long as reasonably needed and retain required employment records independently when necessary.

The company’s location and photo retention setting defaults to 12 months and can be set from 1 to 60 months. This sets the cleanup window for coordinates, distances, accuracy values and punch photos in active records. Removal depends on the cleanup process running; contact us for the current cleanup schedule. Punch times, hours, location status and technical reason labels remain with the work record.

Account deletion removes the company’s active database records and associated stored files. Export needed records first. This does not erase copies already downloaded by an employer or recipient. Backups, security records and provider-held copies may have separate retention periods; contact us for the applicable practices.

8. Access, corrections and exports

Workers should normally ask their employer for access to their information or correction of an error. Employers can review records and make supported audited corrections. A request to delete information may be limited by legitimate recordkeeping requirements.

An owner can download a company JSON export containing its supported records and excluding credentials. Image entries may be marked unavailable or omitted from the embedded bytes because of the export size budget. Check the export and request help obtaining any required records or files that are not included.

Contact the Akordion privacy contact if you need help or cannot resolve a request with the employer. We may verify identity and authority before providing information.

9. Security and incidents

We use measures including encrypted transport, private file access, tenant-scoped application queries, access controls and rate limiting. Passwords and crew PINs are stored as one-way verifiers. A forgotten credential must be reset.

No service can promise absolute security. If an incident occurs, we investigate, contain it and make notifications and reports required by applicable law. Employers remain responsible for their own accounts, devices, exports and authorized users.

10. Cookies and browser storage

Akordion uses authentication and security cookies and functional browser storage, including session coordination and crew-launch progress. The clock’s short-lived action token and readiness location fixes are held in browser memory.

We do not use advertising cookies or cross-site advertising tracking. Error and performance monitoring helps diagnose service failures.

11. Changes to this policy

The date on this page identifies the latest policy update. We update notices when service practices change. Material changes to the worker notice require renewed acknowledgement in the clock.

12. Questions and complaints

For privacy questions, access requests, corrections, complaints or information about service providers, contact our Privacy Contact at support@akordion.app. Workers can also contact their employer’s designated privacy contact.

If a concern remains unresolved, you may contact the Office of the Information and Privacy Commissioner of Alberta or, where it has jurisdiction, the Office of the Privacy Commissioner of Canada.