Who this policy covers
This policy explains how MirsalGo, the operator of the MirsalGo service, handles information through this website, our support and demo services, and the MirsalGo communication service we operate. Contact us at support@mirsalgo.com.
If your organisation provides your account or operates its own deployment, it also determines how that account is administered, who you can contact and the applicable retention settings. Ask your administrator about those arrangements. This policy does not replace your organisation's own privacy notice.
Information we process
- Account information: username, display name, account permissions, contacts and group memberships. Passwords are stored as derived password hashes, rather than plain text.
- Device and session information: device identifiers, public encryption keys, general platform, app version, authentication records and notification tokens where push notifications are enabled.
- Communication information: sender and recipient identifiers, group membership, message timing, delivery and read indicators, attachment sizes, and information needed to establish and route calls.
- Encrypted content: encrypted message payloads and encrypted attachments that the service stores or relays for delivery. Local app storage may retain encrypted history and information needed for secure messaging.
- Website and support information: server access logs; the name, email, request text and optional organisation details you submit; and demo scheduling preferences if you provide them.
Security records may include the source IP address of a sign-in. The website hosting provider may also record IP addresses, timestamps, request paths and browser information in access and error logs.
What encryption protects
Supported app messaging encrypts message content and attachments on the participants' devices. The messaging server stores or routes that content in encrypted form and is not given the keys needed to read it. Supported server-mode voice calls use encrypted media.
Encryption does not conceal account relationships, routing data, timestamps or all other metadata. Administrative service announcements and support requests are not end-to-end encrypted conversations. Older deployments or experimental connection modes may behave differently; use the current supported app and your administrator's approved connection settings.
A recipient can copy or save content. Encryption cannot protect an unlocked or compromised device, and we do not promise that any service is immune to every attack.
How information is used
We use information to provide accounts, deliver messages and calls, enforce access permissions, protect the service, diagnose technical problems, answer support requests and arrange requested demonstrations. We do not use the information collected by this website for behavioural advertising, and we do not sell personal information.
App permissions and notifications
Depending on your device and the features you use, the app may request microphone permission for calls or voice messages, notification permission for incoming activity, and access to selected photos or files when you choose an attachment. You can manage permissions in your device settings. Disabling a permission may prevent the related feature from working.
Where configured, Apple Push Notification service or Google Firebase Cloud Messaging handles notification delivery. These providers process device tokens and technical delivery information under their own policies. Availability depends on the deployment and device settings; this is not a promise that notifications work in every background state.
How long information is kept
Message retention is set by the communication server administrator, with supported periods up to 30 days. The current managed development server uses a one-day setting. A retention setting is not a guarantee that a recipient's exported files or independent copies disappear.
Account, permission and device records are kept while needed to provide and protect the account. Current communication-server security policy limits security events to seven days, with sign-in IP addresses hidden from normal reads after 48 hours and removed by scheduled cleanup. Separate hosting logs and backups have their own operational retention.
Website support and demo requests are kept for up to 180 days while open, or up to 90 days after being marked closed, unless a legal obligation requires otherwise. Expired records are removed during request processing and administrative maintenance. Email copies follow the email provider's and support team's retention practices.
Your choices and requests
You can ask for access to, correction of or deletion of information associated with your account, or raise a privacy concern, by emailing support@mirsalgo.com or using our account deletion page. Available rights depend on applicable law and your organisation's role.
We may need to verify that you control the account before acting. Never send us your password, recovery keys or private conversation contents. An administrator may need to carry out account changes for an organisation-managed deployment.
Signing out is different from deleting an account. Deletion does not remove copies independently saved by other people or information we must retain for a legal obligation.
Cookies and website forms
The public pages load fonts, images and scripts from this website. We do not add advertising pixels or third-party analytics scripts. The support and demo forms use a short-lived essential security cookie to protect submissions; it expires after two hours. The private team request area uses authentication for authorised staff.
Form submissions are saved in a restricted request store on the website server. They are not encrypted end to end; authorised support staff can read them. A short-lived keyed representation of the submitting IP address is used to limit abuse, rather than storing the raw IP in that request store. Web-server logs are separate.
Children and policy changes
MirsalGo is intended for work and organisation-managed communication, not for children under 13. If you believe a child has provided personal information, contact us so we can investigate and take appropriate action.
We may update this policy as the service changes. The date at the top identifies the current version. Material changes will be communicated through appropriate service or account channels.