This is a translation for convenience. The legally binding version is the one in Hebrew. If the translation and the original differ, the Hebrew text prevails.
1. The parties and their roles
The Contractor is the "database owner" (controller): it decides what information about its clients is collected, why, and what is done with it. The Contractor's clients are the "data subjects".
RBM is the "database holder" (processor): it processes the information on the Contractor's behalf, following the Contractor's instructions as reflected in its use of the software, and not for its own purposes, except as set out in section 5.
This agreement supplements the terms of use and the privacy policy. If they conflict on the processing of personal information, this agreement prevails.
2. Definitions
- Personal information: any information about an identified or identifiable person, as defined in the law: name, phone, email, property address, signature, IP address, and document content that identifies a person.
- Document: a quote, contract, change order, warranty certificate or any other document the Contractor creates, sends or signs through RBM Documents.
- Event trail: a document's record of events, which cannot be edited: views, identity verification, signatures, payments and SHA-256 fingerprints.
- Sub-processor: a third party RBM uses to process the information (section 7).
3. Subject, purposes and duration of the processing
RBM processes personal information solely to run the service for the Contractor: creating documents, sending them to clients, verifying the signer's identity, collecting an electronic signature, collecting a deposit through the Contractor's payment processor, keeping site evidence, producing a public verification page, and recording the event trail.
The processing lasts for the whole subscription period, and after it as set out in section 10 (retention and deletion).
4. Types of information and data subjects
- The Contractor's clients: name, phone, email, property address, details of the work, amounts, signature, IP address and browser type at the moment of signing, and the result of OTP verification.
- The Contractor's team: name, email, password (hashed), sign-in log, two-factor authentication secret (encrypted).
- Site evidence: photos the Contractor attaches to a document, which may contain identifying information (a property, a person).
- Financial information: the amount, status and transaction ID of deposits. RBM does not receive or store credit card numbers.
5. The Contractor's instructions and limits on use
RBM will process the information only according to the Contractor's instructions, as recorded in this agreement and in the Contractor's actions in the software. RBM will not sell information, will not use it for advertising, and will not use it to train models.
RBM may use aggregate, anonymous information (for example, the number of documents signed in the system) to improve the service, provided no person or business can be identified from it.
If RBM is required by law to hand over information to an authority, it will notify the Contractor in advance as far as the law allows.
6. Information security
RBM applies security measures appropriate to the sensitivity of the information and to the Protection of Privacy Regulations (Information Security), 5777-2017, including:
- Encryption in transit (TLS 1.2 or higher) on every endpoint, including the public signing pages.
- Encryption at rest of the database and storage; sensitive secrets (the Contractor's API keys, two-factor authentication secrets) are encrypted separately at field level.
- Separation between organizations: every query is filtered by the organization ID; files are kept in private storage and served only after a permission check.
- Two-factor authentication (TOTP) is available to every user and actively recommended for accounts with signed documents.
- An event trail for every document that cannot be edited: who viewed, who signed, from which address, and which SHA-256 fingerprint was signed.
- One-time verification codes for signers are stored as a hash only and deleted after 30 days.
- Rate limiting on public endpoints, CSRF protection, and checking the content of uploaded files (not only their extension).
- A log of sign-ins and security events, and periodic security checks of the database infrastructure.
The Contractor is responsible for securing access on its side: a strong password, turning on two-factor authentication, and removing team members who have left. The Contractor is also responsible for the lawfulness of collecting information from its clients and for giving them notice under section 11 of the law.
7. Sub-processors
The Contractor authorizes RBM to use the following sub-processors. RBM is responsible to the Contractor for their actions as if they were its own:
| Provider | Role | Location | Note |
|---|---|---|---|
| Vercel Inc. | App hosting, edge servers, error logs | USA / European Union | Information passes through the servers and is not stored there permanently |
| Supabase Inc. (on AWS infrastructure) | The database and the private storage of documents and photos | AWS, region ap-northeast-1 (Tokyo, Japan) | Encryption at rest and in transit; daily backups |
| Resend Inc. | Sending operational email (signing links, verification codes, confirmations) | USA | The recipient's address and the message content only |
| OpenAI, L.L.C. | Smart assistant and transcription features, only when the Contractor turns them on | USA | Under the API terms, the information is not used to train models |
| Meta Platforms (WhatsApp Cloud API) | Sending WhatsApp messages, only if the Contractor connected an account | USA / European Union | The phone number and the message content |
Providers the Contractor connects to directly, under its own contract, which are not RBM's sub-processors:
- Deposit payment processing (Tranzila, Cardcom or another provider): the contract is between the Contractor and the payment processor. RBM receives only a payment confirmation and a transaction ID.
- Text messages for signature verification (Inforu, 019 or another provider): sent from the Contractor's text messaging account, with an API key the Contractor enters.
RBM will notify the Contractor by email 30 days in advance of adding or replacing a sub-processor. A Contractor who objects may end the subscription before the change takes effect and receive a full export.
8. Transferring information outside Israel
The database is hosted with Supabase on AWS infrastructure in the Tokyo region (Japan), and the other sub-processors operate in the USA and the European Union. The transfer is made under the Protection of Privacy Regulations (Transfer of Information to Databases Outside the State's Borders), 5761-2001, and subject to each provider's contractual commitment to a level of protection no lower than Israeli law requires, to encryption at rest and in transit, and to not using the information for the provider's own purposes.
The Contractor, as the database owner, hereby approves the transfer for the purposes of this agreement. RBM will consider moving to a region closer to Israel when the sub-processors offer one on equal terms.
9. Security incident
- RBM will notify the Contractor of a severe security incident involving its information without delay, and no later than 72 hours from discovery, by email to the account owner.
- The notice will include: the nature of the incident, the types of information and the people affected as far as known, the steps taken, and recommendations for the Contractor.
- Reporting to the Privacy Protection Authority and to the data subjects, as far as required under regulation 11 of the Information Security Regulations and Amendment 13, is the Contractor's responsibility as the database owner; RBM will provide all the information needed for the report and help carry it out.
10. Retention and deletion
The retention periods are set in the RBM Documents data retention policy, version rbm-retention-2026-09-v2, and summarized here:
- Signed documents, signatures, SHA-256 fingerprints and the event trail: for the life of the account and 7 years after it ends, in line with the limitation period and the inspection and warranty periods in the Sale (Apartments) Law.
- One-time verification codes: 30 days.
- Raw payload of payment confirmations: 180 days; the amount, method and date are kept as a financial record.
- Sign-in logs: 12 months.
- When the subscription ends: 30 days for a full export (PDF and event trail), then deletion of contact details and operational information. Signed documents are kept for 7 years and then deleted.
The Contractor may ask at any time for early deletion of information that is not a signed document. A signed document is evidence of a transaction between two parties and will not be deleted before the period ends, except by court order.
11. Help with data subjects' rights
When a client of the Contractor asks to see, correct or delete information about them, the Contractor handles the request. RBM gives the Contractor the tools: a full document file export, correcting contact details, and deletion. A client who contacts RBM directly through the information request form will be referred to the Contractor, and RBM will help the Contractor reply within 30 days.
12. Audit and transparency
At the Contractor's request, and no more than once a year, RBM will provide a written description of its security measures, the current list of sub-processors, and the results of external security tests as far as they were carried out. An on-site audit will take place by agreement, coordinated in advance, and at the Contractor's expense.
13. Liability
Each party is liable for damage caused by its breach of this agreement or of the law. RBM's liability to the Contractor is limited to the amount paid to RBM in the 12 months before the event, except in the case of a deliberate act or gross negligence.
14. Governing law and jurisdiction
This agreement is governed by the law of the State of Israel. The competent courts of the Tel Aviv district have exclusive jurisdiction.
15. Acceptance and changes
The agreement is accepted by the account owner inside the app (Settings, then Privacy and data). The system records the version accepted, who accepted it, the date and the IP address, and the record is kept as evidence of consent. A material change to the agreement will get a new version number and require acceptance again; until then, the previous version continues to apply.
Privacy contact
RBM Solutions, Tel Aviv, Israel · Reg. no. 207275058
Version history: 2026-09-02, first version: definition of roles, sub-processors, transfer abroad, security incident, retention and deletion.