Skip to content
Apinator
FeaturesSDKsUse casesCompareFree tierDocs
Sign in Get started free
FeaturesSDKsUse casesCompareFree tierDocs Sign in Get started free

Privacy Policy

Last updated: October 2026

Apinator ("Service", "we", "us") is a free WebSocket infrastructure service operated by an individual based in Austria. We take your privacy seriously and process your data in accordance with the EU General Data Protection Regulation (GDPR) and Austrian data protection law (DSG).

1. Data Controller

The data controller responsible for processing your personal data is:

Shpetim Islami
Vienna, Austria
Email: [email protected]

2. What Data We Collect

Account Data

When you create an account, we collect:

  • Email address
  • Name (if provided)
  • Organization name (if provided)
  • Hashed password (we never store plaintext passwords)
  • If you sign in with GitHub or Google: the email address (and, from Google, your name and profile picture URL) that the provider shares with us

Usage Data

When you use the Service, we automatically collect:

  • Connection counts and message volumes (for billing/quota enforcement)
  • API request metadata (timestamps, endpoints accessed)
  • Channel subscription patterns (which channels your application uses)

Server Logs

Our servers write operational logs, which can contain:

  • Request method, path, status code and timing
  • Your email address, when we send you an email
  • The origin, user agent and app key of WebSocket connections we refuse
  • IP addresses and request headers, in web-server error entries

Logs never contain the content of messages sent through your channels. They are forwarded to our monitoring provider, Grafana Labs (see section 5), and kept for at most 30 days. We use them only for debugging, security monitoring and abuse prevention. Our network provider, Cloudflare, also processes IP addresses and request metadata for every request (see section 5).

Cookies

We use strictly necessary cookies only:

  • rt_access — authentication token (httpOnly, secure, session)
  • rt_refresh — refresh token (httpOnly, secure, persistent)

We do not use tracking cookies, analytics cookies, or any third-party advertising cookies.

3. How We Use Your Data

We process your personal data for the following purposes:

  • Service operation — to authenticate you, manage your account, and provide the WebSocket infrastructure (legal basis: contract performance, Art. 6(1)(b) GDPR)
  • Usage tracking — to enforce usage quotas and display usage statistics in your dashboard (legal basis: contract performance, Art. 6(1)(b) GDPR)
  • Security and abuse prevention — to protect the Service and its users from abuse, fraud, and security threats (legal basis: legitimate interest, Art. 6(1)(f) GDPR)
  • Service communication — to send important service-related notifications such as security alerts or changes to the Service (legal basis: legitimate interest, Art. 6(1)(f) GDPR)
  • Sign-in with GitHub or Google — if you choose it, to create and authenticate your account from the identity the provider shares with us (legal basis: contract performance, Art. 6(1)(b) GDPR)
  • Onboarding reminders — if you sign up but don't finish setting up, we may send you up to one short reminder per setup step. Every reminder has a one-click unsubscribe link, and we never send another after you unsubscribe (legal basis: legitimate interest, Art. 6(1)(f) GDPR)

4. What We Do NOT Do

  • We do not sell your personal data to third parties
  • We do not use your data for advertising or profiling
  • We do not use analytics or tracking services
  • We do not share your data with data brokers
  • We do not read the content of messages transmitted through WebSocket channels or keep a history of them — message data is relayed in real time and is not written to a database or to logs. The only exceptions are the short-lived realtime data listed in section 6.

5. Third-Party Services

We use the following processors. Each processes data only on our instructions, under a Data Processing Agreement (DPA) in line with Art. 28 GDPR.

  • Hetzner Online GmbH (Germany) — server hosting in Nuremberg, Germany, and, for applications created in the us region, in Ashburn, Virginia, USA.
  • Cloudflare, Inc. (USA) — network, DDoS protection and TLS for our website, dashboard, API and WebSocket endpoints, and hosting for the website and dashboard. All traffic to the Service passes through Cloudflare, which processes IP addresses and request metadata and handles message data in transit. It does not store message content.
  • Grafana Labs (USA; data stored in Germany) — log and metrics storage for monitoring and debugging (see "Server Logs" in section 2).
  • Resend (Plus Five Five, Inc., USA) — delivery of account emails (verification, password reset, notifications and onboarding reminders), sent from Ireland. Resend receives your email address, name and the content of these emails, and keeps its email records in the USA.

