The processor agreement, published rather than negotiated.

Using SalesWolf to enter personal data accepts this agreement. It sits alongside the terms, and where the two disagree about personal data, this one wins.

If your organisation needs a countersigned copy or its own template, write to us. We would rather have one public version everybody reads than a drawer of variants nobody can compare.

You are the controller of the personal data you enter about other people — the contacts, stakeholders and colleagues who appear in your deals. SalesWolf DOO, registered at Uroša Martinovića 9/44, 11070 Belgrade, Serbia (Reg. No. 21579874, Tax ID (PIB) 111949567), is the processor of that data.

For your own account data we are the controller, and the privacy policycovers it. This agreement is about the first kind.

Subject matter. Processing the deal material you enter so that SalesWolf can extract qualification facts from it, tell you what is missing, and draft text from it.

Duration. For as long as you have an account and have not deleted the material, plus the recovery window in the deletion clause below.

Nature and purpose. Storage, retrieval, text extraction by a language model, the creation of numeric representations used to find related passages, and the generation of drafts. Nothing is processed for our own purposes, and nothing is sold, shared or used for advertising.

Categories of data subject. The people involved in your deals: contacts and stakeholders at the organisations you sell to, and colleagues you mention.

Types of personal data. Whatever you enter. In practice: names, job titles, employers, what someone said in a meeting, and your own notes about their position and behaviour.

Special categories of personal data — health, beliefs, union membership and the rest — are not to be entered. The service is not designed to hold them, and this agreement does not cover them.

We process the material only on your instructions. Your use of the product is that instruction: adding material, running an extraction, generating an artifact, deleting something. We do not process it for any other purpose, and we do not decide what goes in.

If we are ever required by law to process it in some other way, we will tell you before we do unless the law forbids that. If an instruction looks to us like it would break data protection law, we will say so.

The people operating SalesWolf are a very small number, each under a duty of confidentiality. Access to production data is limited to what running and fixing the service requires.

Inside the product, accounts are shared with every member of a workspace, and deals are shared with them by default. An owner or admin of the workspace can make deals private to their owner by default, and a deal's owner can make a single deal private or shared. A member can read and add to a shared deal; only the deal's owner can edit, close or delete it. A private deal stays with its owner, but its account and the people recorded on it stay shared with the workspace.

The measures in place today, stated as facts rather than as intentions:

• Everything in transit is encrypted; the connection terminates at a tunnel we control.
• The database is reachable only from our own application containers on a private network. It has no public address.
• There is no password, and none is stored: you sign in with a one-time code sent to your email address. Sessions expire.
• Authorisation is checked on every request: against the workspace, against whether a deal is shared, and against the deal's owner for an edit, close or delete.
• Request ceilings apply per user and per workspace on the routes that call a language model.
• A document you drop is parsed in your own browser; the file itself is never uploaded, so there is no store of original files to protect.

What is NOT in place, since a security section that lists only what exists is a half-answer: we hold no ISO 27001 or SOC 2 certification, we have not commissioned a penetration test, and the database volume is not separately encrypted at rest. If any of those is a requirement for you, it is one we do not meet today.

You authorise the subprocessors listed on the subprocessors page. Each is bound to no more than what that page describes it receiving.

Before a new one starts receiving anything, the change is published on that page at least 30 days in advance, with the date it takes effect. Be aware of how weak that mechanism is and why we are saying so: the product sends email only for sign-in codes and workspace invitations, and no notice of a subprocessor change is mailed — the published page is the notice. If you object to an addition, tell us and you can stop using the service and delete your material; we will not charge you for a period you objected to.

Most data-subject requests you can satisfy yourself: the material is in front of you in the product, and you can correct or delete any of it. Where that is not enough, we will help you respond to access, correction, deletion, portability and objection requests, and with a data protection impact assessment if you need one.

If personal data you entrusted to us is breached, we will tell you without undue delay after we become aware of it, with what we know: what happened, which data, what we have done, and what you may need to do. We will not wait until the picture is complete to make the first contact.

You can delete any material from inside the product at any time. It disappears at once and is removed from the database 90 days later. When you close your account, the same applies to everything you own.

On the return of data, the honest position: there is no bulk export feature today. You can copy anything out of the product by hand, and if you need a complete copy we will produce one for you manually on request. We would rather say that than describe a self-serve export that does not exist.

We will give you the information you need to verify that we are meeting this agreement, and answer specific questions in writing. Where a written answer is not enough for your obligations, we will agree a proportionate way for you or an auditor you appoint to check — arranged in advance, and not so often or so broadly that it becomes the work.

Material sent to a language model leaves the EU: the gateway is a US company and the model providers behind it operate outside the EU. The privacy policy describes this and the subprocessors page names each company.

The safeguard relied on for that transfer:

Standard contractual clauses: those adopted by the Serbian Commissioner for Information of Public Importance and Personal Data Protection under the Law on Personal Data Protection, and the EU standard contractual clauses each subprocessor uses.

[email protected] reaches a person about anything in this agreement, including a request for a countersigned copy.