Status of this draft privacy notice

Not yet in force. This draft does not yet govern how SmartCompaire handles personal data. Until it is approved, the SLRIS privacy policy on slris.com applies. [To be confirmed by SLRIS legal: that the SLRIS privacy policy covers SmartCompaire until this notice is approved.]Read the SLRIS privacy policy
Placeholders. Text in [square brackets] marks a fact or decision SLRIS has not yet confirmed. Nothing in a placeholder is a commitment.

Who we are and what this privacy notice covers

SmartCompaire is operated by SLRIS Solutions, LLC (“SLRIS”, “we”). It compares payroll and time data between a source and a target system during parallel testing, and includes Hirra, an AI assistant in beta. Registered address: [to be confirmed by SLRIS legal].

Once approved, this notice is intended to cover the SmartCompaire web app and these public pages. SLRIS’s company-wide privacy policy (https://www.slris.com/privacy-policy/) covers its other sites and services. [To be confirmed by SLRIS legal: which document prevails if they differ.]

Customers are the organizations that use SmartCompaire. Each customer decides what payroll data to upload. [To be confirmed by SLRIS legal: whether SLRIS processes that data on the customer’s behalf, the controller and processor roles, applicable data processing terms and legal bases.]

Account data

Profile. Email address, full name, time zone, avatar image address and account status.
Password. A bcrypt hash of your password, never the password itself. Accounts that sign in only with Google have no password.
Google sign-in. Your Google account ID, email, whether Google verified it, Workspace domain, name and profile picture address. We request only the openid, email and profile scopes.
Membership and invitations. Your organizations, your role in each and any individual permission changes. For invitations we keep the invitee’s email and role, and only a hash of the invitation token.
Sign-in security. Last login, failed sign-in count, lockout time and the date your password last changed.

Customer payroll data processed on your behalf

Data comes in as uploaded spreadsheets or CSV files, typed rows or pasted rows. SmartCompaire has no live connection to any payroll or time system.

Pay data. Source and target employee numbers, payroll area and periods, check date, tax authority and pay codes with descriptions, and number, rate, amount, MTD, QTD and YTD figures.
Project and review work. Mappings, thresholds, status rules, comparison results, statuses, defects, KD/AD records and free-text comments.
Original files. Uploaded files are kept as uploaded, including columns SmartCompaire does not import. The data model has no fields for employee names, national IDs, dates of birth, addresses or bank details, so we recommend removing those columns before upload.
Email settings. If admins configure an SMTP server for invitations, its password is encrypted before storage and never returned by the API.

Usage and technical data

Sessions. The IP address and browser user agent of each signed-in session.
Audit log. Sign-ins and failed sign-ins, organization switches, password, role and permission changes, invitations, member removals and project changes. Each entry records who acted, the action, the affected record and the time. Sign-in and session events also record the IP address and browser user agent. Some entries also record the changed values.
Contact requests. If you leave your details, on the Request a demo page or when sign-in or sign-up is refused: your name and email, any company, phone and message you add, and the IP address and browser user agent of the request. Only SLRIS platform administrators can see them. [Retention of contact requests to be confirmed by SLRIS.]
Job records. For each import, run or report: who started it, when, which file and row counts.
AI records. Your Hirra conversations, and a record of each action Hirra attempts with sensitive values masked, token use, cost, IP address and user agent.

How we use data

To run the service. Signing you in, applying permissions, importing files, running comparisons and producing reports.
To send invitations. Only through the SMTP server your organization configures. Without one, no email is sent and the inviter shares the link.
To keep accounts secure. Locking an account for 15 minutes after 8 failed sign-ins, detecting reuse of a replaced sign-in token, and keeping the audit log.
To provide AI features. Answering Hirra questions, carrying out the actions Hirra takes for you, and generating AI Insights reviews.

AI processing in Hirra

Comparison results come from fixed matching and threshold rules, not AI. Hirra reads and explains results and is labeled “in beta and can make mistakes”.

Within your permissions, Hirra can also create projects, defects and KD/AD records, update review fields on result rows, generate reports and cancel jobs without a further confirmation step.

Typed questions go only to the SmartCompaire backend. The backend passes them to our Corra AI service, which sends them to OpenRouter, a third-party model router. API keys stay on our servers.

OpenRouter’s Auto router chooses the model, and so the model provider, for each chat turn. Unless SLRIS restricts the model list, that can be any provider OpenRouter offers. [Currently configured fallbacks, to be confirmed: Anthropic, OpenAI and Google models.]

The model receives your question, up to the last 20 messages of the conversation, your role, your organization’s ID, the name of the project you have open, and the results of data reads Hirra makes with your own permissions.

Those read results can include pay rows with employee numbers and amounts (up to 200 rows per read) and are not redacted; masking applies only to our logs, audit records and stored AI Insights text. Hirra never receives uploaded files.

AI Insights makes one model call containing a run’s totals and breakdowns, including the 15 employees (by employee number) and pay codes with the largest differences, the run trend, defect counts, thresholds, and run and project details.

Our requests to OpenRouter set no zero-data-retention or no-training option, so OpenRouter’s and each model provider’s own terms govern what they keep. [To be confirmed by SLRIS legal: the provider terms that apply.]

Voice input uses your browser’s built-in speech recognition, so your speech goes to the browser vendor’s speech service and the vendor decides where it is processed.

The talking avatar is off by default. When you turn it on, your browser sends Hirra’s reply text directly to HeyGen and LiveKit to be spoken; that text can include figures and employee numbers from your data.

[International transfers, and the regions where OpenRouter, model providers, HeyGen and LiveKit process data, to be confirmed by SLRIS legal.]

Third parties that receive data

The outside services the code sends data to. [Formal subprocessor list and contract terms to be confirmed by SLRIS legal.]

Amazon Web Services

Hosts the web app (AWS Amplify) and file storage (Amazon S3). [API, database and AI service hosting to be confirmed by SLRIS.]

OpenRouter and model providers

Receive Hirra prompts and data read results, only when someone uses Hirra. OpenRouter chooses the model provider for each chat turn.

Learn more

HeyGen and LiveKit

Receive Hirra’s reply text, which can include figures and employee numbers, only while avatar mode is on.

Your browser vendor

Processes your speech when you use voice input in Hirra. Your browser, not SmartCompaire, decides where.

Google

Google sign-in, if you use it. Your browser loads the site’s font from Google Fonts.

Your SMTP server

Chosen by your organization’s admins, including its encryption setting. It carries invitation emails, so whether they are encrypted in transit depends on that setting.

Where data is stored and how it is protected

Location. Stored data sits in one AWS region, set by a server setting; the default in code is us-west-2. [Deployed region to be confirmed by SLRIS.] Customers cannot choose a region. AI and avatar providers process data outside this setting, as described under AI processing.
Separation. Database row-level security limits normal app requests to the caller’s organization, and a query with no organization set returns no rows. Sign-in, background jobs and SLRIS administration bypass it and filter by organization in code.
Encryption. Your browser connects to SmartCompaire over HTTPS with HSTS. [Encryption of internal service-to-service and database connections to be confirmed by SLRIS.] Uploaded files and error reports use S3 server-side encryption (AES-256); generated reports and exports rely on the bucket’s default encryption. Pay data is not encrypted field by field. [Database encryption at rest to be confirmed by SLRIS.]
Downloads. Download links expire after 15 minutes and are issued only after checking the file belongs to your organization.
SLRIS staff access. SLRIS platform administrators can see data in every organization, including user lists and the platform audit log. Switching into an organization is written to the audit log; individual reads by administrators are not. [Staff access controls to be confirmed by SLRIS.]Learn more

Cookies, analytics and browser storage

SmartCompaire does not use cookies and loads no analytics or tracking scripts.

Session storage holds your access token, refresh token and current Hirra conversation ID; they are cleared when you sign out or close the tab. Local storage holds only your theme and whether the sidebar is collapsed.

Retention and deletion

Timers. Download links last 15 minutes, invitations expire after 72 hours by default and are then marked expired, reports are marked expired after 14 days, and expired sessions are deleted 30 days after expiry.
No automatic deletion. Pay data, mappings, results, uploaded files and Hirra conversations are not deleted automatically.
No deletion in the product. Uploaded files, import error reports (which hold the original cells of rejected rows), exports, report files and Hirra conversations cannot be deleted from inside SmartCompaire. [Deletion on request, including stored files, and its timing: process to be confirmed by SLRIS.]
Project deletion. Admins can permanently delete an archived project by typing its name. This removes its mappings, pay data, runs, results, defects, KD/AD records, reports and jobs from the database. Its Hirra conversations and AI action records are kept, and its files stay in storage. Admins can also clear one dataset, which removes its rows but not its files.
Audit logs. The database rejects edits and deletions of audit and AI action records, and they remain after the records they describe are removed.
End of contract. [Retention periods after a customer leaves to be confirmed by SLRIS legal.]

Your rights and how to make a request

If you sign in with a password, you can change it in the app (there is no self-service reset). You can also sign out of every device. Admins can remove members, which ends their sessions, delete projects and clear datasets. Reports and the results grid can be exported.

There is no self-service way to delete your account, delete an organization or export all of an organization’s data. Send those requests, and any request to access, correct or delete personal data, to the contact below. [Rights by jurisdiction and response times to be confirmed by SLRIS legal.]

[To be confirmed by SLRIS legal: if a customer uploaded your pay data, whether that customer controls it and should be contacted first, and how SLRIS handles requests it receives directly.]

Contact

SLRIS Solutions, LLC. Privacy email: [to be confirmed]. Data protection officer: [to be confirmed]. Postal address: [to be confirmed].Contact SLRIS
Company-wide policy. SLRIS’s privacy policy for its other sites and services.SLRIS privacy policy
Governing law and changes. [Governing law, and how customers are told about changes to this notice, to be confirmed by SLRIS legal.]

See SmartCompaire on your own payroll data

Bring a source and a target extract from your parallel run; we will walk through the comparison with you.

Request a demo