Privacy Policy

Last updated: October 25, 2026

1. Introduction

Bipla (“we,” “us,” or “our”) operates the Bipla platform: the web dashboard at bipla.co and the Bipla mobile application for iOS and Android (bundle identifier com.bipla.app) — together, the “Service.” This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Service, on any of those surfaces. Where a section applies to only one of them, it says so. By accessing or using the Service, you agree to this Privacy Policy. If you do not agree, please do not use the Service.

Bipla is a business of Cohen Sahar (כהן סהר), trading as BIPLA, a sole proprietor registered in Israel (business ID 214217333), of 11 Prof. Shor St., Holon 5880510, Israel. It acts as the data controller for the account data described in this policy. For the data your AI agents process about your own end customers, you are the controller and Bipla is your processor — see section 2.3 and our Terms of Service.

2. Information We Collect

2.1 Account Information

When you create an account via Google OAuth, we collect your email address, display name, and profile picture as provided by Google. We do not collect or store your Google password.

2.2 Business Information

You may provide business details such as business name, industry, and description to configure your account and AI agents.

2.3 End-User Messaging Data

When end users message your business on WhatsApp, the AI agent that answers them is provided by Meta (Meta Business AI) and runs on Meta's platform. Bipla stores a copy of the conversation so you can read it, and supplies your booking and business data to the agent. On your behalf we process the following data:

Contact identifiers (e.g., phone numbers, chat IDs)
Display names as provided by the messaging platform
Message content exchanged between end users and your AI agents
Voice message audio (temporarily processed for transcription, then discarded)

2.4 Documents and Files

You may upload documents to build your AI agent's knowledge base. These files are stored securely and processed to enable AI-powered responses.

2.5 Calendar and Booking Data

If you use our calendar features, we may collect event details, attendee information, and scheduling data. If you connect Google Calendar, we access your calendar data in accordance with Google's API Services User Data Policy.

2.6 Usage and Log Data

We automatically collect technical information such as IP addresses, browser type, device information, and pages visited. We do not log message content — only metadata such as message timestamps and character counts. Our mobile app can additionally collect usage and crash information, but only if you turn it on — see section 2.8.

2.7 Cookies and Similar Technologies

Cookies are small text files a website stores in your browser. Similar technologies, such as your browser's local storage, work the same way, and we treat them the same way. When you first visit bipla.co we ask which optional cookies you accept. Rejecting is as easy as accepting, and the website works fully either way.

Strictly necessary — always on, because the website cannot work without them. They need no consent under the ePrivacy Directive and equivalent laws:

bipla-token — session authentication (expires after 1 hour)
bipla-refresh — session renewal (expires after 30 days)
bipla-consent — remembers your cookie choice (expires after 6 months)
NEXT_LOCALE — remembers the language you picked
bipla-onboarding and lastBusinessId — bring you back to the right setup step and the business you last opened
Local storage — display preferences you set yourself (light or dark theme, a collapsed sidebar, a calendar view) and short-lived drafts of setup forms. These never leave your browser.
Meta and Google Maps — when you choose to connect WhatsApp, we load Meta's login script; when you type a business address, we load Google Maps address search. Meta and Google may set their own cookies while you use those features, under their own privacy policies.

Analytics and marketing — optional, and off unless you accept them. We do not use any analytics, advertising, or tracking cookies on bipla.co today, so accepting them currently changes nothing. If we ever add one, it will load only for visitors who accepted that category, and we will list it here first.

If you reject optional cookies — or later withdraw your consent — we store your choice so we don't ask again, never load optional scripts, and delete any analytics or advertising cookies already set on bipla.co. You can change your choice at any time from , also found at the bottom of every page, or by clearing cookies in your browser. We ask again every 6 months, or sooner if what we use changes.

Our mobile app does not use cookies. It can, only if you turn it on, use a device-local identifier to measure app usage and report crashes — see section 2.8. We do not use any advertising identifier on any platform: the app is built without support for Apple's Advertising Identifier (IDFA), and the Android Advertising ID permission is removed from the app entirely.

