Privacy policy
Last updated: June 17, 2026
INTRODUCTION
1.1
This Privacy Policy explains what personal data we collect when you use Flipper’s BUSY service – the busy.app website, the BUSY app, the BUSY Cloud, and the BUSY Bar device – and what we do with it.
1.2
“We”, “us”, and “Flipper” mean Flipper Devices, Inc. (USA) and Flipper FZCO (UAE), which are independent controllers for different parts of the BUSY service. The full allocation – which entity controls which processing, with addresses and contact points – is on our Controllers Page (Annex 1).
1.3
What this policy covers: the BUSY hardware and software service, our website, the BUSY mobile and desktop apps, the BUSY Cloud, our customer support, and our recruitment activities.
1.4
What this policy does not cover: third-party services you choose to connect to BUSY (such as a calendar provider, an OAuth identity provider, or your own server connected via supported IoT protocols). Those are governed by the third party’s own privacy policy.
1.5
For US state-specific rights, see Annex 2 — US States Privacy Notice.
WHO CONTROLS YOUR DATA
2.1
Flipper Devices, Inc. and Flipper FZCO are independent controllers for distinct parts of the service. Inc. controls sales, payment processing, shipping, and logistics data. FZCO controls the website, the BUSY app, BUSY Cloud, device firmware, and analytics. The mapping of processing activities to controlling entities, with addresses and the relevant supervisory authorities, is on our Controllers Page (Annex 1). You can reach any of us at the addresses in Section 12.
WHAT WE COLLECT AND WHY
3.1
When You Visit Our Website. When you visit our website, we receive standard information that your browser sends, such as:
IP address, approximate location derived from it, and language/timezone settings;
browser type and operating system;
pages you view, the page that referred you, links you click, and time spent;
session and error logs needed to keep the site working.
3.2
We use cookies and similar technologies for site operation, security, analytics, and advertising. Strictly-necessary cookies run by default. Analytics, advertising, and other non-essential cookies run only with your consent, which you give and withdraw through our consent banner. Details, vendor names, and cookie lifetimes are in our Cookie Policy.
3.3
We work with online advertising and analytics providers so that advertising you see is more relevant and so that we can measure how our marketing performs. We do this only with your consent. The named providers are listed in our Cookie Policy. Under the California Consumer Privacy Act, some of these activities are considered “sharing” of personal information, and you have the right to opt out – see our US States Privacy Notice.
Purpose |
Legal basis |
|---|---|
Operating the website, security, fraud prevention |
Art. 6(1)(f) legitimate interests |
Analytics, advertising, and measurement |
Art. 6(1)(a) consent (via consent banner) |
Responding to specific requests you make on the site |
Art. 6(1)(b) performance of a contract / pre-contract steps |
3.4
When You Create a Flipper Account. To use the BUSY app and the BUSY Cloud, you create an account. We collect:
email address and password;
if you sign in with Apple, Google, or Microsoft instead, the identifier the provider returns to us and, depending on your settings with that provider, your name and email;
if you set up a passkey, the credential we need to verify it;
optional profile information you choose to add (name, country, profile photo).
Purpose |
Legal basis |
|---|---|
Creating and maintaining your account, authenticating you |
Art. 6(1)(b) performance of a contract |
Account security, fraud and abuse prevention |
Art. 6(1)(f) legitimate interests |
Service announcements relating to your account |
Art. 6(1)(b) performance of a contract |
Optional marketing communications |
Art. 6(1)(a) consent |
3.5
When You Place an Order. When you buy a BUSY product, Flipper Devices, Inc. – acting on our behalf as seller of record in your region – collects what we need to take and fulfill your order:
contact details (name, email, phone if you provide it);
shipping and billing address;
the items, quantities, prices, and order history;
payment confirmation and a tokenized reference to your payment method – full card numbers and bank details are handled by our payment processor (Shopify Payments) and are not stored on our systems;
invoices, receipts, returns, and refunds.
3.6
We share order data with the parties we need to deliver it: payment processor (Shopify Payments), shipping carrier and regional fulfillment partner for your region, and tax authorities when legally required.
Purpose |
Legal basis |
|---|---|
Taking and fulfilling your order, handling returns and refunds |
Art. 6(1)(b) performance of a contract |
Tax, accounting, and bookkeeping records |
Art. 6(1)(c) legal obligation |
Fraud and chargeback prevention |
Art. 6(1)(f) legitimate interests |
3.7
When You Connect Your BUSY Bar Device. Your BUSY Bar device pairs with the BUSY app and may connect to the BUSY Cloud (or, where supported, to your own server using standard IoT protocols). This section describes what the device and the app exchange.
3.8
What the device does not collect. BUSY Bar has no microphone and no camera, and it does not capture or transmit any ambient audio, video, or images. It also has no GPS receiver. Some auto-status features (such as the “On call” indicator on macOS) work by detecting locally on your computer that your Mac microphone is active. This detection runs on your device through the BUSY desktop app; no audio is captured, recorded, or transmitted to us, and the device itself does not listen or watch.
3.9
A light sensor is built into the device to adjust LED brightness automatically. Light-sensor readings are used on the device and are not transmitted to us.
3.10
You can adjust LED brightness in the device or app settings. Any related on-device readings are used locally and are not transmitted to us.
3.11
What the device and app exchange with us. When you pair, sync, or update your BUSY Bar, we may receive technical and operational data, such as:
firmware version and update events;
device model and a device identifier used to associate the device with your account;
storage and configuration status (e.g., free space, sync state);
connectivity events (for example, that a Bluetooth or Wi-Fi pairing occurred), without the contents of your network traffic;
features you activate on the device and in the app (for example, mode switches, session counts, brightness preferences);
images, media, or other content you upload through the BUSY app for display on your BUSY Bar device;
your timezone setting and approximate location (if provided in your account settings), used to localize your session display;
API access tokens you generate to integrate the BUSY Cloud with third-party tools; these tokens are credential-equivalent and are stored securely;
crash and diagnostic data if the device or the app fails or behaves unexpectedly.
3.12
We use this data to operate, secure, and improve the product. Diagnostic and analytics processing for the device and app runs on infrastructure we host ourselves; it is not shared with those vendors as data recipients.
Purpose |
Legal basis |
|---|---|
Operating the device and the app, delivering features you request, OTA firmware updates |
Art. 6(1)(b) performance of a contract |
Protecting the service against abuse, fraud, and security incidents |
Art. 6(1)(f) legitimate interests (security) |
Diagnosing crashes and improving stability and features |
Art. 6(1)(f) legitimate interests (product quality) |
Optional push notifications |
Art. 6(1)(a) consent |
Delivering security updates (device identifier, firmware version, update status, error logs from the update process) |
Art. 6(1)(b) performance of a contract (security updates form part of the product you purchased); (f) legitimate interests (maintaining product security) |
3.13
Self-hosted option (your own server). If you connect your BUSY Bar to your own server using a supported standard IoT protocol, the data exchanged with that server is controlled by you, not by Flipper. Our Privacy Policy does not cover that flow.
3.14
Additional data from the BUSY app. In addition to the device data above, the BUSY app itself produces:
screens you view in the app, features you activate, and broad usage patterns – through self-hosted analytics;
crash and performance logs if the app misbehaves – through self-hosted crash reporting;
push notification token, if you allow notifications;
if you connect Google Calendar or another supported integration, the tokens and the calendar metadata needed for the integration to work (see the “Calendar and similar integrations” subsection below).
3.15
We do not read the content of your communications inside the app for marketing or AI-training purposes. See the “AUTOMATED SYSTEMS, AI, AND DECISIONS ABOUT YOU” section below.
3.16
When You Contact Support. When you write to us by email, fill in a form, or otherwise reach out:
we receive the content of your message, any attachments you send, and your contact details;
we keep a history of your support tickets and our replies so that we can resolve your issue and improve service quality.
3.17
Support data is processed by Flipper FZCO and, where the issue relates to an order, by Flipper Devices, Inc. on our behalf, using the customer-support tooling listed on our Subprocessors page (Annex 3).
Purpose |
Legal basis |
|---|---|
Responding to you and resolving your issue |
Art. 6(1)(b) performance of a contract; (f) legitimate interests where no contract exists |
Quality assurance and training of our support team |
Art. 6(1)(f) legitimate interests |
Keeping records of complaints we are required to keep |
Art. 6(1)(c) legal obligation, where applicable |
3.18
Recruitment. Flipper FZCO handles recruitment for our group. If you apply, we collect what you send us – CV, cover letter, contact details, references – and process it to assess your application (Art. 6(1)(b) – pre-contractual steps). With your consent, we may keep your profile for future opportunities. We do not share your application outside the Flipper group except where you ask us to (for example, a reference you provided).
3.19
What We Receive from Third Parties. In a few situations we receive personal data about you from other sources:
Sign-in providers. If you create your account using Apple, Google, or Microsoft sign-in, we receive an identifier and, depending on your settings, your name and email from that provider (see Section 3.4).
Calendar and similar integrations. If you connect Google Calendar, the BUSY app receives the calendar metadata required to display your status correctly (such as event times, titles, attendee count). We do not use this data for advertising, and we do not use it to train AI models – see the “AUTOMATED SYSTEMS, AI, AND DECISIONS ABOUT YOU” section below. We do not retain it longer than needed to operate the integration.
3.20
Where we receive personal data from third parties, we use it for the same purposes for which we collect it directly and on the same legal bases.
LEGAL BASES (GDPR / UK GDPR)
4.1
Where we rely on legitimate interests. We have weighed our legitimate interests against your rights and concluded that the processing is necessary and proportionate. Our reasons:
4.2
Website and service operation. We need to serve you pages, process your requests, and maintain site and service functionality. This processing is inherent to the service and limited to operational data.
4.3
Security, fraud, and abuse prevention. We need to keep your account, our service, and our payment flow safe. Without this processing, the service is unsafe to operate. Data is limited to what is needed; we do not profile users for purposes beyond protection.
4.4
Diagnostics and improvement. We need to know when the device or the app fails, and how customers use BUSY, to fix problems and decide what to build next. Diagnostic and analytics processing runs on infrastructure we host ourselves.
4.5
Quality assurance for support. We use our own support interactions to coach our team and improve responses, not to evaluate individual users.
4.6
You can object to processing based on legitimate interests at any time (see Section 8 Your Rights). When we receive an objection we re-assess whether our interest overrides yours; if it does not, we stop.
4.7
Whether you must provide your data. Providing your personal data is not a statutory obligation. However, certain data – such as your email address, shipping address, or payment details – is necessary for us to create your account, process your order, or operate the service. If you choose not to provide it, we may not be able to provide the relevant part of the BUSY service to you.
4.8
Where we rely on consent. You can withdraw consent at any time, without affecting processing already carried out on that basis. We will not penalize you for withdrawing consent for analytics, advertising, or marketing emails.
HOW WE SHARE DATA
5.1
Within the Flipper group. Flipper Devices, Inc. and Flipper FZCO share data with each other where necessary to deliver the service. Each controller is independently responsible for what it processes; an Intra-Group Cooperation Agreement covers data sharing and Standard Contractual Clauses for cross-border flows (supplemented by the UK International Data Transfer Addendum where applicable).
5.2
Service providers. We use third-party service providers (“processors” and, in some cases, recipients) to operate the service, including:
payment processing (Shopify Payments);
order fulfillment, shipping, and returns logistics;
cloud hosting;
crash and analytics infrastructure that we host ourselves;
communications and email delivery;
consent management;
security, anti-fraud, and abuse detection;
customer-support tooling.
5.3
The current list of named service providers – together with their roles, locations, and the categories of personal data they process – is published on our Subprocessors page (Annex 3.
5.4
Advertising and analytics partners. With your consent, we work with advertising and analytics partners to deliver and measure marketing on our website. The named partners are listed in our Cookie Policy and on our Subprocessors page (Annex 3). For CCPA opt-out rights, see our US States Privacy Notice (Annex 2).
5.5
Third parties at your direction. If you log in with a social identity provider, connect a calendar, or use a third-party integration, we exchange data with that provider as needed to operate the integration you asked for.
5.6
Legal, protective, and corporate-transaction disclosures. We may disclose personal data when we are legally required to do so – for example, in response to a lawful request from a public authority, to comply with a court order, or to protect the rights, property, or safety of users, Flipper, or others. We may also disclose personal data in connection with a merger, acquisition, financing, restructuring, or asset sale, subject to confidentiality and to the protections of this policy.
INTERNATIONAL TRANSFERS
6.1
Flipper FZCO is based in the United Arab Emirates; Flipper Devices, Inc. operates from the United States. Our service providers are based in several countries. Your personal data may therefore be transferred to, and processed in, countries outside your own.
6.2
For transfers out of the EEA or the UK, we rely on the European Commission’s Standard Contractual Clauses, supplemented by the UK International Data Transfer Addendum where applicable.
HOW LONG WE KEEP YOUR DATA
7.1
We keep personal data for as long as we need it for the purposes set out in this policy, and then we delete or anonymize it. How long that takes depends on the category of data and on the legal, contractual, and operational reasons we have to keep it.
7.2
For the most common categories:
Category |
Retention period |
Clock starts |
|---|---|---|
Account profile data |
While your account is active, and for up to 12 months after deactivation or deletion as a grace period to allow you to restore the account and to resolve any pending disputes, transactions, or legal obligations. After this period, account data is deleted or anonymized. |
Account deletion |
Order and payment records, invoices, receipts |
Up to 7 years, in line with tax and accounting laws of the jurisdiction of sale |
Date of the transaction |
Marketing audiences and engagement data (for analytics and tailored communications) |
Until you unsubscribe or otherwise opt out |
Opt-out |
Marketing consent logs (proof of consent, opt-outs) |
Up to 6 years after consent change, in line with applicable limitation periods |
Consent change |
Website cookies and similar identifiers |
As set out in our Cookie Policy |
Last interaction |
Server-side analytics events (web and in-app) |
Up to 24 months from the event date for analytics purposes; reviewed periodically |
Event date |
Product analytics events |
Until you object to this processing or unsubscribe; we anonymize older events for long-tail analytics |
Objection / unsubscribe |
Calendar and integration data |
While the integration is active; deleted when you disconnect the integration |
Disconnection date |
Crash and error reports |
Up to 90 days for raw error reports; up to 12 months for aggregated debugging data |
Report date |
Firmware and device-side diagnostic logs |
Up to 12 months |
Collection date |
Security update delivery metadata (device identifier, firmware version, update status) |
While the device is supported under our security update commitment (§8 Terms of Sale (Security Update Support Period) / §9 Terms of Service (Firmware and OTA Updates)), plus 12 months for diagnostic purposes |
End of security support period |
Support tickets and correspondence |
3 to 6 years after resolution, depending on the jurisdiction of sale and applicable limitation periods |
Resolution date |
Job applications (unsuccessful) |
A reasonable period after a hiring decision (in line with employment-claims limitation periods in your jurisdiction); longer with your consent if you join our talent pool |
Decision date |
Backup and disaster-recovery copies |
Overwritten on our normal backup rotation cycle |
Deletion in primary system |
7.3
Where we keep data for longer than the periods above – for example, to defend a legal claim, to comply with a regulator’s order, or because anonymized data no longer identifies you – we limit further use to that purpose only.
7.4
When you ask us to delete your data, we delete it from our active systems on the timelines required by law (typically within one month under the GDPR / UK GDPR, 45 days under the CCPA, extendable where permitted). Residual copies in backups age out on the cycle above and are not used during that window except for system restoration.
YOUR RIGHTS
8.1
Depending on where you live, you have rights over your personal data. We honor these rights for all our users globally where it is technically and legally practical, and in addition to the specific rights granted by the laws of your jurisdiction.
8.2
You generally have the right to:
access the personal data we hold about you and obtain a copy;
correct data that is inaccurate or incomplete;
delete data we no longer need to keep;
port data you provided to us, in a structured machine-readable format;
object to processing based on our legitimate interests;
restrict processing in specified situations;
withdraw consent at any time, for processing that depends on consent;
lodge a complaint with your supervisory authority (see Annex 1 for the relevant authorities) and to seek a judicial remedy.
8.3
We respond to rights requests within the time required by your jurisdiction – typically within one month under the GDPR / UK GDPR and 45 days under US state laws, with extensions where permitted. We do not charge a fee unless your request is manifestly unfounded or excessive, in which case we may charge a reasonable fee or refuse to act and tell you why.
8.4
How to exercise your rights:
by email to privacy@flipper.net.
8.5
Account deletion and data export are currently handled on request – please email us and we will process your request within the timelines above.
8.6
Additional jurisdiction-specific instructions for US residents are in our US States Privacy Notice (Annex 2).
CHILDREN
9.1
The BUSY service is intended for general audiences and is not directed at children. We do not knowingly collect personal information from children under the minimum age set by applicable law in your region – generally 16 in the EEA / UK (subject to local variations under Art. 8 GDPR) and 13 in the United States under COPPA. We do not actively verify age.
9.2
If we learn that a user is below the applicable minimum age, we will delete their personal data without undue delay. If you believe a child has provided us with personal information, please contact privacy@flipper.net.
HOW WE PROTECT YOUR DATA
10.1
We take appropriate technical and organizational measures to protect personal data against unauthorized or unlawful processing, accidental loss, destruction, or damage. We use industry-standard encryption for personal data in transit (TLS). Some data at rest may not be encrypted; where that is the case, we apply other technical and organizational measures appropriate to the risk (including access controls, logging, and network segregation). Internal access to production data is limited to a small number of authorized personnel.
10.2
No security measure is perfect. If we become aware of a personal-data breach that is likely to result in a high risk to your rights and freedoms, we will notify you without undue delay, and we will notify the relevant authorities on the timelines set by applicable law.
CHANGES TO THIS POLICY
11.1
We update this policy from time to time to reflect changes to the service, to our practices, or to the law.
11.2
Material changes will be notified to you before they take effect, by email or in-app notice.
11.3
Minor or clarifying changes are reflected in the “Last updated” date at the top of this policy.
CONTACT US
12.1
Privacy contact
12.2
Email: privacy@flipper.net
12.3
US-state privacy requests – see our US States Privacy Notice (Annex 2).
12.4
Entity addresses – see the Controllers Page (Annex 1).
EU representative (Art. 27 GDPR): Prighter EU Rep GmbH, Schellinggasse 3/10, 1010 Vienna, Austria
UK representative (Art. 27 UK GDPR): Prighter Ltd, 20 Mortlake High Street, London, SW14 8JN, United Kingdom
12.5
You can also lodge a complaint with the data protection authority of your country. The European Data Protection Board publishes a directory of national authorities at edpb.europa.eu/about-edpb/about-edpb/members_en; UK users can contact the Information Commissioner’s Office at ico.org.uk.
AUTOMATED SYSTEMS, AI, AND DECISIONS ABOUT YOU
13.1
Automated decision-making with legal or similarly significant effects. We do not make decisions about you based solely on automated processing – including profiling – that produce legal effects concerning you or similarly significantly affect you within the meaning of Art. 22 GDPR / UK GDPR.
13.2
We use automated tools to operate the service – analytics, crash diagnostics, security and fraud-prevention checks, support routing, and spam filtering. These are operational tools, not decisions about you.
13.3
AI and machine-learning models. We do not use the content of your communications with us, your data in the BUSY app, or telemetry from your BUSY Bar to train generalized AI or machine-learning models, whether our own or those of any third party.