Who we are and how to contact us
Byldya Software Ltd (Byldya), based in the United Kingdom, is responsible for personal information it handles for its website, support and the services described here. Contact support@byldya.com about privacy, deletion or this policy.
This policy covers Byldya applications, including Jornal, Choir Music, M-AD and Kovadh, and byldya.com. Features differ between apps, platforms and releases. Normal local app use does not require a Byldya.com account. We do not sell personal information.
App-specific information: Jornal, Choir Music, M-AD and Kovadh. Shared sections below cover support, purchases, website use and privacy rights.
Local app information and your files
Our apps can process records, media, documents, preferences and recovery information on your device to carry out the features you choose. Byldya does not receive or host your personal app records merely because you use an app. Information you deliberately send to support, contribute or deliver through an external service is explained separately below.
You control your saves, exports and backups. Files in cloud-synced folders, operating-system backups or sharing services may be transferred by those services. Uninstalling an app does not necessarily remove separately saved files, backups or credentials. Local deletion cannot guarantee forensic erasure from SSDs, snapshots, backups or recipient copies. Byldya cannot remotely inspect or delete records held only on your device.
Jornal
Jornal processes the health, nutrition and personal records you choose to enter or import, including profile details, meals, symptoms, mood, medications, measurements, journal entries, medical documents and appointment-preparation records. It uses these records for logging, calculations, review, reminders and reports. These can be sensitive health records; review reports and exports before sharing them.
The primary diary store is configured for Apple CloudKit sync on supported devices and Apple accounts. Core diary, profile, symptom, medication, recipe and settings records may therefore sync through iCloud where available. Some Personal Medical Workspace records and document-library attachments use a separate protected local store and are outside that shared sync path. App and device settings, Apple service availability, and the feature used determine which copies exist.
Apple Health access is controlled by the permissions you grant for supported reads and writes. Optional camera, photos, microphone, speech recognition, Bluetooth, notifications, calendar and biometric features use the relevant system controls. Biometric templates stay with Apple's authentication system. Calendar export passes the selected appointment details to the device calendar. Siri and Shortcuts operate under Apple's privacy practices and Jornal's action settings.
On supported devices, optional recipe, prepared-meal and journal structuring use Apple's on-device models, and in-app dictation requires supported on-device speech recognition. These flows do not add a cloud-model or cloud-dictation fallback. Saved records may retain reviewed text, excerpts and corrections. Unfinished recipe scans retain source pages and extracted text for later review and may sync with the primary store; source image bytes are cleared after successful recipe approval or explicit discard. A separately chosen display photo and previously exported backups can remain.
Requested barcode, ingredient, medication and reference lookups can send the search terms, barcode and catalog filters needed for the selected provider to return results. The configured Victuals product service can receive reviewed product and nutrition facts and selected packaging images. Its device authentication uses a pseudonymous device identifier, a device-generated public signing key, verified StoreKit information and, where applicable, Apple App Attest proof. Device keys and access or refresh tokens are stored in the device Keychain. These product-service requests do not include private diary, symptom, medication, HealthKit, Medical workspace, report, backup or medical-document records.
Manual product completion sends reviewed facts to Victuals without packaging images. With the photo route and final confirmation, selected product facts and packaging photos go to Victuals and may be contributed to Open Food Facts, where contributions may become public under its licensing. Selected upload images are metadata-stripped and resized. Byldya may retain contributed product information to improve nutrition information; this is separate from hosting personal journal records.
Failed or pending contributions can retain reviewed drafts and selected images locally for retry. Successfully delivered image bytes and completed retry payloads are cleared; a local contribution-status record can remain until full local-data deletion. Local deletion does not retract information already delivered to a provider. Limit submissions to the product and avoid people, addresses, receipts, medical documents or unrelated personal information. Contact support@byldya.com if personal information was submitted accidentally; Open Food Facts copies are also subject to its own policies and controls.
If you enable Victuals update checks, Jornal can request text-only service messages up to three times daily, subject to iOS scheduling, using device authentication. You can disable these checks in Data API settings. They do not transmit your private health records. Local records, exports and backups remain subject to the controls and limits described above.
Choir Music
Choir Music processes scores, annotations, learning tracks, sing lists, local singer or conductor profiles, roster details, rehearsal information and preferences for the features you use. The shared save, export, backup and support provisions apply. Byldya does not host your personal Choir Music library on byldya.com for normal local use.
If you enable iCloud backup or use cloud sharing and live sync, selected library content and shared sing-list data are handled through Apple's iCloud/CloudKit services. A backup or package can include scores, annotations and attached media. Shared sessions can exchange account or participant identifiers, score and list references, page and scroll positions, timing and shareable annotation state. Nearby rehearsal sessions exchange the relevant session information with connected participants. People with access to a shared list or exported package may retain their own copies.
You choose when to create or restore a backup, share a list or package, or start or join a session. Apple account, service and sharing controls apply to cloud copies. Diagnostic support email is user-initiated: review the prepared message and send it only if you want Byldya to receive it. Do not assume that a score, annotation, roster or rehearsal record is free of personal information.
M-AD
M-AD connects to directory services you select to browse, search, administer and report on your organisation's environment. LDAP/LDAPS and Kerberos workflows exchange authentication and directory requests with the selected domain services. Where configured, native Microsoft Entra ID uses Microsoft sign-in and Microsoft Graph under the permissions and tenant consent granted. Directory account details, object attributes, memberships, policies and security information can contain personal or confidential information.
Connection-profile metadata is stored locally, while saved credentials and native sign-in tokens use macOS Keychain. Local security-descriptor backups, audit events, operational reports and diagnostics can contain directory names, identifiers, policy settings and security trustees. Exported connection profiles omit passwords, Keychain identifiers and certificate-bypass state; this does not make the remaining profile or report anonymous.
M-AD does not automatically upload diagnostics to Byldya. Review and redact reports before exporting or attaching them to a support message. Your organisation and directory providers control their own server access, logging and retention. Removing a local profile or report does not erase directory records, server logs or copies already shared.
Kovadh capture, editing and permissions
Kovadh processes content you choose to capture, import or edit, including screenshots, recordings, camera or microphone media, images, documents, clipboard inputs, OCR text, captions and transcripts. Editable projects can retain original media, edit instructions and related metadata for non-destructive editing.
Recognition and analysis are local. Transcription uses supported on-device speech recognition and does not fall back to cloud transcription. Face and person editing tools detect regions; they do not identify people or create facial identity profiles. Automated suggestions can be wrong and need review.
macOS controls permissions for selected features, including Screen Recording, Camera, Microphone, Speech Recognition, Accessibility, Input Monitoring and files or folders. You can review or revoke access in System Settings. Optional shortcut presentation omits ordinary unmodified typing, but can still reveal sensitive activity. Raw key events are not saved as a key log.
Browser capture uses the page you select, visible screenshot segments and bounded capture geometry. It does not collect browsing history, form fields or page text as separate structured data. Visible pixels can nevertheless contain private information.
Kovadh storage, History and Private mode
Saved projects and exports remain where you choose to save them. Local preferences, project references, file-access bookmarks, integration account labels and pending export jobs support the features you use. Temporary, preview and recovery files can contain media while their task or recovery remains active.
Optional History can retain media, thumbnails, dates, titles, favourites and tags. Application labels and searchable OCR are retained only when enabled. History age, count and storage limits can remove non-favourites; favourites require explicit deletion.
Recent Captures is a separate convenience gallery listing up to 21 screenshots, subject to its memory limits. This gallery limit is not a total file-retention limit: image files already created in the Recent Captures folder can remain after older items leave its index. Removing a recent item does not remove a separate History item, project or export.
Private mode prevents History, OCR-index and recent-item bookkeeping. It still allows saves or exports you explicitly request. Excluded applications are omitted from the corresponding retention paths.
History asset encryption is optional and off by default. New encrypted recording History items retain finalized media for verified temporary playback, rather than an editable multi-track recording archive. With asset encryption off, a retained recording package can remain editable. OCR-index encryption is separate. Keys and integration credentials use macOS Keychain. These controls do not encrypt every ordinary project, export, temporary file, backup or screenshot stream.
Organisation-managed restrictions can limit destinations, require Safe Share or metadata stripping, disable selected features and control retention. Settings show effective restrictions. They do not remove copies already held by another application or service.
Kovadh sharing and external services
Kovadh does not automatically upload captures or projects to Byldya. Delivery uses a destination you explicitly select and review. Connecting an integration, discovering destinations or refreshing authentication can contact the provider before file delivery. Providers receive the authentication information, reviewed file and fields needed for the action.
The planned App Store v1 integration routes are Slack and Microsoft Teams, with verified flattened still images and silent MP4/H.264 recordings up to the 512 MiB Kovadh adapter limit. Recording Safe Share omits audio, captions, source metadata and editable project data. Provider and tenant limits can be stricter. This route does not imply support for every recording or sharing combination.
Clipboard, printing, Open In and macOS sharing pass information to the system or receiving app. Universal Clipboard and cloud-synced storage may transfer it under your settings. Direct evaluation builds can also run explicitly enabled folder or script automation until stopped; receiving scripts and apps operate under their own controls.
External providers and their workspace, tenant or site administrators control their own access, retention, backups and further use. Disconnecting locally deactivates the account and attempts credential removal; failed Keychain cleanup can retain non-secret retry references. Disconnect does not necessarily revoke provider authorization or delete past deliveries. A request already admitted by a provider may finish.
Kovadh redaction and sensitive content
Editable projects may contain original, unredacted media. Blur, pixelation and ordinary covers are cosmetic concealment. Secure Redact removes covered content from a materialized export, rather than from the original project. Review the selected range, audio, captions, metadata and resulting file before sharing. Detection tools cannot guarantee that every sensitive detail is found. Unsupported or unauditable secure-output combinations are refused.
Purchases and diagnostics
Apple handles App Store payment and account information under Apple’s privacy policy. Apps that offer purchases use verified purchase information for feature access. Kovadh does not send payment-card details or transaction payloads to a Byldya billing server.
Kovadh has no advertising or cross-app tracking SDK and no automatic analytics or crash-upload service. Its operational diagnostics use content-free statuses, counts and error categories, rather than captured media, OCR or transcript text, source paths or credentials. Apple and the operating system can handle diagnostics under your device settings. An attachment you deliberately send to support is separate from automatic diagnostics. These Kovadh-specific statements do not assert identical diagnostic behaviour for every other app.
Support messages and retention
If you email support@byldya.com, we receive your address, message and attachments you choose. We use them to answer the request, investigate the reported problem, secure our services and handle related disputes. Our ordinary lawful basis is our legitimate interest in providing and maintaining support; contractual or legal obligations can apply where relevant. Support is optional for normal local app use. Avoid sending passwords, tokens or unnecessary sensitive media.
IONOS provides our email service. Access to support correspondence is limited to people and service providers who need it for those purposes.
Our retention schedule is 12 months after the last substantive contact for routine support correspondence. Unneeded attachments, including copies within email messages, are deleted within 30 days after the issue is resolved. We can keep an attachment-free case summary for the remainder of the correspondence period.
If particular information is still needed for an active case, a security investigation, a legal requirement or the establishment, exercise or defence of a legal claim, we retain only what is necessary for that reason and review it when the reason ends. Deletion applies to live copies; provider backup copies expire through the applicable backup lifecycle and are not retained for ordinary reuse. Local app records have their separate user-controlled retention settings.
Website, cookies and hosting
IONOS hosts byldya.com. Visiting the website is separate from using an app locally. Hosting and security systems can process connection information such as IP/network details, request time, requested page or file, referrer, browser, operating system and device type to deliver the site and investigate errors or abuse. Our lawful basis is our legitimate interest in operating a secure and reliable website.
Byldya does not use tracking cookies. The site uses first-party browser storage to remember your colour theme; clearing site storage resets that preference. The public site currently displays English and clears any legacy language preference. Absence of tracking cookies does not mean that the hosting server receives no connection information.
IONOS standard Web Hosting documentation describes visitor logs retained for eight weeks and IP-address anonymisation. Security or proxy records can involve additional network information; the exact provider product and configuration govern those records. We do not promise that every network record is anonymous. Necessary incident extracts follow the documented-need exception above rather than being kept indefinitely.
IONOS may provide cookie-free service statistics under the hosting product. We do not use tracking cookies to follow visitors across sites. External links open services under their own policies and do not automatically attach app content.
Providers and international handling
Our hosting, email, security and backup providers process information needed to provide those services. IONOS service terms and data-processing information describe its relevant infrastructure and subprocessors. A UK business address does not imply that all service processing is physically within the UK.
Where a restricted international transfer is involved, the applicable arrangements must provide the protection required by UK data-protection law, such as an applicable adequacy decision or approved contractual safeguards. Contact support@byldya.com for information about arrangements applying to a specific service. Information you choose to send to Apple, Slack, Microsoft, Victuals, Open Food Facts, your selected directory service or another recipient is also subject to that recipient’s processing locations and policies.
Children and your privacy rights
Consult each app’s App Store age rating and feature guidance; an age rating is not a guarantee that users will never handle sensitive or children’s information. Parents or guardians can contact support if a child has sent personal information to Byldya. We investigate and minimise or delete information that is not needed, subject to applicable obligations.
For information held by Byldya, you can request access, correction, deletion, restriction or portability where the relevant right applies. You may object to processing based on legitimate interests. Where consent is the basis, you may withdraw it without affecting earlier lawful processing. These rights have conditions and exceptions; we may need proportionate information to verify a request.
We cannot remotely access records held only on your device. Use the app, file, backup and recipient controls for those copies. Requests to Byldya should go to support@byldya.com. You may complain to the UK Information Commissioner’s Office at https://ico.org.uk/make-a-complaint/ or another competent supervisory authority.
Updates and contact
We update this policy when relevant practices change and show the date of the new version. A policy update does not itself authorise a new upload or replace a required feature-level choice.
Privacy and support: support@byldya.com. Website: https://byldya.com/. Full policy: https://byldya.com/privacy.html.