app2email

Privacy Policy

Last Updated: November 10, 2026

This Privacy Policy explains how app2email ("we", "our", "us") operated by Katalina Technologies Pty Ltd collects, uses, stores, and protects your personal data when you use our WhatsApp-Email bridge service. We are committed to protecting your privacy and complying with the General Data Protection Regulation (GDPR), Australian Privacy Principles, and applicable data protection laws.

By using the Service, you agree to the collection and use of information in accordance with this Privacy Policy.

1. Data Controller

Company: Katalina Technologies Pty Ltd

Address: 520 Oxford St, Bondi Junction NSW 2022, Australia

Email: support@app2email.com

2. Definitions

The words of which the initial letter is capitalized have meanings defined under the following conditions:

  • Account means a unique account created for You to access our Service or parts of our Service.
  • Application/Service refers to app2email, the WhatsApp-Email bridge service provided by the Company.
  • Personal Data is any information that relates to an identified or identifiable individual.
  • Device means any device that can access the Service such as a computer, a cellphone or a digital tablet.
  • Service Provider means any natural or legal person who processes the data on behalf of the Company.
  • Usage Data refers to data collected automatically, such as IP address, browser type, and usage patterns.

3. Data We Collect

3.1 Account Information

  • Email address
  • WhatsApp phone number details
  • Billing information is processed securely by our payment provider.

3.2 Communication Data

  • WhatsApp messages
  • Email messages
  • Metadata (timestamps, sender/recipient information, message delivery status)

3.3 Chat History

We store conversation history as an essential part of our service for:

  • Providing chat history to Service users
  • Enabling logging and reporting features
  • Operational audits and compliance

Chat history storage is required to provide the service, but permanent deletion of all stored history can be made at any time in the account dashboard, or by contacting support.
Only the text of the messages, and basic details of any attachments (type, size, filename) are retained.
All attachments received in any messages are usually kept in memory only while forwarding, and are never stored by the Service.
In cases where immediate forwarding is not possible due to WhatsApp or Email service issues, the attachment to be forwarded will be temporarily stored on the Service server, and will be immediately deleted by the Service after forwarding.

3.4 Website Usage Data

Usage Data is collected automatically when visiting the app2email.com website and may include:

  • Your Device's Internet Protocol address (IP address)
  • Browser type and version
  • Pages of our Service that You visit
  • Time and date of Your visit
  • Time spent on pages
  • Other diagnostic data

3.5 Connected Calendars

If you use the bookings feature and choose to connect a calendar, we access the calendar data described in section 17 (Google Calendar Data). We access nothing from your calendar unless you connect it.

If you connect Cal.com, you give us a Cal.com API key. We use it only to read your Cal.com event types, the start and end times of your Cal.com bookings and the busy times of the calendars you connected in Cal.com (to offer customers only free times), and to create a Cal.com booking for each confirmed appointment and cancel it when the appointment is cancelled or moved. The key is stored encrypted and deleted when you click Disconnect; to stop access at once, also delete the key in Cal.com (Settings, Developer, API keys).

You can also connect a booking service: Calendly, Acuity Scheduling, Square Appointments, Microsoft Bookings, SimplyBook.me, Setmore or Zoho Bookings. Depending on the service you give us an access token, an API key or a login, or you sign in with the service (Microsoft Bookings, Zoho Bookings). We use this access only to read the services, appointment types, staff members and locations you choose from, the start and end times of your existing appointments and blocked times in that service (to offer customers only free times), and to create an appointment there for each confirmed booking and cancel it when the booking is cancelled or moved. The appointment we create carries the customer's name and the contact details they gave in WhatsApp, in its notes. We ask the service not to send its own messages to your customer. Keys, tokens and passwords are stored encrypted and deleted when you click Disconnect; to stop access at once, also withdraw the key or token in the service itself.

Online booking page. If you switch on the online booking page, your customers can book on a web page. A customer enters a name and, if you ask for them, an e-mail address and a note. A customer we do not know yet also confirms the booking by sending a WhatsApp message from their number; if they pay or buy a package they type their WhatsApp number on the page. We keep these details as part of the booking, for you.

Calendar team. If you invite people to your calendar, we store their login e-mail address, their role and the options you set for them, and we send them an invitation e-mail. They see only the calendar, not your dashboard.

Payments. If you take payments for bookings, the customer pays through Stripe or PayPal under your own account with them, and the money goes to you. Their terms and privacy policy apply to the payment. We store the amount, the status and the provider's reference of each payment. We never see or store card details.