Sign-in Providers

If you choose to sign in with GitHub (GitHub, Inc.) or Google (Google Ireland Ltd.), you sign in with that provider directly, and it shares your email address (and, for Google, your name and profile picture) with us. The provider's own privacy policy applies to that sign-in.

6. Data Retention

  • Account data — retained for as long as your account exists. Deleted within 30 days of account deletion.
  • Usage records — retained for up to 12 months for quota tracking purposes.
  • Server logs — retained for a maximum of 30 days.
  • Unverified accounts — accounts whose email address is never verified are deleted 30 days after sign-up.
  • Rate-limit counters — IP addresses used to rate-limit sign-up and sign-in are kept for up to one hour.
  • WebSocket message data — not stored. Messages are relayed in real time and dropped once delivered. Two kinds of realtime data are held briefly in memory on the realtime servers of the region your application was created in, and may also be in the snapshot those servers write to their own disk about once a minute:
    • Cache channels — the last event published to each cache channel, including its data. Replaced by every publish and deleted 30 minutes after the last one.
    • Presence channels — the user ID and user information your application supplies for each member. Kept while the member is subscribed and removed when they leave, or about a minute after a server failure.

7. Your Rights Under GDPR

As a data subject in the EU, you have the following rights:

  • Right of access (Art. 15) — request a copy of your personal data
  • Right to rectification (Art. 16) — correct inaccurate personal data
  • Right to erasure (Art. 17) — request deletion of your personal data
  • Right to restriction (Art. 18) — restrict processing of your personal data
  • Right to data portability (Art. 20) — receive your data in a machine-readable format
  • Right to object (Art. 21) — object to processing based on legitimate interests

To exercise any of these rights, please contact us at [email protected]. We will respond within 30 days.

8. Data Transfers

Account data and usage records are stored in the European Union (Nuremberg, Germany), and so is the realtime data of applications in the eu region. If you create an application in the us region, its WebSocket traffic is handled, and the short-lived realtime data described in section 6 is held, on Hetzner servers in Ashburn, Virginia, USA. Our contract for these servers is with Hetzner Online GmbH in Germany. The Ashburn data center is operated for Hetzner by Hetzner US LLC. Only the data of applications you choose to create in the us region is processed there. Your account data stays in the EU.

Some of our processors are based in the USA, or may access data from there: Cloudflare, Grafana Labs and Resend. Cloudflare may serve your request from the data center nearest to you, including outside the EU. Resend stores email records in the USA. These transfers rely on the EU Commission's adequacy decision for the EU-U.S. Data Privacy Framework, for providers certified under it, and on the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR) in each provider's DPA. You can request a copy of the relevant safeguards at [email protected].

Our website loads no fonts, scripts or other assets from third parties.

9. Security

We implement reasonable technical and organizational measures to protect your data, including encrypted connections (TLS), hashed passwords, and access controls. However, as stated in our Terms of Service, no service can guarantee absolute security.

10. Children

The Service is not directed at children under 16. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us so we can delete it.

11. Changes to This Policy

We may update this Privacy Policy from time to time. The "last updated" date at the top indicates the latest revision. Continued use of the Service constitutes acceptance of the updated policy.

12. Supervisory Authority

If you believe your data protection rights have been violated, you have the right to lodge a complaint with the Austrian Data Protection Authority:

Österreichische Datenschutzbehörde
Barichgasse 40–42, 1030 Vienna
www.dsb.gv.at

13. Contact

For any privacy-related questions or requests, please contact:
[email protected]

Apinator

Free, hosted WebSocket infrastructure with open-source SDKs. A community project.

Product

  • Features
  • Documentation
  • Status
  • Blog

Use cases

  • Live chat
  • Notifications
  • Dashboards
  • Multiplayer
  • All use cases

SDKs

  • JavaScript
  • Node.js
  • Python
  • Go SDK
  • PHP
  • Swift

Compare

  • Pusher alternative
  • Ably alternative
  • Bird alternative
  • Free WebSocket server
  • Managed WebSockets

About

  • Privacy
  • Terms
  • Imprint
  • GitHub
© 2026 Apinator · Free forever ws://realtime · MIT SDKs