LoudMeet Privacy Policy

How Alexandr Korsak (Bitscorp) collects, uses, and stores data in the LoudMeet mobile app (co.bitscorp.loudmeet).
Privacy Policy
Effective date: 14 November 2026. I take your privacy seriously. This notice explains what LoudMeet stores on your device, what (if anything) leaves the device, and how to contact me.
Alexandr Korsak (Bitscorp), a self-employed professional (autónomo) in Spain, operates the mobile application LoudMeet (co.bitscorp.loudmeet). Bitscorp is a trading name, not a registered company. This page applies to LoudMeet on iOS and Android. The website https://bitscorp.co has a separate Privacy Policy and Terms and Conditions.
The app
LoudMeet turns calendar meetings on your device into escalating alarms so a quiet notification is harder to miss. You pick which calendars to watch. The app can add a leave-now ping for in-person meetings and show a prep card when the alarm fires.
Data stored on your device
  • Your alarm preferences, selected calendars, and related settings on this device.
  • Calendar events are read locally to schedule alarms. Event details are not uploaded to Bitscorp.
  • Local notifications and exact alarms. Remote push notifications are not used.
Data that leaves your device
  • Calendar data is not sent to a Bitscorp server. There is no LoudMeet backend.
  • If you send feedback, your email app may include basic device and app version details in a message to alex@bitscorp.co.
  • Purchase and subscription status are handled by Apple or Google and RevenueCat, as described below.
Permissions
  • Calendar: read so the app can fire alarms before meetings you have chosen to watch.
  • Reminders (iOS, some versions): the system calendar permission may also request reminders access. LoudMeet does not need a reminders list for its own features.
  • Notifications and exact alarms (optional): used to deliver the nudge, warning, and full alarm on this device.
You can change or withdraw permissions in the operating system settings.
Sensitive information
Calendar events can include meeting titles, times, locations, and attendees. LoudMeet reads them on the device and does not upload them to us.
Analytics and crash reporting
LoudMeet does not include a third-party analytics or crash-reporting SDK. I do not run Mixpanel, Google Analytics, Firebase, Sentry, or a similar product inside this app. The stores and RevenueCat may keep their own purchase or install records under their policies.
Third parties
I only involve the parties below for the purposes stated. Each has its own privacy policy.
  • RevenueCat: To check and restore your Pro entitlement. RevenueCat receives purchase tokens, subscription status, and an anonymous app user identifier. It does not receive the journal, photos, files, or other content you keep in the app.
  • Apple: If you buy or manage a subscription or a lifetime purchase on the App Store, Apple processes the payment. We do not receive your full payment card number.
  • Google: If you buy or manage a subscription or a lifetime purchase on Google Play, Google processes the payment. We do not receive your full payment number.
Accounts, servers, and retention
No Bitscorp server. Calendar access, notifications, and settings stay on the device.
LoudMeet does not require a Bitscorp account. Information stored only on your device remains there until you delete it in the app or uninstall the app. Purchase records are kept by Apple or Google and by RevenueCat for as long as they need them to provide the subscription. If you email me, I keep the message long enough to respond and then delete it when it is no longer needed.
Your rights
Because most LoudMeet content never leaves your device, the practical way to access or delete it is in the app, or by uninstalling the app (which removes local data). For any personal data I hold in email, or questions about purchase records, write to alex@bitscorp.co. If you live in the European Economic Area, the United Kingdom, or another region with similar rights, you may also request access, correction, deletion, or a restriction of processing of personal data I hold, and you may lodge a complaint with your local supervisory authority. In Spain that authority is the Agencia Española de Protección de Datos (AEPD).
International processing
I am based in Spain. Apple, Google, and RevenueCat may process purchase data in other countries. Their policies describe those transfers.
Changes to this policy
This Privacy Policy is effective as of 14 November 2026. I may update it from time to time. The current version will always be at https://bitscorp.co/loudmeet/privacy. Material changes will be reflected on this page, and I may also note them in the app.
Contact
Questions about this policy or about LoudMeet: alex@bitscorp.co. There is no telephone contact number. Related pages: LoudMeet Terms and Conditions, and the list of Bitscorp app policies.