AI brief and drafts in the calendar. When a person on your team asks the assistant for a draft message or a preparation brief about a customer, we send that customer's name, booking history, notes and recent messages to our AI model provider to write the text. This happens only when the person asks. If you hide customer contact details for that person, the phone number and e-mail address are left out. The text is a suggestion; nothing is sent to the customer until a person sends it.

Deleting booking data. You can erase one customer's booking data (names, e-mail addresses, notes and the link to their number are removed from their appointments, and their notes, links and poll votes are deleted), and you can set a number of days after which this happens automatically for appointments that ended. Payment records keep the amount and the date but lose the name and number.

4. Legal Basis for Processing

We process your personal data under the following legal bases:

  • Contract Performance: To provide the WhatsApp-Email bridge service you've subscribed to
  • Legitimate Interests: For service improvement, fraud prevention, and security
  • Legal Obligation: For compliance with applicable laws and regulations

5. How We Use Your Personal Data

We use your personal data to:

  • Route messages between WhatsApp and Email
  • Enable human-in-the-loop interventions via email
  • Deliver AI agent responses and automation services
  • Send outbound broadcasts as requested by you
  • Provide detailed logging and reporting
  • Conduct operational audits and quality assurance
  • Manage Your Account and registration
  • Respond to support inquiries
  • Send service-related notifications

6. Data Sharing and Third Parties

6.1 Service Providers

We may share your data with:

  • WhatsApp/Meta: For message delivery (subject to their privacy policy)
  • Email service providers: For email delivery
  • Cloud hosting providers: For secure data storage
  • AI service providers: Only if you choose to integrate external AI services
  • Google: Only if you connect Google Calendar: the booking details you choose are written into your own calendar (see section 17)

6.2 Your AI and Automation Services

When you connect your own AI and automation systems, data is shared according to your configuration. We do not control how your proprietary AI systems process data. Your proprietary knowledge remains secure within your own systems.

6.3 Legal Requirements

We may disclose your data if required by law, court order, or to protect our legal rights.

7. International Data Transfers

Your data may be transferred to and processed in countries outside the European Economic Area (EEA) or Australia. When we do so, we ensure appropriate safeguards are in place, such as:

  • Standard Contractual Clauses approved by the European Commission
  • Adequacy decisions
  • Other legally approved transfer mechanisms

8. Data Retention

  • Active account data: Retained while your account is active
  • Chat history: Retained until you request deletion
  • Billing records: Retained for 7 years for accounting and tax purposes
  • Deleted account data: Permanently erased within 30 days of account closure

9. Your Rights Under GDPR and Australian Privacy Law

You have the following rights:

9.1 Right to Access

Request a copy of all personal data we hold about you

9.2 Right to Rectification

Correct any inaccurate or incomplete data

9.3 Right to Erasure ("Right to be Forgotten")

Request deletion of your personal data, including all chat history

9.4 Right to Restrict Processing

Limit how we use your data in certain circumstances

9.5 Right to Data Portability

Receive your data in a structured, machine-readable format

9.6 Right to Object

Object to processing based on legitimate interests

9.7 Right to Lodge a Complaint

File a complaint with your local data protection supervisory authority

To exercise any of these rights, contact us at: support@app2email.com

10. Security of Your Personal Data

The security of Your Personal Data is important to Us. We implement appropriate technical and organizational measures to protect your data:

  • Encryption in transit (TLS/SSL)
  • Access controls and authentication
  • Regular security audits
  • Secure data centers
  • Employee confidentiality agreements

However, remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While We strive to use commercially acceptable means to protect Your Personal Data, We cannot guarantee its absolute security.

11. Chat History Control

You have full control over chat history storage:

  • Enable/Disable: Toggle chat history storage at any time in your account settings
  • Instant Deletion: Request immediate and permanent erasure of all stored history
  • Default Setting: You can choose whether chat history is enabled or disabled by default
  • Privacy-First: When disabled, messages are processed in real-time and not stored
  • Secure Storage: If enabled, chat history is securely encrypted and remains private

12. Cookies and Tracking

We use cookies and similar technologies for:

  • Essential website functionality
  • Analytics to improve our service
  • User preferences and settings

You can control cookies through your browser settings. Disabling cookies may affect website functionality.

13. Children's Privacy

Our Service is not intended for individuals under the age of 16 (or 13 in certain jurisdictions). We do not knowingly collect personally identifiable information from anyone under the age of 16. If you believe we have collected data from a child, please contact us immediately at support@app2email.com.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify You of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date at the top of this Privacy Policy.

