Privacy Policy

Draft of 27 October 2026

This policy explains what personal data Warsita collects, why, and what you can do about it. It covers our website (warsita.com), the dashboard (app.warsita.com), the API (api.warsita.com) and the messages that pass through them.

1. Two roles

  • Account data. For the people who use Warsita (workspace owners and members), we decide how their account data is used: we are its controller.
  • Customer Data. For the messages, phone numbers and contacts a customer sends and receives through Warsita, the customer decides what is processed and why; we process that data on the customer's behalf and on their instructions. If you received a WhatsApp message sent through Warsita, contact the business that sent it; we will help them answer your request.

2. What we collect

Data What it includes Why
Account data Name, email address, password (stored only as a hash), workspace memberships, sign-in times To run your account and keep it secure
Billing data Your plan, invoices and the payments we record To bill you and keep accounting records
Session data The linked WhatsApp number, its status and session events, and the device keys WhatsApp uses to keep it linked To keep the number connected and show its status
Message data Recipient, type, status and timestamps of each message; its content only until it is sent, unless message logging is on To send messages and report what happened to them
Webhook data The events delivered to your webhook and the result of each delivery To deliver events and let you debug your endpoint
Contact lookups Phone numbers you check and the profile information WhatsApp returns To answer the request you made
Technical data IP address, browser and request logs To operate, secure and fix the service

Passwords, session API keys and personal access tokens are stored only as hashes, so nobody can read them back. Webhook signing secrets and proxy URLs are stored as they are, because the service needs them, protected by the database's encryption and access controls.

3. How long we keep it

  • Message logs, session events and webhook deliveries: 30 days, then deleted automatically. A customer can clear a session's message log at any time.
  • Message content: only until the message is sent, unless the customer turns on message logging for that session.
  • Account and billing data: while the account exists, and billing records as long as accounting law requires.
  • Backups: kept up to 7 days, then overwritten.

4. Where it is stored and who processes it

Warsita runs on Google Cloud in Jakarta, Indonesia. We use a small number of service providers, listed with their role on the Subprocessors page. Messages travel over WhatsApp's network to their recipients because the customer sends them there; WhatsApp handles them under its own terms and privacy policy.

We do not sell personal data, and we do not use Customer Data to advertise or to train models.

5. Security

All traffic uses TLS. The database is encrypted at rest and reachable only by the service. Staff access the admin console with a password and a second factor (a passkey or an authenticator code), and every change they make is logged. Access to production systems within Warsita is limited to the people who need it.

6. Cookies

The website sets no cookies. The dashboard and the admin console set one session cookie each, which keeps you signed in, and remember your light or dark theme in your browser's storage. We use no advertising or analytics cookies.

7. Your rights

You can ask to access, correct, or delete your personal data, to receive a copy of it, or to object to or limit how we use it. Workspace owners can change most data in the dashboard themselves. For anything else, email hello@warsita.com; we answer within 30 days. Requests about Customer Data are passed to, or handled with, the customer responsible for it.

8. Changes

We will post changes to this policy here, and email workspace owners about material changes before they take effect.

9. Contact

Questions about privacy: hello@warsita.com.