2.8 Mobile App Analytics and Crash Reporting (opt-in)

The Bipla mobile app can collect anonymous usage and crash information to help us find what is broken and what is confusing. This is off by default. Nothing is collected until you turn it on, and we ask once, plainly, the first time you sign in on a device. You can change your mind at any time in Settings → Privacy, and turning it off stops collection immediately.

We use Google Firebase Analytics and Firebase Crashlytics. If you turn this on, we collect:

Which screens you open and which actions you take in the app — for example, that a booking was created, or that a setup step was abandoned. These records are limited to the name of the action and a small set of fixed labels.
Crash and error reports — the type of error, the code it happened in (a stack trace), and the state of the app at that moment.
Basic device and app information — device model, operating system version, app version, language, and country.
A random app-instance identifier that Google generates for this installation of the app. It is not your name, your email, your phone number or your Bipla account, and it is reset if you delete and reinstall the app, or if you turn this setting off.

What we never send. No analytics record or crash report we send contains your name, your email address, your phone number, any message exchanged with your customers, any customer's details, any document you uploaded, or any identifier that would let Google connect this data to your Bipla account. This is enforced in the app's code: the function that sends these records is built so that it cannot accept an identifier.

We do not use this data for advertising. Google Signals is disabled, the data is excluded from advertising personalization, we do not collect any Google advertising identifier, and this data is not linked to any Google Ads account. We do not track you across other companies' apps or websites.

Google processes this data as our processor under the Google Analytics Data Processing Terms. We keep the usage event data for 2 months, after which Google deletes it automatically. Crash reports are kept for 90 days.

This section applies to the mobile app only. The bipla.co website has no analytics of any kind.

2.9 Push Notification Tokens

If you turn on notifications in the mobile app, we store a push token issued by Apple or Google and relayed through Expo's push service. The token identifies the device, not you personally. It is deleted when you sign out, when you disable notifications, and when you delete your account.

Notification content carries no customer names and no message text, by design. A notification tells you that something happened and which of your businesses it concerns; the details are fetched by the app only after you open it, over an authenticated connection. This is enforced in code, not by policy.

3. How We Use Your Information

We use the information we collect to:

Provide, operate, and maintain the Service
Process messages through AI on your behalf
Store and index your documents for AI-powered retrieval
Manage your account, billing, and support requests
Detect and prevent fraud, abuse, and security incidents
Send you operational notifications about your business, where you have enabled them
Measure how the mobile app is used and diagnose crashes — only where you have turned that on (section 2.8)
Comply with legal obligations

3a. Legal Bases for Processing

If you are in the European Economic Area or the United Kingdom, we rely on the following legal bases under the GDPR:

Performance of a contract — operating your account, running your AI agents, processing messages and bookings, and billing you for usage.
Legitimate interests — securing the Service, preventing fraud and abuse, and maintaining an audit trail of administrative actions.
Legal obligation — tax, accounting, and records we are required to keep.
Consent — optional website cookies (section 2.7), mobile app analytics and crash reporting (section 2.8), and push notifications (section 2.9). You may withdraw consent at any time, from Cookie settings on the website, in Settings → Privacy in the app for analytics, and in your device settings for notifications. Withdrawing consent does not affect processing already carried out before you withdrew it, and it does not affect anything we do on one of the other bases above.

4. Third-Party Service Providers

We share data with the following categories of service providers, solely to operate the Service. Each one, what it receives, and where it processes data is listed on our Sub-processors page.

Cloud hosting and infrastructure — hosting, databases, file storage, and a short-lived job queue. All data is encrypted in transit and at rest.
AI processing — your messages to the Bipla assistant, uploaded documents, and voice messages are sent to our AI provider for responses, document indexing, and transcription. Our provider's API terms do not allow it to use this data for model training.
Messaging platforms — when you connect WhatsApp, messages pass through Meta, which runs the AI agent that answers your customers and bills AI messages directly to your business under Meta's own terms. If you link Telegram to the Bipla assistant, those messages pass through Telegram.
SMS — phone number verification, booking-related messages to your customers, and app install links.
Payments — our payment processor and merchant of record for web checkout receives your billing contact details and handles your payment method directly. Card details never reach Bipla's servers.
Mobile app delivery and notifications — relays push notifications to Apple and Google, and serves over-the-air updates to the mobile app.
Mobile analytics and crash reporting — usage events and crash reports, only from devices where you have turned this on. Never used for advertising and never linked to your Bipla account. See section 2.8.
Address search — the address you type when adding a business location.

