Bloo Share Privacy Policy
Effective date: 2026-06-26
Last updated: 2026-06-26
Version: privacy-2026-06-26
This Privacy Policy explains how Bloo ApS processes personal data when you use the Bloo Share website, app, rental boxes, booking flow, payment flow, support channels, gift cards, and related services.
1. Who We Are
Bloo ApS is the data controller for personal data processed through Bloo Share unless this policy says otherwise.
Company details:
- Legal name: Bloo ApS
- CVR/VAT: DK44996677
- Address: Enghavevej 29, 4. th, 1674 København V, Denmark
- Email: support@blooshare.dk
- Phone: +45 91 84 03 33
2. Scope
This policy applies to:
- the Bloo Share mobile app;
- the Bloo Share website at blooshare.dk;
- paddleboard rental bookings and rental boxes;
- account creation, login, and account deletion;
- payments, refunds, gift cards, and receipts;
- customer support and in-app feedback;
- app diagnostics, analytics, push notifications, and security logs.
3. Summary
We process personal data to create accounts, provide rentals, process payments, unlock and manage rental equipment, send service messages, handle support and feedback, improve reliability, prevent misuse, and meet legal obligations.
We do not sell personal data.
Marketing messages are sent only where we have the required consent. Service messages about bookings, returns, safety, payments, or account administration are not marketing messages.
4. Data We Process
The table below describes the main processing activities.
| Processing activity | Data processed | Purpose | Legal basis | Retention |
|---|---|---|---|---|
| Account creation and login | Phone number, Firebase Auth UID, account metadata | Create and manage the account | Contract, GDPR Art. 6(1)(b) | Until account deletion plus the 30-day deletion processing period, unless retained for legal, accounting, dispute, safety, or fraud reasons |
| Anonymous/pre-account session | Transient Firebase anonymous auth UID for web guest reservations; no Firestore user document before conversion | Enable web users to browse locations and create future reservations without a full account. Account creation is required before the rental date. Converting to a full account creates a new UID — no data is migrated from the anonymous session. | Contract performance steps, Art. 6(1)(b) | Anonymous UID is abandoned on conversion or discarded on sign-out; no Firestore user profile is created for anonymous sessions |
| Social sign-in profile | Name (given/family) and email from Google or Apple sign-in, where you choose that login method | Populate your account and send booking/receipt communications | Contract, Art. 6(1)(b) | Account lifetime; deleted/anonymized on account deletion |
| In-ride operational contact | Phone number stored in account | Allow Bloo staff to reach the active customer by phone during a rental for safety or operational reasons (e.g. overdue return, safety concern, equipment issue) | Legitimate interests, Art. 6(1)(f) — operational necessity during an active rental | Used only during active rentals; not used for marketing; retained as part of the account record per the account retention schedule |
| Terms acceptance | User UID, accepted terms version, timestamp, language/version, signup or checkout context, booking ID if relevant | Prove which terms applied and when they were accepted | Contract, Art. 6(1)(b); legal claims/legitimate interests, Art. 6(1)(f) | Account or booking lifetime plus dispute/legal period |
| Bookings and rentals | Booking time, rental station/location, duration, booking ID, user ID, rental status | Provide the rental service | Contract, Art. 6(1)(b) | Account lifetime, then anonymized or retained only as needed for accounting, disputes, safety, or legal obligations |
| Payments | Payment status, transaction ID, limited payment metadata, Stripe customer/payment references | Process payments, refunds, chargebacks, accounting | Contract, Art. 6(1)(b); legal obligation, Art. 6(1)(c) | Accounting material retained for the current financial year plus 5 years where required |
| Gift cards | Buyer details, gift-card code, redemption history, payment records | Sell, deliver, redeem, and support gift cards | Contract, Art. 6(1)(b); legal obligation, Art. 6(1)(c) | Voucher log retained 5 years per Bogføringsloven (accounting records); redemption records retained until case resolution plus 24 months |
| Damage, loss, theft, and safety incidents | Uploaded photos, booking ID, user ID, support notes, damage reports | Handle safety incidents, damage claims, loss, theft, and disputes | Legitimate interests, Art. 6(1)(f); legal claims; legal obligation where applicable | Until case is resolved plus applicable legal/dispute period |
| First-party app error logs | app_errors: owner UID, route, booking ID, stack head, error message, source, platform, app version, build number, fatal flag, timestamp |
Debug errors, improve reliability, investigate security/support issues | Legitimate interests, Art. 6(1)(f) | 90 days unless needed for active support, security, or legal issue |
| Crash diagnostics | Crash reports, stack traces, ANR data, app/device state, installation/crash IDs (Firebase Crashlytics) | Diagnose crashes, improve app stability, investigate serious technical issues | Legitimate interests, Art. 6(1)(f) | 90 days (Firebase Crashlytics platform default) |
| In-app feedback | dev_feedback: user UID, free-text message, optional screenshot, locale tag, timezone offset, screen size, device pixel ratio, route path, location ID, app version, platform |
Receive feedback, diagnose issues, improve the product, respond to support requests | Legitimate interests, Art. 6(1)(f); contract where support-related; your explicit action for screenshots | 180 days unless needed for active support, security, or legal issue |
| Location/proximity | Medium-accuracy GPS coordinates while the app is open; local distance and paddle-back-time calculations | Show nearby rental boxes/platforms and support the rental/return flow | Contract, Art. 6(1)(b); device permission requested by the operating system | Location calculations are performed on your device and are not sent to the Bloo backend |
| Bluetooth/BLE | BLE device/proximity signals, connection status, unlock/session context, local unlock outcome logs, and background BLE scanning where needed for session continuity | Connect to and unlock rental equipment, assist equipment location and session management, support local troubleshooting | Contract, Art. 6(1)(b); legitimate interests, Art. 6(1)(f), for reliability and misuse prevention | BLE unlock outcomes are processed on your device and are not retained by the Bloo backend |
| Push service messages | Device token, notification preferences | Send booking reminders, return reminders, operational notices, safety notices | Contract, Art. 6(1)(b); legitimate interests, Art. 6(1)(f) | Until account deletion, token refresh, or opt-out where applicable |
| Push token linkage | fcm_tokens/{installationId} with userId, userRef, fcmToken |
Manage device tokens for push delivery and prevent notification errors | Contract, Art. 6(1)(b); legitimate interests, Art. 6(1)(f) | Delete on account deletion and when the token is rotated/refreshed; unused tokens expire after 12 months of inactivity |
| Customer support | Email/phone, message content, support history | Respond to requests and manage support cases | Contract, Art. 6(1)(b), or legitimate interests, Art. 6(1)(f) | 24 months after last contact unless an active dispute or legal obligation applies |
| Firebase Analytics | screen_view events, route/screen names, app activity, device/app metadata, and manual analytics events (including booking_id references) |
Understand app use, improve reliability and product design | Consent, Art. 6(1)(a) — analytics does not run until you actively consent in the app | 14 months |
| Persistent identifiers | installationId, app/device identifiers, notification token |
Security, diagnostics, push delivery, analytics (with consent), fraud/misuse prevention | Contract, consent, or legitimate interests depending on purpose | Deleted/unlinked on account deletion, token rotation, or withdrawal of consent, as applicable |
| Fraud and misuse prevention | Booking history, payment status, incident records, access/security records | Protect users, equipment, and Bloo from misuse, fraud, damage, theft, and unlawful activity | Legitimate interests, Art. 6(1)(f) | Retained for the period necessary to investigate and resolve misuse, then deleted or anonymized |
| Legal compliance | Transaction records, accounting records, official requests, legal claims material | Meet tax, bookkeeping, complaint, and legal obligations | Legal obligation, Art. 6(1)(c); legal claims | Current financial year plus 5 years for accounting material where required; otherwise as legally necessary |
5. App Permissions
The app may request permissions depending on the feature used.
Camera:
- Used for damage reports, rental completion photos, support, or feedback.
- Camera use is still-photo only. The app does not record video or audio.
Location:
- Used only while the app is open, to calculate distance to nearby rental boxes/platforms and estimate return/paddle-back time.
- The app uses medium-accuracy GPS on your device and does not send GPS coordinates to the Bloo backend.
- The app does not use background location tracking.
Bluetooth:
- Used to connect to and unlock rental equipment.
- BLE unlock outcomes are processed on your device and are not sent to the Bloo backend.
- Background BLE scanning may occur to assist equipment location and session continuity.
Notifications:
- Used for service messages such as booking reminders, return reminders, safety notices, payment notices, and account notices.
- Marketing notifications require separate consent.
6. Payments And Stripe
Payments are handled through Stripe. Bloo stores limited payment metadata such as transaction IDs, payment status, refund status, and references needed to manage bookings, accounting, refunds, chargebacks, and support.
Bloo does not store full card numbers.
Stripe has a dual role in the payment flow:
- Processor role: Stripe processes payments on Bloo's behalf under a Data Processing Agreement (DPA).
- Independent controller role: Stripe independently manages fraud prevention, payment authentication, dispute resolution, compliance checks, and payout scheduling to Bloo's bank account.
As an independent controller, Stripe may hold or delay funds for fraud-prevention review and may adjust refund amounts based on fraud assessments. See Stripe's privacy policy at https://stripe.com/privacy and its dispute policy at https://stripe.com/docs/disputes.
7. Gift Cards
Bloo may issue gift cards as promotional vouchers/discount codes redeemable for equipment rental services.
Legal structure: Gift cards are discount vouchers (not stored-value or prepaid instruments), redeemable only for Bloo services, non-transferable, expiring 3 years from the issue date. Unused balance may be refunded in cash upon written request to support@blooshare.dk.
Data processing: Bloo processes buyer details, gift-card codes, redemption history, and payment records to deliver and support gift cards. Voucher logs and redemption records are retained 5 years per accounting requirements (Bogføringsloven) and applicable dispute-resolution periods.
VAT: When a gift card is redeemed, VAT is calculated on the final service price after the voucher discount is applied.
8. Feedback And Screenshots
If you submit in-app feedback, Bloo may receive your message, technical app context, route/screen information, locale tag, timezone offset, and platform information.
Screenshots are submitted only after a clear action by you. A screenshot may show personal data visible on your screen. Please do not submit screenshots or messages containing sensitive information unless necessary for the support case.
Feedback screenshots are stored in Firebase Storage with authenticated, size-limited access and are readable only by authorized Bloo staff or approved support/admin systems.
9. Analytics
Bloo uses Firebase Analytics to understand app use and improve reliability.
- Analytics runs on a consent basis (GDPR Art. 6(1)(a)) and does not run until you actively consent in the app. You can withdraw consent at any time in app settings or by contacting support.
- Analytics may send automatic
screen_viewevents and some manual events that includebooking_id, which can be linked to booking records. These events are treated as personal or pseudonymous data. - The integration is basic measurement only. Google Signals is not enabled, User-ID is not implemented, and advertising features are not configured.
- Analytics data is retained for 14 months.
The Bloo Share app does not use any advertising SDK and does not track you across other companies' apps or websites.
10. Marketing
Bloo sends marketing only where the required consent has been collected. Marketing may include offers, campaigns, promotions, or other non-service messages.
Service messages are not marketing. Service messages may include booking confirmations, return reminders, payment notices, safety notices, support messages, account notices, and operational information.
You may withdraw marketing consent at any time using the unsubscribe link in any marketing email you receive from Bloo.
11. Website Cookies
The Bloo Share website may use strictly necessary cookies to make the website work. Analytics, marketing, or other non-necessary cookies are not set until consent has been given through a cookie consent mechanism, and you can reject non-necessary cookies and later change your choice. Mobile-app analytics (Firebase Analytics, §9) is separate from website cookies.
12. Sharing And Service Providers
Bloo uses the following service providers to operate the service.
| Provider | Role | Purpose | Data categories |
|---|---|---|---|
| Firebase / Google Cloud | Processor | Authentication, Firestore, Storage, hosting/functions, first-party logs, feedback, screenshots, app infrastructure | Account data, bookings, photos, app_errors, dev_feedback, screenshots, device identifiers, logs |
| Firebase Cloud Messaging / APNs | Processor / platform provider | Push notifications | Device tokens, notification metadata |
| Firebase Analytics | Processor (consent basis, Art. 6(1)(a)); does not run until you consent | App analytics | Screen views, app activity, event parameters, device/app metadata, booking references where used |
| Firebase Crashlytics | Processor | Crash diagnostics and app-stability monitoring | Crash reports, stack traces, ANR data, app/device state, installation/crash IDs |
| Stripe | Processor (payment execution) and independent controller (fraud detection, dispute resolution, payout management) | Payments, refunds, chargebacks, fraud checks, 3D Secure authentication, disputes, payouts | Payment metadata, payment references, card/payment details handled by Stripe |
| Resend | Processor | Transactional email delivery (booking confirmations, gift-card delivery) | Email address, message content |
| Google Maps | Provider | Maps, rental-location display, proximity features | Map interaction data |
Bloo does not share personal data with third parties for their own marketing unless you have consented or the law allows it.
13. International Transfers
Some providers may process or access personal data outside the EEA, including in the United States. Where this happens, Bloo relies on applicable safeguards such as adequacy decisions, the EU–US Data Privacy Framework where available, Standard Contractual Clauses, data-processing terms, and appropriate technical and organizational measures.
You may contact Bloo for more information about the safeguards relevant to your data.
14. Retention
Bloo keeps personal data only as long as needed for the purposes described in this policy or as required by law.
| Data category | Retention |
|---|---|
| Account data | Until account deletion plus the 30-day deletion processing period, unless retained for legal/accounting/dispute/safety reasons |
| Booking history | Account lifetime, then anonymized or retained only as needed for accounting, disputes, safety, or legal obligations |
| Accounting/payment records | Current financial year plus 5 years where required |
| Damage/loss/theft photos | Until case resolved plus legal/dispute period |
app_errors logs |
90 days unless needed for active support, security, or legal issue |
dev_feedback and screenshots |
180 days unless needed for active support, security, or legal issue |
fcm_tokens/{installationId} |
Deleted on account deletion and token rotation/refresh |
| Marketing consent records | Until withdrawn plus compliance evidence period |
| Terms acceptance records | Account/booking lifetime plus dispute/legal period |
| Firebase Analytics | 14 months |
| Firebase Crashlytics | 90 days (platform default) |
| Support emails/messages | 24 months after last contact unless an active dispute or legal obligation applies |
| Gift-card records | Voucher logs and redemption records retained 5 years from end of financial year (Bogføringsloven §10) |
15. Security
Bloo uses technical and organizational measures to protect personal data, including encrypted transport (HTTPS/TLS), Firebase Authentication and Storage access rules that restrict data to its owner and authorized staff, restricted admin access, and regular review. Feedback screenshots and damage photos are stored in non-public, authenticated-access storage paths, and Google Maps API keys are restricted.
16. Minors
You must be at least 18 years old to create an account, make a booking, pay for a rental, buy a gift card, or enter into a rental agreement.
Participants must be at least 12 years old. The booking holder (who must be 18 or over) is responsible for the supervision and conduct of all participants under 18. Bloo processes only the adult booking holder's data and does not knowingly collect account or booking data from children.
17. Automated Decisions
Bloo does not make decisions based solely on automated processing that produce legal effects or similarly significant effects. App-wide safety/availability controls and eligibility checks (such as "Start Now" eligibility) may affect whether a feature is available, but they are not automated decisions about you.
18. Your Rights
Subject to GDPR and applicable law, you may have the right to:
- access your personal data;
- correct inaccurate data;
- request deletion;
- restrict processing;
- object to processing based on legitimate interests;
- receive data portability where applicable;
- withdraw consent where processing is based on consent;
- complain to a supervisory authority.
To exercise your rights, contact support@blooshare.dk with the subject "Privacy request". Bloo may ask for information needed to verify your identity and normally responds within one month. Some rights depend on the legal basis and circumstances; deletion does not override legal/accounting obligations, safety obligations, fraud prevention, or valid legal claims.
19. Account Deletion
You may delete your account in the app or by contacting support.
In-app deletion path: open the navigation drawer and tap Delete account, then confirm in the dialog.
Email deletion path:
- Send an email to support@blooshare.dk.
- Use the subject "Delete my Bloo Share account".
- Include the phone number or account identifier used for the account.
- Bloo may verify your identity before deleting the account.
Account data is deleted or anonymized within 30 days after confirmation, unless Bloo must retain specific records for accounting, legal claims, fraud prevention, safety incidents, dispute handling, or other legal obligations. Deletion covers the Firebase Auth user, the Firestore user document, booking links where deletion/anonymization is possible, damage photos where no legal/dispute reason remains, app_errors and dev_feedback linked to the user, feedback screenshots, and push tokens.
20. Complaints
You can contact Bloo first at support@blooshare.dk.
You may also complain to Datatilsynet, the Danish Data Protection Agency, at https://www.datatilsynet.dk/.
21. Changes
Bloo may update this Privacy Policy from time to time. Material changes will be notified through the app, website, email, or another appropriate channel where required. The effective date and version at the top of this policy show which version applies.
22. Contact
Questions about this Privacy Policy or privacy requests can be sent to:
Bloo ApS Email: support@blooshare.dk Address: Enghavevej 29, 4. th, 1674 København V, Denmark
23. App Store Privacy Disclosures
The Bloo Share app is distributed through the Apple App Store and Google Play. Both stores require Bloo to declare what data the app collects and how it is used. Those declarations are based on the same data practices described in §4 of this policy. The app does not use data to track you across other companies' apps or websites, integrates no advertising SDK, and shares no data with data brokers. If you have questions about what data the app collects or how to exercise your rights, contact support@blooshare.dk.