HelloWorkr
Back to homeGet the app ↗

HELLOWORKR · LEGAL

Privacy Policy

How we use and protect information across HelloWorkr.

On this page ⌄
  1. 1. What this notice covers
  2. 2. Accounts and professional profiles
  3. 3. Location, check-ins and presence
  4. 4. Connections, messages, events and member activities
  5. 5. Notifications and subscriptions
  6. 6. Technical information and website technologies
  7. 7. Purposes and legal bases
  8. 8. Recipients and international processing
  9. 9. Retention and account deletion
  10. 10. Security
  11. 11. Your rights and choices
  12. 12. Children, external services and changes

Proposed version date: 13 October 2026. This revision has not been published and does not replace the privacy notice currently available on helloworkr.com.

Data controller: Fourtyfour Technologies ApS (HelloWorkr), CVR 42578746, Denmark.
Privacy contact: [email protected] · +45 31 31 56 41.

1. What this notice covers

This notice covers the HelloWorkr mobile app, our website and support. It explains the information used for accounts, professional networking, workspace discovery, check-ins, events, member activities and subscriptions. A privacy notice informs you about processing; reading it or accepting our terms does not give blanket consent to other uses of your information.

2. Accounts and professional profiles

We process your name, email, account ID, authentication credentials and session records to create your account, sign you in and handle account recovery. Our authentication provider is Supabase. Credentials are not member profile fields.

Your profile can include an avatar, professional title, biography, industry, skills, interests, LinkedIn or website links, and what you are looking for professionally. You choose the optional information you add and can edit it in the app. We also keep membership tier, account status and administrator or ambassador status.

Members can see profile information in networking, connections, spaces and events. The app presents different detail depending on the feature, membership tier and connection status. Your name, avatar, professional title, participation and presence can be shared with other members; optional professional fields should be treated as information you are sharing with the community. Do not add confidential information to your profile. Public discovery pages for visitors show spaces, events and activity teasers, rather than personal member feeds.

3. Location, check-ins and presence

With device location permission, HelloWorkr uses precise latitude and longitude, accuracy and update times to find nearby spaces and members and to automatically check you in and out. Your latest precise coordinates are sent to and stored on our Supabase backend. Displaying an approximate distance does not mean that the backend only receives approximate location.

Location updates start when you enter the signed-in app with permission. The app pauses its location stream and presence heartbeat when it is backgrounded, and resumes them after checking permission when you return. Signing out stops tracking. A paused app can still have a stored latest location and an active check-in; backgrounding does not immediately check you out. An update already in progress may finish during a lifecycle change. The current app does not provide continuous background journey tracking or a separate switch for automatic check-in.

We keep the space ID, check-in and check-out times and your chosen Open To intentions, such as coffee, coworking, networking or do-not-disturb. A latest-location record is updated rather than used as a full GPS journey log, but check-in history can reveal visits over time.

Nearby cards display approximate distance. Other members may see your name, avatar, professional title, online status, current space and Open To intentions. The detail presented depends on the feature, subscription and connection relationship. Event and activity organizers receive participation information needed for their event. Administrators can access records for service operation and support. Do-not-disturb describes your availability; it does not stop location processing or hide every community record.

Online status is refreshed while the app is active. It may remain visible briefly after you leave; a scheduled server task marks accounts offline after more than ten minutes without a refresh. Check-ins have their own lifecycle and are separate from online status.

You can refuse or revoke location permission in your device settings. This affects nearby discovery and automatic check-in; location-independent browsing remains available. Revoking permission stops new location access, but does not erase an already stored location or historical check-ins. Contact us to request erasure. Device permission is for these location functions and is not permission for unrelated advertising or other use of your location.

4. Connections, messages, events and member activities

We store favorites, connection requests and decisions, event registrations and participation, activity submissions, joining and leaving records, replies and notification read status. Member activities include their title, description, image, venue, times and author. Activities are reviewed by administrators before publication.

Private chat records include message content, sender and recipient IDs, timestamps and read status. Chats are stored on the backend and delivered to the conversation participants. They are not end-to-end encrypted. A recipient can keep or share a copy. Authorized service personnel may need access for support, abuse investigations or legal requests.

Activity audiences depend on membership and participation. Organizers and eligible members can see participant or author information and replies; some members receive counts or redacted teasers. Replies are not private one-to-one messages. Blocking affects interaction and discovery but cannot retrieve copies someone already received.

When you report a member, activity or reply, we store your account ID, the subject, reason, timestamps and review outcome. A reply report can retain a snapshot after the original reply is removed. Moderation records may include decisions, reasons, administrator notes and activity-creation restrictions. These records support abuse prevention and review; they are available to administrators rather than posted as community content.

5. Notifications and subscriptions

The app stores an in-app notification inbox. If you allow push notifications, it registers a device messaging token with your account. Google Firebase Cloud Messaging and, on iOS, Apple Push Notification service handle delivery. Push messages can include an activity title, notification type and activity or notification identifiers. Notification previews may appear on your lock screen. You can change operating-system notification permission and the available in-app notification preferences. Delivery depends on your device and service availability.

Apple App Store or Google Play handles payment for native Premium subscriptions. We receive and verify store platform, product, transaction reference or purchase token, the account association, subscription status, purchase period and renewal information. These records establish membership access and help with restores, cancellations and disputes. Native subscriptions do not send your full payment-card number or card security code to HelloWorkr.