You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page. Continued use of our service after changes constitutes acceptance of the updated policy.

15. Contact Us

If you have any questions about this Privacy Policy, wish to exercise your rights, or have other privacy inquiries, you can contact us:

Email: support@app2email.com

Mail: Katalina Technologies Pty Ltd, 520 Oxford St, Bondi Junction NSW 2022, Australia

16. Supervisory Authority

If you are in the EU/EEA, you have the right to lodge a complaint with your local data protection supervisory authority. A list of EU supervisory authorities can be found at: https://edpb.europa.eu/about-edpb/board/members_en

If you are in Australia, you can contact the Office of the Australian Information Commissioner (OAIC) at: https://www.oaic.gov.au

17. Google Calendar Data

The bookings feature lets you connect a Google Calendar so that customers are only offered times when you are free and their bookings appear in your calendar. This section explains what Google user data app2email accesses, how we use, store, share and delete it, and how you can withdraw access. It applies only if you connect a Google Calendar, which you do yourself on the Bookings > Calendar page by signing in with Google and approving the access. You can use bookings without connecting any calendar.

17.1 Data We Access

When you connect, Google asks you to approve these permissions, and we access only the following:

  • Your Google account email address (the "openid" and "email" permissions), to show you which Google account is connected.
  • The list of your calendars (read-only): each calendar's ID, name, colour, whether it is your main calendar and whether you can add events to it, so you can choose the calendar bookings go to and the calendars that block times.
  • Free/busy times of the calendars you choose: only the start and end times of busy periods. This permission does not give us event titles, descriptions, locations or guests.
  • Events in calendars you own, used to add an event for each booking to the calendar you choose and to remove that event when the booking is cancelled or moved. To work out your busy times in that calendar we read only each event's start and end time, its status, whether it is marked busy or free, and your own reply if you were invited. We do not read the titles, descriptions, locations or guest lists of events that app2email did not create.

17.2 How We Use It

We use Google user data only to provide the bookings feature you set up:

  • to offer your customers only the times when your chosen calendars are free;
  • to add each confirmed booking to the calendar you chose, using the event title and description you set on the Calendar page (for example the customer's name, phone number, the service and the time), and to remove that event if the booking is cancelled or moved;
  • to show you, on your dashboard, which account and calendars are connected and whether the connection works.

Events are added without Google sending invitations or notification emails to anyone. Customers who book see only the times on offer, never your calendar or its events.

We do not:

  • sell Google user data, or use or transfer it for advertising, including personalised, retargeted or interest-based advertising;
  • use Google user data to develop, improve or train generalised artificial intelligence or machine learning models;
  • use Google user data to decide creditworthiness or for lending purposes;
  • allow people to read your Google user data, unless you ask us to in a support request, it is necessary for security (for example investigating abuse), or it is required by law. Our systems otherwise process it automatically.

app2email's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

17.3 How We Store and Protect It

  • The sign-in tokens Google gives us are encrypted (AES-256-GCM) before they are stored in our database. They are never shown on your dashboard or sent to your browser, and we never see your Google password.
  • We store the connected account's email address and the list of your calendars (IDs and names) with your booking settings.
  • For each booking added to your calendar we store the ID of that calendar event, so we can remove it if the booking is cancelled or moved.
  • Free/busy times are held in memory for at most 60 seconds to answer booking requests quickly, and are never written to our database.
  • All data is sent to and from Google over encrypted connections (HTTPS) and is stored on our servers, protected as described in section 10.

17.4 Sharing

We do not share or transfer Google user data to anyone else. The only data we send is the booking details you choose, which are written into your own Google Calendar. The exceptions are when the law requires it, or as part of a merger, acquisition or sale of our business, in which case the data stays subject to this Privacy Policy and you will be told first.

17.5 Keeping and Deleting It, and Withdrawing Access

  • Disconnect: when you click Disconnect on the Book-and-Pay > Calendar page, we ask Google to cancel our access and immediately delete the stored tokens, the account's email address and your calendar list. Events already added to your calendar stay there; you can delete them in Google Calendar.
  • In your Google account: you can also remove app2email's access at any time at myaccount.google.com/permissions. We then stop using the connection at once, and your dashboard shows that it needs reconnecting. Clicking Disconnect on the Bookings > Calendar page then deletes what we stored.
  • Closing your account: all Google user data we hold is deleted within 30 days, as set out in section 8.
  • On request: email support@app2email.com and we will delete your Google user data.

By using app2email, you acknowledge that you have read and understood this Privacy Policy and agree to the collection and use of information in accordance with this policy.