Privacy Policy
Last updated: 19 November 2026
This policy explains how abit, the operator of Pingrota ("we", "us"), handles personal data. For the data your organization puts into Pingrota we act as a processor on your behalf; for account, billing and website data we are the controller. Contact: response@abit.co.il.
What we collect
| Data | Examples | Why |
|---|---|---|
| Account data | Name, work email, position, organization name and role | Sign-in, invitations, showing who is on call |
| Contact channels | Phone number (stored encrypted, used only after you verify it), WhatsApp opt-in, push device tokens, notification preferences | Paging you the way you chose |
| Customer Data | Alerts and their payloads, incidents, notes, schedules, time off, postmortems | Running the service for your organization |
| Billing data | Plan, Paddle customer and subscription IDs, card brand and last four digits | Billing and automatic upgrades. Full card details are held by Paddle, never by us |
| Technical data | IP address, request logs, audit log of changes | Security, abuse prevention, troubleshooting |
We do not sell personal data, use it for advertising, or build profiles. The marketing website sets no cookies and runs no trackers. The app uses one strictly necessary session cookie to keep you signed in.
Legal bases
We process account and Customer Data to perform our contract with your organization, technical and security data for our legitimate interest in a safe and reliable service, billing data to meet legal and contractual obligations, and phone and WhatsApp channels with the consent you give when you add them, which you can withdraw at any time in your profile.
Who processes data for us
| Provider | Purpose | Location |
|---|---|---|
| Microsoft Azure | Hosting the application and database | Israel (Israel Central) |
| Cloudflare | DNS, TLS, network protection, the marketing website | Global edge network |
| Paddle | Payments, invoicing and tax, as merchant of record | UK / EU / US |
| Google Workspace | Sending email | Global |
| Meta (WhatsApp Business) | WhatsApp pages, if you opt in | Global |
| Apple, Google (Firebase), Expo | Push notifications to the mobile app | Global |
| Slack | Incident messages, if your organization connects it | Global |
| Twilio (your own account) | SMS and phone calls, if your organization connects Twilio; Twilio processes these under your agreement with it | Global |
Where data leaves Israel or the EEA, the transfer relies on adequacy decisions or the providers' standard contractual clauses.
How long we keep it
- Raw alert request bodies: 14 days.
- Notification delivery attempts: 90 days.
- Incidents, notifications, alert receipts and the audit log: 400 days after the incident resolves (open incidents are kept while open).
- Sessions and sign-in links: until they expire.
- Account data: while the account exists; billing records as long as tax law requires (Paddle keeps its own).
Security
Each organization's data is isolated in the database with row-level security. Traffic is encrypted in transit, secrets such as phone numbers and third-party tokens are encrypted at rest, and access to production systems is limited to the operators who run Pingrota.
Your rights
Depending on where you live (for example under the GDPR or Israel's Protection of Privacy Law), you may ask to access, correct, delete, restrict or export your personal data, object to processing, or withdraw consent. You can edit your profile and contact channels yourself in the app. For Customer Data, contact your organization's admin first; we help them answer requests. Otherwise write to response@abit.co.il; we reply within 30 days. You may also complain to your data protection authority.
Changes
We will post updates here and, for material changes, email account owners and admins in advance.