The short version
- We collect only what we need to run your account, your servers and your billing.
- We don't sell your information. We use Google Analytics to count website visits, Google Ads to see which of our ads bring new customers, and Meta's pixel, which also helps Meta decide who sees our ads on Facebook and Instagram. In the EEA, the UK and Switzerland they set cookies only if you allow them; everywhere else you can switch each of them off in Cookie settings.
- Card details go straight to Stripe and PayPal details stay with PayPal. We never see your full card number.
- Your websites and the data of your visitors belong to you. We handle them only to host them.
- Mail in your mailboxes is yours. Nobody at Rabbitflare reads it: our systems scan it for spam and malware, and we look at a message only when our systems hold it for review, or when you ask us to.
- You can ask us to see, correct, export or delete your data at any time.
Who we are
Rabbitflare provides managed WordPress hosting on DigitalOcean, Vultr, Hetzner, Linode, Google Cloud and Amazon EC2, and on servers you connect yourself, through the website rabbitflare.com and the control panel at app.rabbitflare.com (together, the “Service”). Rabbitflare is a service of Rabbit Rank LLC, 701 Tillery Street, Unit 12-2508, Austin, TX 78702, United States (“Rabbitflare”, “we”, “us”). Payments for the Service are processed in the name of Rabbit Rank LLC.
For the personal information described in this policy, we are the data controller. This policy covers the Service, the emails we send and your conversations with our support. It does not cover the websites you host with us (see Your websites and visitors) or third-party websites, such as PayPal, that you may visit through the Service.
Information we collect
Information you give us
- Account details: your name, email address and password. We store your password only as a salted one-way scrypt hash, so we can't see or recover it.
- Sign in with Google: if you choose it, Google shares your name, your email address, whether Google has verified that address, and an identifier for your Google account, which we keep to recognize you next time. We never receive your Google password or access to anything else in your Google account.
- Sign in with GitHub: if you choose it, GitHub shares your public profile (your name and username), your email addresses and which of them GitHub has verified, and your GitHub account ID, which we keep to recognize you next time. We use GitHub's access only to read these once when you sign in, and don't keep it. We never receive your GitHub password or access to your repositories.
- Servers and sites: the names, plans and regions you choose; site names and titles; the domain names you connect; the WordPress administrator username and email address for each site; and the cron jobs you set up.
- Support messages: anything you send us when you contact support, sent through a ticket in the control panel or by email: your name, email address, the topic, your message and any files you attach.
- Hopper, the assistant on rabbitflare.com: the questions you ask it. If you use its “Message our team” form, also your name, email address and message, which reach us with your conversation as a support ticket. Please don't share passwords or other sensitive information in the chat.
Information created when you use the Service
- Sign-in and security data: for each signed-in session, a session identifier (stored hashed), the IP address and the browser user agent. We also briefly use IP addresses to limit repeated sign-up, sign-in, password-reset and support-form attempts, and questions to Hopper.
- Support ticket details: the IP address and browser user agent each support ticket was sent from, which we keep with the ticket to help us prevent abuse of the form.
- Server data: your servers' IP addresses and the WordPress administrator password we generate for each site, which we store encrypted (AES-256-GCM). We also collect resource metrics (CPU, memory, disk, load and bandwidth), from DigitalOcean's monitoring or, on the other clouds and your own servers, from the server itself, and the recent output of your cron jobs (the last 20 runs of each job). For Google Cloud and Amazon EC2 servers, we also read how much data each one sends, from Google Cloud Monitoring and Amazon CloudWatch, to bill data transfer.
- Servers you connect yourself: the IP address you give us, and what the server reports when it connects (its number of processors, memory, disk size, operating system and the hardware name its provider gives it). We manage it by signing in over SSH with our own key, which we remove when you disconnect the server. We never ask for its password.
- Activity log: a record of what happens to your servers and sites (for example “SSL certificate issued”), with the time and whether you, our systems or an administrator made the change.
- Files: when you use the File Manager, the files you open, edit or upload pass through our systems to and from your server. We don't keep copies of them.
- AI agent: if you switch it on, your tasks (what you write, your files, Claude's replies and every step it took on your server), and your AI credit balance, top-ups and usage.
- Rabbit Shield: if you turn it on for a server, what its scans find on your sites (where each finding is, a fingerprint of the file, which check found it and when), the plugins, themes and WordPress version each site runs, the scan history, what each clean-up changed so it can be undone, and who turned Rabbit Shield, Claude's second opinion or an AI clean-up on, and when. Files a clean-up moves to quarantine stay on your own server.
- Technical data: like any website, the servers that deliver our pages process your IP address, the page requested and the time, to deliver them and protect against abuse.
Information from payment providers
- Stripe (cards, Apple Pay and Google Pay): you enter card details into a secure Stripe form on our pages; they go directly to Stripe and never reach our servers. Stripe gives us identifiers for your customer record, subscriptions and saved cards, and each saved card's brand, last four digits and expiry date so we can show them to you.
- Billing name and address: when you pay by card, you give the full name and billing address for your bills. We pass them to Stripe, which keeps them on your customer record and saved cards and prints them on your invoices; we don't keep our own copy, and the Billing page reads them back from Stripe. Stripe also records when you agreed to card charges, and which person on your account agreed.
- PayPal: you approve payments on PayPal's website. PayPal gives us a subscription identifier, its status, and the email address of the PayPal account used.
- We keep the plan, price and status of each subscription, and invoice information from Stripe or PayPal to show your billing history.
Our website, rabbitflare.com, sets one cookie of its own, to remember your cookie choices, and our hosting network sets one security cookie. Optional cookies follow your cookie choices: in the European Economic Area, the UK and Switzerland they're used only if you allow them, and everywhere else they're on until you switch them off. The website uses Google Analytics. While analytics is on, it collects information about your visit: the pages you view, how you arrived, your browser and device, and your approximate location (from your IP address), and it uses cookies to recognize your browser on later visits. While it's off, it sets no cookies and Google receives only a basic signal for each page, with no identifier: the time, the page, the page you came from and your type of browser. Google Analytics doesn't store IP addresses. The control panel doesn't use Google Analytics.
We also advertise on Google. If you arrive from one of our ads while advertising measurement is on, Google Ads keeps the ad's click code in a cookie, and if you sign up, start a free trial or make your first payment within 90 days, the control panel tells Google Ads it happened, with the payment's amount. Google Ads doesn't receive your name, your email address or anything else you do in the control panel.
We also advertise on Facebook and Instagram. While Meta advertising is on, rabbitflare.com uses Meta's pixel, which tells Meta each page you view there, and the control panel tells Meta, through the same pixel, when you sign up, start a free trial or make your first payment, with the payment's amount, but not which page you're on. Meta also receives your IP address and your type of browser, and its cookies let it match all this to its ads: Meta uses it to measure our ads and to decide who sees them, so it may show you our ads. Meta doesn't receive your name, your email address or anything else you do in the control panel. See our Cookie Policy for every cookie we use and how to change your choices.
How we use it
We use personal information only for the purposes below. Where the GDPR or UK GDPR applies, the legal basis for each is shown in brackets.
- To provide the Service: creating your account, building and running your servers and sites, issuing SSL certificates, backups, Media Offload, cron jobs, the File Manager, and support (performance of our contract with you).
- To take payments and keep billing records (contract, and our legal obligations for accounting and tax).
- To send service emails: confirming your email address, password resets, when a server is ready, payment problems and changes to your subscription (contract).
- To tell customers about our own services: now and then, news about Rabbitflare and offers on our own services, such as a seasonal discount (our legitimate interest in telling customers about services like the ones they use). Each of these emails says how to stop them: reply “unsubscribe”, or use your mail app's Unsubscribe link, and we won't send you another. Service emails continue. We never give your address to anyone else for their marketing.
- To help you finish setting up a new account: a few reminders if you stop before confirming your email address or creating your first server, which you can stop from the email (our legitimate interest in helping you get started).
- To keep the Service secure: protecting accounts, preventing fraud and abuse, and investigating problems (our legitimate interest in a safe, reliable service).
- To fix and improve the Service using error logs and activity records (legitimate interests).
- To understand how our website is used, with Google Analytics: with cookies while analytics is on (in the EEA, the UK and Switzerland your consent, which you can withdraw at any time from Cookie settings; elsewhere our legitimate interest, and you can switch it off), and otherwise only the basic signal without cookies or an identifier (our legitimate interest in counting visits to our website).
- To measure our advertising, with Google Ads: whether a visit from one of our ads led to a sign-up, a free trial or a first payment, so we know which ads are worth paying for (in the EEA, the UK and Switzerland your consent, which you can withdraw at any time from Cookie settings; elsewhere our legitimate interest in measuring our own advertising, and you can switch it off).
- To advertise on Facebook and Instagram, with Meta's pixel: so Meta can measure our ads and show them to people likely to find Rabbitflare useful (in the EEA, the UK and Switzerland your consent, which you can withdraw at any time from Cookie settings; elsewhere our legitimate interest in advertising our service, and you can switch it off).
- To meet legal obligations, such as responding to lawful requests from authorities (legal obligation).
We don't build marketing profiles of our own, and we don't make automated decisions that have legal or similarly significant effects on you. The only use of what you do here to choose ads is Meta's, described above, and only while Meta advertising is on.
Who we share it with
We don't sell your personal information. While Meta advertising is on, Meta's pixel shares what's described above with Meta for advertising, and you can switch it off at any time in Cookie settings. Google Ads only tells us which of our ads led to a sign-up, a free trial or a payment. Apart from that, we share your information only with the service providers who help us run the Service:
| Provider | What they do for us | Privacy information |
|---|---|---|
| DigitalOcean | Hosts our website, control panel and database, and runs your servers, backups, snapshots and monitoring in the datacenter you choose. | Privacy policy |
| Vultr | Runs your servers, backups and snapshots in the location you choose, for servers you create on Vultr. Vultr is operated by The Constant Company, LLC. | Privacy policy |
| Hetzner | Runs your servers, backups and snapshots in the location you choose, for servers you create on Hetzner. Hetzner is operated by Hetzner Online GmbH, in Germany. | Privacy policy |
| Linode | Runs your servers, backups and snapshots in the location you choose, for servers you create on Linode. Linode is operated by Akamai Technologies, Inc. | Privacy statement |
| Google Cloud | Runs your servers in the region you choose, for servers you create on Google Cloud, and measures the data they send. Google Cloud is operated by Google LLC. | Privacy notice |
| Cloudflare | Delivers our website and control panel and protects them from attacks and bots, as part of DigitalOcean's hosting. | Privacy policy |
| Amazon Web Services | Runs the servers you create on Amazon EC2, in the location you choose, and the Amazon CloudFront CDN for sites whose owners switch it on, delivering those sites' images, CSS, JavaScript and fonts to their visitors. Its email service, Amazon SES, delivers the emails we send you. Our emails contain no open or click tracking. On Amazon EC2 servers with Rabbit Shield on, Amazon GuardDuty scans a copy of the server's disk for malware, in our AWS account, and deletes the copy after the scan. | Privacy notice |
| Rabbitflare Backup storage | Our cloud storage, run for us by cloud storage providers. It keeps the backups of sites that use Rabbitflare Backup, and the media files of sites that use Media Offload, private and encrypted at rest. | Covered by this policy |
| Stripe | Processes card, Apple Pay and Google Pay payments, stores saved cards, and screens payments for fraud. | Privacy policy |
| PayPal | Processes PayPal payments and subscriptions. | Privacy statement |
| Resend | Receives your email replies to our support emails, so they reach your support tickets. | Privacy policy |
| SMTP2GO | Delivers the WordPress emails of sites that use Rabbitflare SMTP, such as password resets, new-account emails and order emails, and mail sent from Rabbitflare Mail mailboxes to other providers. It tells us whether each email was delivered, bounced or reported as spam. | Privacy policy |
| Anthropic | Runs Claude, the AI model behind the AI agent, for customers who switch it on. What you write in a task, the files you attach, and what Claude reads on your servers while it works (files, command output, logs) are sent to Anthropic to write its replies. Database passwords and WordPress keys are replaced with placeholders first. For Rabbit Shield, Anthropic also receives the suspicious files sent for Claude's second opinion, on servers where you turn it on, and what Claude reads on a site during an AI clean-up you start. Anthropic doesn't use this information to train its models. | Privacy policy |
| Google Gemini | Writes the answers of Hopper, the assistant on rabbitflare.com. Your questions and the conversation so far are sent to Google's Gemini API to create each answer. | Privacy policy |
| Lets you sign in with your Google account, if you choose to. | Privacy policy | |
| Google Web Risk | For Rabbit Shield, checks the addresses of your sites against Google's list of dangerous sites, so we can warn you if Google flags one. | Privacy policy |
| The antivirus engine's maker | On servers where Rabbit Shield's antivirus engine looks files up online, checks fingerprints of files (a short code worked out from each file, never the file itself) against its list of known malware. Under its licence it may also receive technical information about the server, such as installed software and the names and sizes of files; we switch off the optional sharing it allows. | Shown in the control panel when you turn Rabbit Shield on |
| Google Analytics | Counts visits to rabbitflare.com and shows us which pages are read. Its cookies follow your cookie choices. Not used in the control panel. | Privacy policy |
| Google Ads | Shows our ads on Google, and tells us when a visit from one of our ads leads to a sign-up, a free trial or a first payment (with the payment's amount). Its cookies follow your cookie choices. It doesn't receive your name or email address. | How Google uses cookies in advertising |
| Meta (Facebook and Instagram) | Shows our ads on Facebook and Instagram. While Meta advertising is on, its pixel tells Meta about visits to rabbitflare.com and when someone signs up, starts a free trial or makes a first payment (with the payment's amount), and Meta uses this to measure our ads and decide who sees them. Its cookies follow your cookie choices. It doesn't receive your name or email address. | Privacy policy |
| GitHub | Lets you sign in with your GitHub account, if you choose to. | Privacy statement |
| Let's Encrypt | Issues free SSL certificates for your domains. | Privacy policy |
| Google Trust Services | Issues free SSL certificates for staging copies, and for your domains when Let's Encrypt can't. It receives the domain names and your server's address, not your contact details. | Privacy policy |
Stripe and PayPal also act as independent controllers for some of the information they collect, for example to meet financial regulations and prevent fraud, and their own privacy policies apply to that. Please note that SSL certificates are publicly logged: every domain name we request a certificate for appears in public Certificate Transparency logs, as it does with any certificate authority.
We may also disclose information if the law requires it, to protect the rights, property or safety of our customers, the public or Rabbitflare, or to a buyer or successor if our business is ever sold or reorganized, in which case this policy continues to apply.
Where your data is stored
Our control panel and its database are hosted by DigitalOcean in New York, in the United States. Your servers, and the websites on them, run on the cloud and in the location you choose: DigitalOcean has 11 datacenters in North America, Europe and Asia Pacific, Vultr has 32 locations across North America, South America, Europe, Asia Pacific, the Middle East and Africa, and Hetzner has 3 locations in Germany and Finland, and Amazon EC2 has 17 locations in North America, South America, Europe and Asia Pacific, run by Amazon Web Services. A server you connect yourself stays with your own provider, in the location you chose there, under your agreement with them; we don't share your information with that provider. Rabbitflare Backup storage keeps each site's backups in the region chosen for them, in the United States, Europe or Asia Pacific, and Media Offload's media files in the United States. Our other providers may process data in the United States and other countries.
If you are in the European Economic Area, the United Kingdom or Switzerland, this means your personal information is transferred outside your country. Where we do this, we rely on appropriate safeguards, such as the European Commission's Standard Contractual Clauses (and the UK Addendum) included in our providers' data processing terms.
How long we keep it
- Account and server records: for as long as your account is open. When you ask us to delete your account, we delete or anonymize them within 30 days, except what we must keep by law.
- Billing records: kept as long as tax and accounting laws require, which is usually several years.
- Sign-in sessions: end after 30 days or when you sign out. Expired sessions are deleted within the hour.
- Password-reset and email-confirmation links: deleted once used or expired.
- Background tasks, including the details of emails queued for sending: deleted 14 days after they finish.
- Payment notification records from Stripe and PayPal: deleted after 90 days.
- Cron job output: only the 20 most recent runs of each job are kept.
- Website analytics: Google Analytics keeps visit data for up to 14 months. Turning analytics off in Cookie settings deletes its cookies from your browser.
- Advertising measurement: Google's ad cookies expire after 90 days. Turning advertising measurement off in Cookie settings deletes them from your browser.
- Meta advertising: Meta's cookies expire after 90 days. Turning Meta advertising off in Cookie settings deletes them from your browser. Meta keeps what it has received under its own policy.
- Support tickets: kept for two years, then deleted. Files you attach are removed from our systems once they've reached our support inbox, and after 14 days at the latest. Our email conversations with you stay in our support mailbox for as long as we need them to help you.
- Hopper conversations: kept only in your browser, until you close the tab. We don't store them, except a conversation you send to our team through Hopper's form, which is kept as a support ticket.
- AI agent tasks: until you delete them. Files you attach to a message but never send: one day. Restore points: 7 days, on your server.
- Rabbit Shield: findings and scan history for as long as the site exists. A clean-up can be undone for 30 days, and files in quarantine are deleted from your server after 30 days.
- Media Offload: a site's media stays in storage while Media Offload is on. Files you delete or replace in WordPress are kept for 30 days, then deleted. When you turn Media Offload off, storage keeps the site's copies for 7 days, and when you delete the site, for 3 days; then they're deleted.
- Your servers, sites, backups and snapshots: until you delete them. Destroying a server deletes it together with its sites, backups and snapshots. A server that is never paid for is removed after 48 hours.
Your websites and your visitors
The WordPress sites you host with Rabbitflare, and any personal information in them (such as your visitors' comments, orders or form entries), belong to you. For that information, you are the controller and we act as your processor: we store and process it only to host your sites and provide the Service, to keep it secure, to provide support you request, or where the law requires it. We never use it for our own purposes.
You are responsible for your sites' own privacy notices and for any consent your sites need, for example for cookies set by WordPress plugins. If you need a data processing agreement for your use of the Service, contact us.
Mailboxes you manage
For the content of the mailboxes you run on Rabbitflare Mail, and the personal information in it, you are the controller and we are your processor: we store and process it only to provide the service, keep it secure and welcome at other providers, give support you ask for, or where the law requires it. For the sign-in and security records of your mailbox users, and for our own abuse records, we are the controller. If you need a data processing agreement, contact us.
Nobody at Rabbitflare reads your mail. Messages our systems hold for review may be read by our staff, and by the account's administrators, to decide them. Support may look into a mailbox only with the account owner's written consent in a support ticket, for a limited time, and every such access is logged and notified to the mailbox and the owner.
An account's administrators can also open one of its mailboxes for up to 60 minutes, giving a reason. They can read it but not change anything, the opening is logged, and the mailbox's person is told when it starts and when it ends.
What we keep for mailboxes:
- Mailbox content: the messages, attachments, contacts and calendar entries in mailboxes, for as long as their users keep them.
- Mailbox users, who are usually our customers' staff: name, address, a salted hash of the password, two-factor and passkey records, a recovery address, the devices and sessions signed in, and sign-in events with the time, result, IP address, approximate location (country) and network, and the app or browser used.
- Delivery metadata: for mail sent from a mailbox, who wrote to whom, when, the size, the outcome (delivered, bounced, complained) and bounce reasons; for mail received, the sending server, authentication results and the spam score.
- Held messages and abuse reports: messages our systems hold for review, and reports people send to our abuse desk, including the headers they paste.
- Reports from other providers about our customers' domains (DMARC and TLS reports): sending server addresses and counts, with no message content.
How we use it:
- To provide the mailboxes, webmail and apps (our contract with you), and to bill for them (contract and law).
- To keep mail secure and welcome at other providers: scanning every message for spam, phishing and malware, watching for compromised mailboxes, suppressing addresses that bounced or complained, and working out where a sign-in came from to detect takeovers (our legitimate interest in a safe service and in our customers' mail being delivered). The location database used for this runs on our own server, and nothing is sent to anyone for it.
- To answer lawful requests (legal obligation).
Who handles it for us:
| Provider | What they do for us | Privacy information |
|---|---|---|
| Rabbitflare Mail servers and storage | Run for us by a European data-centre provider in Helsinki, Finland. Message bodies are kept in a private storage bucket in the European Union, run for us by a cloud storage provider. The mail index and metadata are encrypted. | Covered by this policy |
| Email delivery partners | Carry mail from mailboxes to other providers, in the European Union and the United States, and tell us when a message was delivered, bounced or reported as spam. A partner may keep a sample of about one message in a thousand for 35 days to investigate abuse. Mail between Rabbitflare Mail mailboxes never leaves our server. | Covered by this policy |
| Rabbitflare Mail backup storage | Our backup storage in the European Union, run for us by a cloud storage provider. Backups are encrypted before they leave our server. | Covered by this policy |
Where it's stored: mailbox content is stored in the European Union and backed up, encrypted, within the European Union. Mail you send to other providers passes through our delivery partners in the European Union and the United States. Where that involves a transfer outside your country, we rely on the Standard Contractual Clauses in their terms.
How long we keep it:
- Mail: until the user deletes it. Trash and Spam are emptied after 30 days.
- A deleted mailbox or domain: recoverable for 30 days, then deleted. Copies in our mail backups are deleted within a further 90 days, and the storage's own version history within 7 days.
- Exports: kept for 30 days, and each download link works for 24 hours.
- Delivery metadata: recipient addresses for 30 days, then only as hashes; counts and rates for two years.
- Sign-in events and device records: 180 days.
- Held messages: at most 72 hours.
- Server logs: 30 days on the server, one year in encrypted backups.
- DMARC and TLS reports: 90 days.
- Abuse reports and the actions we took: kept with our records of the account.
Security: two-factor sign-in and passkeys for mailbox users, an app password per device, encryption of the mail index, metadata and backups at rest, message bodies in a private bucket that only the mail server can reach, and every administrative action logged.
Security
We protect your information with measures including:
- Encryption in transit (HTTPS) everywhere, and secure, HttpOnly session cookies.
- Passwords stored only as salted scrypt hashes, and WordPress administrator passwords encrypted at rest with AES-256-GCM.
- Card details handled only by Stripe, a PCI DSS Level 1 certified payment provider.
- A firewall, brute-force protection and automatic security updates on every server, and each site isolated under its own system user and database.
- Access to production systems limited to the people and automation that need it.
No system is perfectly secure. If we become aware of a breach that affects your personal information, we will notify you and the relevant authorities as the law requires.
Your rights
You can update your name, email address and password at any time in the control panel's Settings. For anything else, email [email protected] from the address on your account and tell us what you need. We don't charge for this, and we'll reply within 30 days.
If you are in the EEA, the UK or Switzerland
You have the right to access your personal information, correct it, have it deleted, restrict or object to how we use it, and receive it in a portable format. Where we rely on your consent, you can withdraw it at any time. You also have the right to complain to your local data protection authority, though we'd appreciate the chance to help first.
If you are in California or another US state with privacy laws
You have the right to know what personal information we collect and how we use and disclose it, to access it, to correct it, and to have it deleted. We don't sell personal information. While Meta advertising is on, Meta's pixel shares information with Meta for advertising, which some state laws call sharing for targeted advertising: you can opt out at any time by switching Meta advertising off in Cookie settings. Our Google Ads measurement only tells us which of our ads worked, and you can switch it off there too. We don't use sensitive personal information to infer characteristics about you. You may use an authorized agent to make a request, and we won't discriminate against you for exercising any of these rights.
Children
The Service is for businesses and adults. It isn't directed at children under 16, and we don't knowingly collect their personal information. If you believe a child has given us personal information, contact us and we'll delete it.
Changes to this policy
We may update this policy as the Service changes. We'll change the “Last updated” date above, and if a change is significant we'll email you before it takes effect.
Contact us
For questions about this policy or your personal information, email [email protected], or write to us at:
Rabbit Rank LLC701 Tillery Street, Unit 12-2508
Austin, TX 78702
United States