The website's payment notice names Quickpay, Nets and Clearhaus for website payments. Consult the notice shown at a website checkout for that payment's processing details. Account deletion in HelloWorkr does not cancel an Apple or Google subscription; manage it with the relevant store.

6. Technical information and website technologies

Infrastructure providers process network and request information, such as IP addresses and request times, to deliver and protect the service. The mobile app uses Sentry for crash reports and sampled performance diagnostics, including app and device information, errors, stack traces and operational breadcrumbs. Talker provides application logs, and selected errors and breadcrumbs are sent to Sentry. The app disables Sentry's default personal-information collection and filters selected fields; diagnostics can still contain information included in an error or its context.

The current website uses WordPress and WooCommerce. It includes Cookiebot for cookie choices, Google Tag Manager and configured Meta/Facebook pixel tracking through PixelYourSite; the published website notice also identifies Google Analytics. Depending on your choices and the website feature, these technologies can process device/browser identifiers, page visits and interactions for statistics or marketing. Use the website's cookie controls to review the technologies and change your choices. Browser settings also allow you to remove cookies. Necessary session, security, payment and consent-preference technologies serve website operation; optional statistics and marketing require a separate choice.

The mobile app's processing described here supports service operation. It does not add a separate advertising, session-replay or optional click-analytics collection service. This notice does not authorize sale of private chats or individual location histories, or their use to train general-purpose AI models.

7. Purposes and legal bases

  • Providing requested services: accounts, profiles, networking, messages, discovery, location-based check-in, events, activity participation and membership verification support the service you use (GDPR Article 6(1)(b)).
  • Operating a reliable and safe community: proportionate security, abuse review, diagnostics and service reporting serve our legitimate interests in protecting members and keeping HelloWorkr reliable (Article 6(1)(f)). You may object to processing on this basis.
  • Legal obligations: records required for accounting, lawful requests and handling data-protection rights are processed under Article 6(1)(c).
  • Optional website statistics, marketing technologies and consent-based communications: these rely on your separate consent (Article 6(1)(a)) where required. You may withdraw it without affecting earlier lawful processing.

Core account and transaction information is required for the related service; without it we cannot provide that account or verify a subscription. Optional professional fields and device permissions are your choice. Membership eligibility and nearby ordering use automated rules; member-activity moderation is reviewed by administrators.

8. Recipients and international processing

Recipients include the members and organizers described above; HelloWorkr administrators and support personnel; Supabase for authentication, database, file storage and realtime services; Sentry for diagnostics; Google Firebase and Apple for push; and Apple or Google for native purchases. The website uses the providers identified in Section 6 and the payment providers identified in Section 5. Providers may have their own responsibilities when operating their services, including app-store payments. We may disclose relevant records to authorities or advisers when a legal obligation or a specific legal claim requires it.

Provider operations can involve processing outside the European Economic Area, including the United States. The app sends Sentry events to its German ingestion endpoint; that does not mean all provider operations are confined to Germany. Contact [email protected] for the recipient, destination and transfer-mechanism information applicable to your data and for copies of relevant safeguards. Provider privacy information is available from Supabase, Sentry, Firebase, Apple and Google.

9. Retention and account deletion

Your latest location remains stored until replaced or removed; revoking permission does not remove the existing record. Check-in history is separate. The app ignores old coordinates in some discovery flows, but that freshness check does not delete them.

Activity replies are scheduled for deletion after 48 hours from the activity's end, by an hourly cleanup task. Reports can retain a snapshot separately. In-app notifications older than 90 days and completed, failed or invalid push-delivery records older than seven days are removed by a daily cleanup task. Cleanup is scheduled rather than instantaneous.

Delete account in the app marks your profile deleted, prevents further sign-in, ends sessions, marks you offline and removes your latest location, active check-ins and registered push tokens. It cancels your pending or approved future activities, removes your future activity participation and marks your replies deleted.

This is not immediate erasure of every record. Profile and authentication records, historical check-ins and participation, private messages, reports and moderation history, subscription records and some uploaded files may remain. We do not publish a fixed automatic erasure period for those categories. Retention depends on whether information is needed for an active account or subscription, an unresolved support or abuse case, an applicable accounting obligation or a specific legal claim. Contact us for an erasure request and details of the reason and period applicable to retained records. Other members and independent providers can retain their own copies under their responsibilities.

10. Security

We use authenticated access, database access rules and store verification for relevant service functions. Data travels through HTTPS connections. Access controls reduce risk but cannot guarantee absolute security. Please protect your account and avoid putting sensitive personal information in profile fields, messages or reports unless it is necessary to your request.

11. Your rights and choices

Depending on the processing, you may request access, correction, erasure, restriction and a portable copy of data. You may object to legitimate-interest processing and to direct marketing, and withdraw consent. These rights have legal conditions; we will explain any restriction.

Email [email protected]. We may need proportionate identity verification. We normally respond within one month; if a lawful extension is needed, we will explain it within that month. You can complain to Datatilsynet, the Danish Data Protection Agency, or the competent authority where you live or work. Contacting us first is optional.

12. Children, external services and changes

HelloWorkr is intended for adults aged 18 or over. If you believe a child has supplied information, contact us. External websites, venues and app stores have their own privacy notices for their services.

We will date material revisions and provide any additional notice or choice required for changed processing. Continued use is not consent to a new optional purpose. Previous notices are retained as records of what was disclosed.

HelloWorkr
HomePrivacy policyTerms of serviceContact
© 2026 HelloWorkr · Fourtyfour Technologies ApS