Effective date: [EFFECTIVE DATE]
This Privacy Policy explains how [JANNIE LEGAL ENTITY NAME] (“Jannie,” “we,” “us”) handles personal information through the Jannie website, business platform, mobile attendance experience, and related services.
1. Our role
Jannie is a B2B service. For workforce, customer, location, attendance, payroll-input, billing-input, and evidence records, the business that uses Jannie generally determines why and how the information is used. That business is the Customer and Jannie processes the information on its behalf.
Jannie may separately determine how it handles business contact details, website interactions, account security, support requests, product analytics, billing records, and its own legal compliance.
Workers should first contact the company that engaged or employed them about workforce records or employment-related questions. Jannie is not the employer and does not determine employment consequences.
2. Information we collect
Depending on Customer configuration and a user’s role, Jannie may collect:
- Identity and contact data: name, email, telephone number, mailing address, internal worker code, organization, role, and login identifiers.
- Tax-profile data: Social Security number, ITIN, EIN, tax classification, and related profile fields entered by a worker. Jannie does not treat these entries as a completed or certified tax form.
- Banking data: bank name, account type, routing number, and account number used to prepare Customer-controlled direct-deposit records and NACHA files.
- Workforce and operational data: employee or contractor status selected by Customer, location assignments, schedules, service information, attendance status, clock-in and clock-out times, approved rates or amounts entered by Customer, exceptions, notes, and audit history.
- Precise location: latitude, longitude, timestamp, and reported accuracy collected only when a user initiates clock-in or clock-out. Jannie does not continuously track a device.
- Evidence: photographs of arrival, work areas, completed work, receipts, tickets, or other Customer-configured evidence. Users must avoid capturing faces or unrelated personal information.
- Client, location, payroll-input, and billing-input data: Customer business contacts, service locations, approved operational totals, invoice data, payment-status records, and downloaded-file metadata.
- Technical and security data: IP address, device/browser information, authentication events, error logs, audit logs, and security signals.
- AI and support data: questions submitted to Jannie AI, generated responses, feedback, support requests, and communications. Restricted sensitive data is not intended to be included in AI prompts.
- Marketing data: business contact information, communication preferences, campaign engagement, and opt-out records.
[LAUNCH BLOCKER: the current product requests an identification photograph. Decide whether to remove it or add a specific, lawful purpose and disclosure before publication.]
3. Sources
We receive information directly from workers and business administrators; from the Customer that invited or configured a user; automatically from devices when a user performs an action; and from subprocessors that help provide authentication, hosting, security, email, support, and AI functionality.
4. How we use information
We use information to:
- provide, secure, maintain, troubleshoot, and support Jannie;
- authenticate users and enforce organization and role boundaries;
- record attendance and operational evidence requested by Customer;
- organize Customer-approved payroll and billing inputs;
- generate a NACHA-formatted file for Customer review and download;
- answer authorized operational questions and identify possible anomalies;
- communicate about accounts, security, service updates, support, and lawful B2B marketing;
- maintain audit trails, prevent abuse, respond to incidents, and enforce agreements; and
- comply with law and protect rights, safety, and service integrity.
Jannie does not use workforce information to classify workers, determine fraud, make employment decisions, calculate legal pay obligations, or autonomously modify Customer records.
5. Artificial intelligence
Jannie uses OpenAI’s API to generate limited operational responses. Jannie’s approved design excludes the following from OpenAI requests: SSN/TIN, bank account and routing numbers, dates of birth, photographs, exact coordinates, NACHA files, and tax forms. Users must not enter that information in AI prompts.
Names, internal codes, generic location labels, attendance summaries, and other limited operational data may be processed when necessary to answer an authorized question. Under OpenAI’s current API data controls, API input and output are not used to train models by default unless Jannie affirmatively opts in. OpenAI may retain limited abuse-monitoring logs under its applicable terms and settings.
6. Disclosures and providers
We disclose information only as needed:
- to the Customer and users authorized by that Customer;
- to contracted providers of hosting, content delivery, database, storage, authentication, security, email, and artificial intelligence services;
- to professional advisers, auditors, insurers, and authorities when reasonably necessary; and
- in a merger, financing, acquisition, or sale, subject to appropriate confidentiality and notice obligations.
Our subprocessors process information on Jannie’s behalf under contractual privacy and security obligations. Microsoft Clarity has a different role, described below and separately in our Subprocessors and Other Providers list.
Attendance diagnostics with Microsoft Clarity
On the production app’s clock-in and clock-out pages only, including Spanish pages, Jannie starts Clarity when the page opens to diagnose browser, permission, upload, and connectivity problems, even if no error occurs. It does not load on attendance login or panel, staff, client portal, operations, or the public website.
Clarity collects page interactions (such as taps, scrolling, and timing), masked page structure for session replay when available, browser/device and performance information, and technical markers for page opening, submission, completion, and failure categories. Microsoft receives the connection IP address and may derive approximate location. This is separate from the precise GPS used by Jannie for attendance.
The contractor UUID is passed only to Clarity’s Identify API, which hashes it in the browser before transmission. The existing short reference, such as CDAB3, is a readable label and search tag. It can match multiple contractors; the full UUID is the authoritative custom ID. These identifiers let authorized support correlate diagnostics with a contractor and are not anonymous, even without cookies.
Jannie applies Strict masking and explicitly masks the page. The integration excludes names, phone numbers, PINs, tokens, exact GPS, photographs, location IDs, request/response payloads, and raw backend error text from its Clarity instrumentation. It sends only predefined custom events with no error details. URLs with parameters/fragments or unsafe referrers are reloaded to a clean clock page before Clarity loads. Masking preserves layout and interaction signals; it is not a claim that no personal data is processed.
Clarity cookies are disabled and both advertising and analytics storage consent signals are denied. Collection still starts on opening the page; cookie denial is not an opt-out from all diagnostics. Replay and continuity may be limited, particularly in the EEA, UK, and Switzerland. See our Cookie Notice.
Under the Clarity Terms, Jannie and Microsoft are independent controllers; Microsoft is not Jannie’s processor or subprocessor for Clarity. Microsoft collects or receives personal data to provide Microsoft Advertising and may also use data for its own product improvement and other purposes described in the Microsoft Privacy Statement. Cookies Off does not replace those terms. Jannie uses these diagnostics for troubleshooting, not employment decisions or advertising.
Access to Jannie’s Clarity project is intended for authorized support/engineering personnel who need it to investigate a problem. Microsoft also processes the data under its own terms. Requests about Jannie’s use may be sent to contact@jannie.app; Microsoft’s statement explains its own privacy choices and requests. Processing may occur in the United States and other countries where Microsoft operates.
Clarity’s published retention is 30 days for playback, 9 months for labeled or favorited sessions, and 9 months for heatmap/click data. This is separate from the operational-record retention below. Jannie’s operating policy is to avoid labeling/favoriting recordings unless extended retention is needed for a documented investigation; these periods are not a configurable 30-day limit on all Clarity data.
7. Retention
For active Customer accounts, the standard service is designed to retain a rolling history of up to four years, unless Customer selects a shorter period or law/contract requires another period. Certain security, consent, dispute, and transaction records may be retained longer when reasonably necessary.
After Customer termination, Customer generally has 90 days to export data. Jannie may then delete data from active systems and allow encrypted backups to expire under normal rotation. A Customer may purchase a separate read-only archive. Workers should request employment or tax copies from the Customer, which is responsible for its legally required records.
Jannie retains marketing opt-out records as needed to honor the opt-out. AI conversation history and high-risk evidence should use shorter periods where operationally feasible and documented in the Retention Policy.
8. Security
We use reasonable safeguards designed for the nature of the data, including organization isolation, role-based access, encryption, masking of sensitive fields, audit logging, restricted administrative access, secure development practices, vendor review, backups, and incident response. No service can guarantee absolute security.
9. Choices and requests
Depending on applicable law and Jannie’s role, individuals may request access, correction, deletion, or a copy of personal information. For workforce records, submit the request first to the Customer that employed or engaged you. Jannie will assist Customer as required by contract and law.
For information Jannie controls directly, contact contact@jannie.app. We may need to verify identity and authority. Some information may be retained where legally permitted or required.
Users can disable device location permission, but the Customer-configured digital clock-in or clock-out cannot be completed without the required point-in-time location. The Customer is responsible for any alternative process and employment-related response.
Marketing recipients may opt out using the unsubscribe link or by emailing contact@jannie.app. Transactional and security messages may still be sent.
10. Children and restricted sectors
Jannie is for adults and is not directed to anyone under 18. We do not knowingly provide the service for minors. Jannie is not approved for health-care providers, schools, or government entities without a separate written compliance review.
11. U.S. processing
Jannie is operated for U.S. businesses. Information may be processed in the United States and in other locations where approved providers operate, subject to contractual and legal safeguards.
12. Changes
We may update this Policy prospectively. If a change materially expands how we use information, we will provide clear notice and obtain authorization where required rather than relying only on a silent policy update.
13. Contact
Privacy: contact@jannie.app
Security incidents: contact@jannie.app
Mail: [JANNIE LEGAL ENTITY NAME], [BUSINESS ADDRESS]