We do not sell your personal data to any third party, and we do not share it with advertising networks.

5. Data Storage and Security

We implement industry-standard security measures to protect your data, including:

Encryption in transit (TLS/SSL) and at rest
Encrypted storage of sensitive credentials
Database connections secured with SSL certificates
Rate limiting to prevent abuse
Webhook signature verification for messaging platforms
Access controls enforcing data isolation between accounts

While we strive to protect your data, no method of transmission or storage is 100% secure. We cannot guarantee absolute security.

6. Data Retention

We retain your data for as long as your account is active or as needed to provide the Service. You may delete documents at any time through the platform. When you delete your account or business, all associated data — including agents, documents, conversations, and messages — is permanently removed from our systems. Specifically:

Account, business, agent, document, conversation and message data — for the life of the account, then permanently deleted within 30 days of a deletion request.
Mobile app usage events — 2 months, then deleted automatically by Google (only collected if you opted in; see section 2.8).
Mobile app crash reports — 90 days, then deleted automatically by Google (only collected if you opted in).
Push notification tokens — until you sign out, disable notifications, or delete your account, whichever comes first.
A one-way hash of your sign-in identity — retained after account deletion for fraud prevention. It cannot be reversed to identify you. This is described in full on Delete your Bipla account.

6a. Account Deletion

You can ask us to delete your Bipla account and its data at any time — from the app (Settings → Delete account), from the web dashboard (Settings → Account), or by email. We lock the account when the request arrives and permanently delete the data within 30 days. For the full list of what is deleted, what we are required to retain, and why, see Delete your Bipla account.

7. Your Rights

Depending on your jurisdiction, you may have the following rights regarding your personal data:

Access — Request a copy of the data we hold about you
Correction — Request correction of inaccurate data
Deletion — Request deletion of your data
Portability — Request your data in a portable format
Restrict Processing — Request that we limit how we use your data
Object — Object to processing we carry out on the basis of legitimate interests
Withdraw Consent — Withdraw consent where processing is based on consent
Lodge a complaint — Complain to your local data protection supervisory authority

Two of these you can exercise yourself, immediately, without contacting us: deletion, from Delete your Bipla account or in the app, and withdrawal of analytics consent, in the mobile app at Settings → Privacy.

To exercise any of the others, contact us at hi@bipla.co. We will respond within 30 days.

8. Children's Privacy

The Service is not directed to individuals under the age of 16. We do not knowingly collect personal data from children. If we become aware that we have collected data from a child under 16, we will take steps to delete that data promptly.

9. International Data Transfers

Bipla is established in Israel, which the European Commission recognises as providing an adequate level of data protection. Our hosting, databases, and most of our service providers are in the United States; our job queue runs in Germany; Meta processes data in Ireland and the United States. Your data may therefore be transferred to and processed in countries other than your own. The country for each provider is listed on our Sub-processors page.

For transfers of personal data out of the European Economic Area and the United Kingdom to countries without an adequacy decision, we rely on the European Commission's Standard Contractual Clauses, incorporated into our agreements with these providers — for Google Analytics and Crashlytics, through the Google Analytics Data Processing Terms. You can ask us for a copy of the relevant safeguards at hi@bipla.co.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy on this page and updating the “Last updated” date. Your continued use of the Service after any changes constitutes acceptance of the updated policy.

11. Contact Us

If you have questions or concerns about this Privacy Policy or our data practices, please contact us at hi@bipla.co, or by post at Cohen Sahar (כהן סהר), trading as BIPLA, 11 Prof. Shor St., Holon 5880510, Israel.