Privacy Policy

Scope and responsibility

This policy covers the AlmiraLink public website, customer account and customer app, connected Windows bridges and phone companions when they communicate with the central service. It explains our handling of personal information. A mobile carrier, device owner, app store or payment provider may also process information under its own policies. A bridge operator is responsible for lawful authority over the devices and information it connects.

Account and service information

We collect the name, email address and password supplied during account registration. Passwords are stored as hashes rather than as readable passwords. Authentication tokens, account roles, plan records, permissions and administrative actions support account security and service operation.

Connected bridges report unit identifiers, device labels, phone identifiers, availability, state and health information. Service records can include the selected phone, assignment, caller or recipient number, call direction, start and end times, session state and command delivery status. Your computer label and each connected phone are separate service identifiers.

Calls, microphone access and audio

Calling requires microphone permission and a functioning internet connection. Audio is relayed to support a live call; the central service does not provide a library of replayable call recordings. The relay uses short-lived audio packets with expiry and cleanup on delivery or call termination. This is not a promise that no temporary packet can ever exist in infrastructure storage or diagnostics.

Call traffic also passes through the connected phone and its carrier. We do not represent this route as end-to-end encrypted against every participant or as anonymous calling. A device owner, carrier or lawful authority may have access under its own responsibilities. Do not use the service for information that requires safeguards beyond those confirmed for your account.

SMS and phone history

Sending a message processes the destination, message body, selected phone, timestamps and delivery status through the service and connected device. A queued or dispatched message is not proof of recipient delivery. The carrier and recipient can retain their own copies.

Retrieving phone SMS and call-history copies depends on device approvals and the bridge operator enabling the relevant sharing option. These permissions are distinct from ordinary account registration. Customers see records through their authorized assignment and feature permissions; authorized administrators may access service records for operation, support and security. Revoking access stops future authorized access, but does not automatically erase stored records or copies on phones.

Payments, referrals and support

IdeaLaunchkit.com collects payments on behalf of AlmiraLink, using Stripe-hosted checkout and subscription management. Payment information necessary to collect, reconcile and support the transaction is handled through this payment arrangement. We receive payment references, customer and subscription identifiers, invoice amounts, currency, payment status, renewal information and billing-event details needed to match payment to the signed-in account. We do not store raw card numbers or card security codes in our application database. Stripe processes billing information under its own privacy notice.

Referral information includes referral codes, signup attribution, verified sales, reward calculations, approval and payout status, and payout details you submit. Referrers receive masked account identifiers and conversion status rather than another customer’s full contact or card information. Support enquiries contain the contact details and message you choose to submit, ticket status and administrator replies or notes.

Why information is used

We use information to register and authenticate customers; connect authorized phones; route permitted calls and messages; show account activity; confirm payments; maintain subscriptions; assess referral conversions; respond to support; investigate misuse; and preserve records required for business, dispute and legal purposes. We do not use access to one phone as permission to expose another customer’s personally assigned phone.

Where consent is required, it must relate to the described purpose. Device, microphone and optional sharing approvals can be withdrawn through device settings or by contacting support. Essential processing may remain necessary to supply an active service or comply with law. Withdrawing a device permission can stop the affected feature. This policy does not obtain blanket permission for advertising or unrelated use.

Service providers and international processing

The website is hosted through Bolt and the central backend uses ChatGPT Sites hosting infrastructure. Stripe provides checkout and subscription management. Internet, telecommunications and connected-device providers carry communications. These providers receive information needed for their respective functions; their own notices explain processing they control independently.

Your use of the service may involve storage, support or transmission outside your province or country, including where our infrastructure providers operate and where the bridge phone is located. Local courts and authorities may have lawful access there. We do not promise Canadian-only or Jamaican-only storage. Where additional transfer safeguards or consent are legally required, they must be addressed before the affected processing; using a remote phone is not itself proof of a lawful international transfer.

Disclosure and confidentiality

Information may be disclosed to the customer and authorized bridge or service administrators within their role, to providers needed for the service, when you direct or consent to a disclosure, and when required or permitted by applicable law. We may preserve relevant information to investigate fraud, protect accounts or respond to a valid legal process. A corporate reorganization may require transfer of relevant records with appropriate protection and notice. We do not publish private phone data as public marketing content.

Retention and deletion

Retention depends on the record and its purpose. Live audio packets are temporary. Account, assignment, call metadata, support, referral and payment records can remain after a call ends or access is revoked. Billing, dispute, fraud and accounting requirements may justify keeping limited records after account closure. There is no universal automatic deletion timer for all customer information.

You may request account closure, deletion or de-identification through Contact. We assess the records involved, applicable obligations and third-party information, and explain any information that must be retained and why. Deleting an app or signing out does not delete your account, cancel a Stripe subscription or erase carrier and recipient copies. Do not assume that a deletion request has completed until we confirm its scope and outcome.

Your choices, requests and complaints

You can request access to information about you, correction of inaccurate records, information about its use or disclosure, and deletion or withdrawal of consent where applicable. Additional rights such as objection, restriction, portability or appeal may apply depending on your location and the law governing the processing. We verify identity proportionately and protect other people’s information when answering a request. We respond within applicable legal time limits and explain a permitted extension or refusal.

Address privacy requests to Altergy Network Solutions Corp. through Contact with the subject “Privacy request”. If the response does not resolve your concern, you may contact the privacy regulator with jurisdiction, including the Office of the Privacy Commissioner of Canada or Jamaica’s Office of the Information Commissioner where applicable. This policy does not restrict those rights.

Security and account protection

We use authentication, permission checks and other safeguards appropriate to operation of the service. No network or device can be promised completely secure. Keep your password and enrollment codes confidential, install supported updates, protect the connected phone and report suspected unauthorized access promptly. We assess security incidents and provide notices where legally required. Support will not ask you to reveal a password or card security code.

Children and information about other people

Accounts and paid service arrangements are intended for people able to enter the relevant agreement, or persons acting with appropriate guardian or organizational authority. Do not connect a device or upload another person’s messages, contacts or history without authority and any required consent. If you believe a child’s information has been submitted without appropriate authorization, contact us so we can assess and address it.

Changes and contact

We update this policy when our handling changes. The publication date identifies the current text. Where required, material new uses or disclosures will receive additional notice or consent rather than being treated as authorized merely because this page changed.

Use the Contact page on this website. Include the email associated with your account, the relevant order, invoice or ticket reference, and a clear description of your request. Never send a password, full payment-card number, card security code, phone unlock code or USB debugging credential.