Gather Time Clock privacy policy
Effective September 23, 2026. Applies to the Gather Clover time clock and connected employee timecards.
Who operates Gather
Maximilian Anthony Reyes, operating as Gather, provides this service. Contact details are below. This policy covers employee timekeeping, not Gather’s separate donation, customer-club or messaging features. Your employer chooses to use Gather and controls its store’s employment records.
Information we process
- Existing Gather employee account information: name, email, store and membership identifiers, assigned roles, account status, hire date and store timezone.
- Timekeeping records: clock-in and clock-out timestamps, associated employee, store and terminal, and calculated elapsed time.
- Security information: hashed PIN verification data, pairing records, encrypted terminal credentials, short-lived authorization tickets, duplicate-request records and audit events.
- Information you provide to support and connection information needed to operate and secure the service. Hosting systems may generate access and error logs, including network information such as IP addresses.
The first Clover release does not read Clover employee records, orders, payment-card data or loyalty balances. It does not request contacts, microphone, GPS or biometric access.
Purposes and access
We use employee information to authenticate staff, record and display timecards, calculate elapsed hours, prevent duplicate punches, provide support and secure the service. Store owners and authorized managers can view their store’s timecards; employees can view their own. A shared terminal briefly displays the identified employee’s name and clock status, which may be visible to people nearby.
Hosting and database providers process information to operate the service. Gather uses Render for hosting; database configuration may use a separately hosted private PostgreSQL database. Access by Gather’s operator and service providers is limited to providing, maintaining, securing and supporting the service. We may disclose records at the store’s authorized direction or where required by law.
We do not sell or share employee timekeeping information for cross-context behavioral advertising, use it for unrelated advertising, or combine stores’ employee records for unrelated commercial profiling. We process employer-controlled records to provide the agreed service and compatible operational purposes.
Retention
We preserve timecards for four years from the shift date, including after a store stops using Gather. Authorized stores can request copies during this period. Records subject to a legal hold or another applicable preservation obligation are retained longer. Open or unresolved shifts are reviewed before deletion. At the end of the retention period, Gather reviews records for removal; this is an operator-managed process, not deletion immediately at an anniversary.
Removal includes associated stored punch-response copies and punch audit snapshots in the active database. Security, account, support and infrastructure records may have different lifecycles and are retained only as needed for the service, security, requests or legal obligations. Backup copies follow the applicable backup lifecycle and may not disappear at the same moment as active records. Restricted backup data is not used for ordinary operations; if restored, deletion and preservation decisions must be reapplied before normal use.
Requests and offboarding
Employees should contact their employer about attendance errors and employer-controlled records, and may also contact Gather using the details below. We verify identity and authority, coordinate employer instructions and respond as required by applicable law. A store leaving Gather can request a copy of its retained timecards through support. Deactivating an employee, revoking a terminal or uninstalling the app does not erase historical timecards. Deletion requests are evaluated against recordkeeping and legal-hold obligations.
Security and device storage
The production terminal uses HTTPS, encrypted device credentials and server-side access controls. PIN verification data is hashed. The terminal does not keep an offline punch queue. The web interface uses authentication cookies and no advertising tracking is part of the time-clock client. No system is perfectly secure; protect your PIN and report suspected unauthorized access.
Policy changes
We publish updates here with a revised date and provide additional notice or obtain consent when required. Contact Gather with questions about this policy or your information.