The terms you are agreeing to, written out in ordinary language

Surhires is a hosted recruitment software and applicant tracking system. It is not an HRIS, a payroll system, a background-check provider or an assessment platform. It handles candidate relationships, outbound sourcing, client submittals and the placement pipeline through to the first invoice. Naming the boundary matters commercially, because a firm that buys expecting payroll has bought the wrong thing and the agreement will not fix that.

Licensing is per named user, per month, on one of three tiers. Starter, Professional and Enterprise are provisionally priced at 39, 49 and 99 US dollars per user per month, with annual billing at 32, 41 and 82. Those figures are provisional pending buyer validation rather than a signed-off price sheet, and the order form is what fixes the number you pay. Enterprise carries a platform fee in addition to the seat price.

A named user means a person, not a login shared around a desk. Seats can be reassigned when somebody leaves, which is different from being pooled between two recruiters working the same hours. The distinction is the one most often argued at renewal, so it is worth understanding before you size the account.

The trial is fourteen days and does not ask for a credit card. Nothing converts automatically at the end of it, which means a trial that lapses simply stops rather than quietly becoming a subscription you did not choose. There is no free-forever tier, and that is a deliberate decision rather than an oversight: recruitment software needs imports, onboarding and messaging infrastructure behind it, and an unsupported free account serves nobody well.

Data you load during a trial is yours in exactly the way data loaded during a paid term is yours. If you import three thousand candidates to see whether the parsing holds up and then decide against the product, the export runs the same way it would for a paying customer. A trial that holds your data hostage is a trial nobody should start.

What a trial cannot include is the parts of the service that depend on your own accounts and registrations. Carrier registration for SMS, a WhatsApp Business number and a job board contract are yours to hold, and no trial period changes who is responsible for obtaining them.

The candidate records, client records, notes, message history, documents and everything derived from them belong to the customer. Soor LLC processes that data to run the service you have asked for, and does not sell it, rent it, share it with other customers, or use one customer's candidate database to enrich another. There is no shared talent pool sitting behind the tenant boundary.

Aggregate operational telemetry is a different thing and is worth naming rather than hiding. Counts of API calls, error rates, feature usage and performance metrics are used to run and improve the service. They are not candidate data, they do not identify a candidate, and they are not sold on.

Where models are involved, the position is that your data is processed to serve your request and is not used to train general models offered to anyone else. Model providers appear in the sub-processor register by category, and the terms that govern that processing sit in the data processing addendum rather than in the main agreement.

The acceptable-use rules exist because recruitment software is a sending platform, and a sending platform can be turned into a spam cannon by one customer in an afternoon. The prohibitions are the ordinary ones: no unlawful content, no attempt to break the tenancy boundary, no reselling access, no scraping the service, and no messaging that breaches the sending rules of the jurisdiction you are sending into.

That last one carries the most weight in practice. Consent to contact, opt-out handling, carrier registration and the content of what you send remain the sender's responsibility. The product supplies opt-in capture, suppression lists, keyword handling and a postal address in email footers; it cannot supply the judgement about whether a given campaign is lawful.

Volume limits and fair-use ceilings apply to sending and to API access. They are published rather than discretionary, so a desk that plans a large campaign can size it in advance instead of discovering a ceiling mid-send.

Suspension is not a routine collections tool. It exists for the situations where continuing to run the account creates a live problem: non-payment that has gone unanswered through the stated dunning sequence, a security compromise of the account, sending activity that is generating carrier or abuse complaints, or a legal requirement to stop.

Where notice can be given before suspension, it is given, with what has to change and how long there is to change it. Where the trigger is a live security or abuse event, action can come first and the notice immediately after, because waiting a business day to disable a compromised account is not a defensible choice.

A suspended account is not a deleted account. Access is restricted, the data remains, and restoring it once the cause is resolved is an ordinary support action rather than a recovery project. Deletion only ever follows termination and the retrieval window that comes with it.

Subscriptions run for the term stated on your order form, monthly or annual, and renew on the basis that order form sets out. There is no automatic annual escalator built into the standard terms. Either side can decline to renew with the notice the agreement states, and that notice period is a real term worth reading rather than a formality.

Export is self-service throughout the term. Candidates, clients, jobs, applications, notes, message history and attached documents come out as structured files you can load elsewhere, without raising a ticket and without a professional-services quote. That is a deliberate position: a migration fee charged on the way out is a lock-in mechanism dressed as a service.

After termination the tenant stays retrievable for a defined window before deletion, and the length of that window is stated in the agreement rather than here, because it is exactly the kind of term that changes and the executed copy has to be the one that governs. Ask for it in writing during procurement and keep the answer with the contract.

The service is warranted to perform materially as described in the documentation, and Professional and Enterprise plans carry a 99.9 percent uptime target as a contractual commitment with the service credits that go with it. Starter does not carry that target. Saying so plainly is better than implying a single number applies to everyone.

Liability is capped, as it is in essentially every software agreement of this size, and the cap is expressed against fees paid over a defined preceding period. Indirect and consequential losses are excluded. A recruitment firm that loses a placement because a system was slow will not recover the fee from the vendor, and any vendor implying otherwise is not describing a contract anyone signs.

What sits outside the cap is worth asking about specifically during procurement, because the carve-outs are where the real negotiation happens: data protection obligations, confidentiality breaches and indemnities usually sit on their own terms. Those are the clauses to hand to counsel first.

Soor LLC is a limited liability company registered in Delaware, USA, and the standard agreement is governed by Delaware law with venue in Delaware. For a US buyer that is unremarkable. For a UK or Australian buyer it is a real consideration, because it sets the forum, the procedure and the cost of any dispute a long way from home.

It is a negotiable term at the Enterprise tier rather than a fixed one, and buyers with a procurement policy that requires local law or local venue should raise it early rather than at signature. So should buyers whose own client contracts flow down a governing-law requirement, which is common in RPO and in public-sector supply chains.

Data protection obligations do not follow governing law. A UK or EU customer keeps UK or EU data protection obligations regardless of which court would hear a commercial dispute, and the transfer mechanisms for that sit in the data processing addendum rather than in this clause.