1. Who this covers, and our two roles

9forty5 is operated by Temporal Logic LLC d/b/a Temporal Logik, a Texas limited liability company. This policy applies to the 9forty5 web application and its APIs.

We handle two kinds of information in two different roles, and the distinction matters:

• Account information: the business that subscribes, its billing details, and the person who administers the account. Here we act on our own behalf (as a "controller" or "business").
• Employee information: the records an employer enters or generates about its workforce. Here we act on the employer's instructions (as a "processor" or "service provider"). The employer, not Temporal Logik, decides what to collect, who may see it, and how long to keep it. If you are an employee and want your records corrected or deleted, start with your employer; we will support their instructions.

2. What we collect

Account and billing. Company name, plan, subscription status, billing tier, and the identifiers our payment processor assigns to your customer and subscription records. We do not receive or store full card numbers. Those go directly to Stripe.

Employee records. First, middle, and last name; work email; up to two phone numbers; mailing address; hire date; assigned site and department; role; an optional external payroll identifier; and, if the employer chooses to enter it, Social Security number. Employers may also record wage or salary rates with effective dates.

Time and schedule data. Clock-in and clock-out times; the site and department each punch belongs to; punch type; calculated time cards and their hour classifications; time-off requests, approvals, and balances; scheduled shifts and assignments; and time card submission and approval status.

Location, when enabled. If the employer enables it and the employee's browser provides it, a punch may record latitude, longitude, and an accuracy radius, plus a flag for whether the punch fell outside the site's geofence. Location is captured only at the moment of a punch. The Service does not track location continuously or in the background. It is left empty when the browser reports nothing, for example because permission was denied or no fix was available.

Authentication. Passwords are stored only as bcrypt hashes and are never recoverable. If passkeys are used, we store the credential's public key and identifier; biometric data never leaves the employee's device and is never sent to us.

Activity records. An activity log recording actions taken in the Service: who, what, when, and which endpoint. It is used for audit and troubleshooting.

Technical data. Ordinary server logs generated by operating a web service, including IP address, timestamps, and error diagnostics.

3. What we do not do

To be specific about the things a privacy policy is usually vague about:

• No analytics or advertising trackers. The application loads no third-party analytics, tag manager, session recorder, advertising pixel, or social widget. There are none to disable.
• No sale or sharing of personal information as those terms are defined under the California Consumer Privacy Act, and no cross-context behavioral advertising.
• No model training on your data. We do not use identifiable Customer Data to train machine learning models, and our AI provider does not train on data submitted through its API.
• No advertising cookies. See section 4.

4. Cookies and local storage

9forty5 does not use cookies. Your session token is held in your browser's local storage, along with two interface preferences: whether the navigation sidebar is collapsed, and whether you have chosen light or dark mode. None of it is used for tracking, none is shared, and clearing your browser storage signs you out and resets those preferences. Because we set no non-essential cookies, there is no consent banner.

5. How we use information

• To provide the Service: authenticate users, record punches, calculate time cards and overtime, manage schedules and leave, and generate payroll exports.
• To bill for paid plans and to enforce plan limits.
• To send transactional email: account verification, password resets, and notices about your account. We do not send marketing email to employees.
• To secure the Service: detect and investigate abuse, fraud, and unauthorized access, and maintain the audit log.
• To provide support you request, and to diagnose faults.
• To comply with law and to establish or defend legal claims.

6. Who we share it with

We share personal information only with the service providers below, each bound to protect it and to use it only to provide their service to us:

• Amazon Web Services: hosting, database, and file storage. Data is stored in the United States.
• Stripe: payment processing for paid plans. Stripe receives billing details directly; we receive only identifiers and subscription status.
• Amazon Simple Email Service: delivery of transactional email.
• Anthropic: the large language model behind the AI-assisted features. See section 7 for exactly what is sent.

We may also disclose information if required by law or valid legal process, to protect our rights or the safety of others, or in connection with a merger, acquisition, or sale of assets, in which case we will give notice before your information becomes subject to a different policy. We do not otherwise disclose personal information to third parties, and we do not sell it.

7. AI-assisted features: what is and is not sent

The Service can answer questions about your operational data using a large language model operated by Anthropic. When a manager asks such a question, the question and the results of a fixed set of read-only queries are sent to Anthropic's API. Those results can include employee names, hours worked and how they were classified, overtime, attendance and punctuality, scheduled versus actual hours, leave taken and upcoming absences, headcount, and labor cost including wage-derived figures.

The following are excluded by design and are never sent to the model: Social Security numbers, payroll registers, detailed timecard payloads, employee contact information, and the punch audit trail. The set of queries the model can call is fixed in the application. It cannot reach data outside that set, and it cannot write anything.

Anthropic processes this data to return a response and does not use data submitted through its API to train its models. If you would rather no employee data reach a model provider, do not use the AI features.

8. Security

We protect information with measures including:

• Encryption of Social Security numbers at rest, using AES-256-GCM with a per-record nonce and authentication, under a key held outside the application source and outside the database.
• Passwords stored only as bcrypt hashes, never reversibly encrypted.
• Encryption in transit. The Service is served over HTTPS (TLS). Plain HTTP is redirected to it rather than answered, so credentials, session tokens, and employee data do not cross the internet in cleartext. Certificates are obtained and renewed automatically.
• Signed, expiring session tokens with a revocation mechanism that invalidates a user's outstanding sessions.
• Role-based access control, so employees see their own records and managers see only the sites they are assigned to.
• Social Security numbers masked in payroll exports, showing only the last digits.
• A database that is not reachable from the public internet; only the application edge is exposed.

No system is perfectly secure, and we cannot guarantee absolute security. If we become aware of a breach affecting your information, we will notify you as required by applicable law and without undue delay.

9. How long we keep it

Employee records and time data are retained for as long as the employer's account is active, because they are business records the employer is generally required to keep. Deactivating an employee in the Service preserves their historical records rather than deleting them. This is deliberate, so that past time cards and payroll history remain intact and auditable.

After an account terminates, Customer Data remains available for export for 30 days, and we may delete it thereafter. We will delete or return Customer Data sooner on an employer's written instruction, except where we are required to retain it by law. Ordinary server logs are retained on a short rolling basis.

10. Your rights

Depending on where you live, you may have rights to know what personal information is held about you, to obtain a copy, to correct it, to delete it, and to not be discriminated against for exercising those rights. California residents have these rights under the CCPA as amended by the CPRA; residents of certain other states have comparable rights.

If you are an employee, contact your employer first. They control the records and can act on them directly in the Service. We act on their instructions, and we will forward any request we receive to them.

For account information we hold in our own right, or if you cannot reach the employer, write to legal@temporallogik.com. We will verify your identity before acting and will respond within the time the applicable law allows. We do not charge for these requests.

11. Children

The Service is a workplace tool and is not directed to children. We do not knowingly collect information directly from anyone under 16. An employer may enter records for a lawfully employed minor; where that happens, the employer is responsible for any parental notice or consent that applies and for compliance with child labor law.

12. Where data is processed

The Service is operated from and its data stored in the United States. If you access it from elsewhere, you are transferring information to the United States, where privacy law differs from your own jurisdiction's. The Service is not currently offered to customers in the European Economic Area or the United Kingdom, and we make no representation about GDPR compliance.

13. Changes to this policy

We may update this policy. Material changes will be announced by email to the account address, by notice in the Service, or both, at least 30 days before they take effect, and the version and effective date on this page will change. We will not materially reduce the protections that applied to information already collected without your consent.

14. Contact

Privacy questions and requests: Temporal Logic LLC d/b/a Temporal Logik, legal@temporallogik.com.