Not legal advice. This is general information written with AI assistance to help a practice think the question through. It is not a legal opinion. Laws, Google's terms and the IPA guidelines change; check the current versions and consult an Israeli privacy lawyer before relying on this. Summary A paid Google Workspace account with Google's HIPAA Business Associate Agreement (BAA) accepted is a reasonable basis for meeting the confidentiality requirements in the Israel Psychological Association (IPA) AI guidelines. This holds if it is configured correctly and used only through its covered services. The IPA Ethics Committee's interim AI guidelines (23 March 2026) ban putting client information into public commercial AI tools. They name ChatGPT, Gemini and Claude as examples. They allow work on a specific client's material in two cases. One is a system built and secured for therapeutic work. The other is an organizational or private system that explicitly permits sensitive medical information. Either way, confidentiality must be assured by the vendor's own terms or by a contract. Workspace with a BAA fits the second case: Explicit permission for health data. The BAA is Google's contract that allows protected health information in a defined list of services. That list includes Gmail, Drive and Docs, Meet, Calendar, the Gemini app and Gemini inside Workspace (Google's list, updated 28 Oct 2026). Contractual confidentiality. The Cloud Data Processing Addendum (CDPA) also binds Google. Google may process data only to provide the service. Staff are bound by confidentiality. Incidents must be reported, and data deleted after termination. Google holds ISO 27001 certification. No model training and no human review. Google says Workspace does not use customer data to train models without permission. It also says Gemini content in Workspace is not reviewed by humans (Workspace generative-AI privacy hub). The key distinction: the IPA's "Gemini" ban targets the public consumer product. The Gemini app used through a managed Workspace account under the BAA and CDPA is a fundamentally different contractual setting. A strict reader of the guidelines could still disagree, but that reading would be tantamount to banning any software - like Gmail - or any external LLM - and even when covered by BAA. Requirement-by-requirement Each row pairs a requirement with what Workspace plus the BAA provides. The right-hand column shows what is still your responsibility. | Requirement (source) | What Workspace + BAA provides | Still on you | |---|---|---| | Confirm the tool is secure enough to protect confidentiality before entering client data (IPA guidelines, sec. C) | BAA, CDPA, ISO 27001 and SOC 2/3 reports; security controls in the Admin console | Configure it (see Basic setup); keep proof you checked | | No client data in public commercial AI tools (IPA, sec. C) | Gemini under a managed work account is covered by the BAA and CDPA, not consumer terms | Never use a personal Gmail or consumer Gemini; Gemini in Chrome is excluded from the BAA | | Use only systems that explicitly allow sensitive medical information, with confidentiality assured by vendor terms or contract (IPA, sec. C) | The BAA explicitly allows health information in listed services | Keep client data inside listed services only | | System complies with Israeli privacy law and record rules (IPA, sec. C) | CDPA covers processing limits, confidentiality, security, breach notice and deletion | Your own privacy obligations as database controller | | Written outsourcing agreement with any external party that holds your database (Data Security Regulations 2017, reg. 15) | CDPA plus BAA work as the processor agreement | Check them against reg. 15; record it in your security procedure | | Transfer abroad needs the recipient's written undertaking to meet Israeli conditions or ISO 27001 compliance (PPA opinion on reg. 2(4), April 2026) | Google may process data worldwide under the CDPA; it holds ISO 27001; purpose limits and deletion are in the contract | Ask a lawyer whether the CDPA meets the opinion's test | | Stricter enforcement and fines since 14 Aug 2025 (Amendment 13) | A documented, contract-backed setup | Database mapping, security procedure, access control | | Informed, written consent before AI use with a client (IPA, sec. D) | Nothing | Consent form; record the client's decision | | Record AI use in the client's file (IPA, sec. F) | Nothing | Note each AI use in the record | | Critically review all AI output; responsibility stays with you (IPA, sec. A) | Nothing | Review and correct every draft | Limits and conditions The BAA covers the platform, not how you use it. These points decide whether the setup actually holds up: The BAA is a US instrument. Israeli law does not recognize a BAA as such. In Israel the BAA counts as evidence of the vendor's commitments. The CDPA does most of the legal work. Covered services only. Third-party add-ons and "Additional Google services" are not covered (Google HIPAA help page). Gemini in Chrome is excluded by name. As of 28 Oct 2026, Gemini Notebook (formerly NotebookLM) is not on the Workspace BAA list. Don't put client material in it until Google lists it. Sharing mistakes break it. Google warns that a file shared with "anyone with the link" or with outside users can expose Gemini prompts and output to them. Feedback leaves the protected path. If you press feedback and choose to share the prompt, Google may keep it for up to 18 months. You remain the database controller. You must still map the database, write a security procedure, control access, report breaches and follow record-retention rules. Clinical duties are not technical. These include written informed consent, a note in the record, critical review of output, and treating clients who refuse AI without it. Pricing For a clinical practice, Business Standard at $14 per user per month on an annual plan is the practical minimum. Starter lacks Gemini in Docs, Sheets, Drive and Meet. Google's own page shows prices in US dollars for Israel, before VAT. The figures below are October 2026 list prices; confirm them at workspace.google.com/pricing. | Plan | Annual plan (USD/user/month) | Flexible, monthly (USD/user/month) | Storage per user | Fit for a practice | |---|---|---|---|---| | Business Starter | 7.00 | 8.40 | 30 GB | Email only; limited Gemini | | Business Standard | 14.00 | 16.80 | 2 TB | Recommended: full Gemini in Workspace apps | | Business Plus | 22.00 | 26.40 | 5 TB | Adds Vault (retention, eDiscovery) and advanced device management | A solo psychologist needs one licence: about $168 a year on Standard, plus VAT. The BAA costs nothing extra. Basic setup Do these steps in order, and finish steps 1–5 before any client data enters the account. Google renames Admin console menus from time to time, so look for the closest match. Sign up. Go to workspace.google.com, choose Business Standard and use your practice domain (for example yourname.co.il). Verify the domain as prompted. Secure the admin account. In the Admin console, go to Security → Authentication → 2-Step Verification. Turn it on and enforce it for everyone. Passkeys or a security key are best. Accept the BAA. Sign in as super admin. Go to Account settings → Legal and compliance. Review and accept the HIPAA Business Associate Amendment. Save a screenshot of the acceptance; Google notes that it shows electronic acceptance. Review the data processing terms. In the same Legal and compliance page, review the Cloud Data Processing Addendum and fill in the privacy contact details. Close the gaps outside the BAA. Apps → Additional Google services: turn off what you don't need. Apps → Google Workspace Marketplace apps: block third-party apps and add-ons, or allow only ones you have vetted. Don't use Gemini Notebook or Gemini in Chrome for client material. Restrict sharing. Go to Apps → Google Workspace → Drive and Docs → Sharing settings. Turn off or warn on sharing outside your domain. Set new links to "Restricted". Turn on Gemini for work accounts. Enable the Gemini app and Gemini in Workspace for your organization. Always use them signed in with your work account, never a personal Gmail. Protect devices. Use a screen lock and disk encryption on every computer and phone that opens the account. Turn on endpoint management in the Admin console. Write down your controls. Map the client database. Write a short data security procedure. List who has access. Attach the BAA screenshot and CDPA. Update clinical paperwork. Add an AI section to your written informed-consent form: what the tool does, how confidentiality is protected, limits, alternatives and risks. Note each AI use in the client's record. Review every output before it enters the file. Sources IPA Ethics Committee — Principles and ethics rules for using AI tools in psychological work, interim guidelines (23.3.2026) IPA professional ethics page Google — HIPAA compliance on Google Cloud and Google Workspace (included services, updated 28.10.2026) Google — HIPAA compliance with Google Workspace and Cloud Identity (how to accept, what is excluded) Google — Cloud Data Processing Addendum Google — Generative AI in Workspace privacy hub Google Workspace pricing page Tel Aviv Municipality — guide to regulation 15 of the Data Security Regulations Shibolet — PPA final opinion on regulation 2(4), transfers abroad (13.4.2026) Shibolet — PPA enforcement after Amendment 13 (in force 14.8.2025)