Data Processing Addendum

This addendum is between the account owner ("you", the customer) and [COMPANY LEGAL NAME] ("Plazas", "we").

It covers "customer personal data": personal data about other people that you or your users put into Plazas, connect to it, or that reaches your account from the public. For that data you are the controller (under Israeli law, the owner of the database) and we are the processor (the holder). If you yourself act for someone else, you are their processor and we are your sub-processor.

It does not cover the data of your own Plazas account (your email, plan, coin history), for which we are the controller under the Privacy Policy.

We process customer personal data only on your documented instructions. Your instructions are: the Terms, this addendum, and what you do in the app (hiring an employee, giving a task, ticking which employee may read a connection, approving a proposal, switching the website assistant on).

We will tell you if we think an instruction breaks data protection law, and we may pause it. If a law requires us to process the data in another way, we will tell you first unless that law forbids it.

We do not sell customer personal data, do not use it for advertising and do not use it to train AI models of our own.

• Having a lawful basis for the data you put in or connect, and for sending it to the sub-processors listed in section 6.
• Telling the people concerned what the law requires, including that an AI assistant answers on your website and that conversations are saved.
• Choosing which AI employee may read which source, and checking and approving what is sent in your name.
• Marketing messages you send with text produced in Plazas: you need the consent and the unsubscribe wording the law requires.
• Not connecting data you are not allowed to process this way.

Access to customer personal data on our side is limited to the people who need it to run and support the service, and they are bound to keep it confidential.

You give us general permission to use the sub-processors on the Sub-processors page. We have a contract with each that requires it to protect the data, and we remain responsible to you for what they do with it.

Before adding or replacing a sub-processor we will update that page and give notice at least [SUB-PROCESSOR CHANGE NOTICE PERIOD] ahead. You may object on reasonable data-protection grounds within that time; if we cannot resolve it, you may close your account and receive a refund of any prepaid period not yet used.

Services you connect yourself (for example your Google, HubSpot or GitHub account) are your own providers, not our sub-processors.

We keep the technical and organisational measures described in section 8 of the Privacy Policy, and may improve them but not weaken them in a way that matters. In summary: encryption in transit, row-level access rules on every table, server-only writing of results and connected rows, an encrypted store for connection secrets, automatic holding back of columns that look personal in connected tables, owner approval before any action in a connected app, rate limits on public entry points, and no logging of task or conversation content by our functions.

You are responsible for the security of your own password, devices and connected accounts.

If a person asks us to see, correct or delete data that belongs to your account, we will pass the request to you and not answer it ourselves unless the law requires.

You can already find, correct and delete most records yourself in the app. The app does not yet have a tool that collects or exports everything held about one named person across tables; when you receive such a request, write to us and we will help you search and produce or delete the records within a reasonable time.

We will also give reasonable help with data protection impact assessments and with questions from an authority, as far as they concern our processing.

You can export your saved document at any time (Settings, Account) and ask us for the tables that export does not include. When you delete your account, the customer personal data in our database is deleted at once; copies in our provider's backups expire within [BACKUP RETENTION PERIOD]. If we close your account, we delete the data within [DELETION PERIOD AT END OF SERVICE] unless the law requires us to keep it.

Not yet automatic: removing the sign-ins to apps that our connection provider holds for you. Disconnect them before you delete the account, or ask us to.

If we learn of a breach of security that leads to the loss, change, disclosure of or access to customer personal data, we will tell you without undue delay and no later than [BREACH NOTICE PERIOD] after we become aware of it, with what we know: what happened, what data and roughly how many people, what we are doing about it, and whom to contact. We will keep you updated and help you meet your own duties to notify.

The database is in Frankfurt, Germany. Some sub-processors process data in the United States and other countries. For transfers out of the EEA, the UK or Switzerland we rely on [TRANSFER MECHANISM], which are made part of this addendum where they are needed. For data from Israel, see section 6 of the Privacy Policy.

On written request, at most once a year unless there has been an incident, we will give you the information reasonably needed to show that we meet this addendum, and answer a reasonable written questionnaire. An on-site audit needs our agreement on timing, scope and confidentiality, and is at your cost. Requests go to [PRIVACY CONTACT EMAIL].

If this addendum and the Terms disagree about the processing of customer personal data, this addendum prevails. The limits on liability in the Terms apply to this addendum, as far as the law allows. The law and courts are those of the Terms.