Alliedly Privacy Policy

Alliedly is a Canadian platform for continuing education discovery and compensation information, launching first with diagnostic medical sonography. Our live database currently operates through Lovable Cloud in Northern Virginia, United States. We collect account, credential, salary and limited usage information to run the platform. Salary entries are stored separately from names and credentials, but this does not guarantee anonymity. In a workplace with few reports, another person may be able to infer who submitted a pay figure.

Alliedly is operated by 1001317755 Ontario Inc., an Ontario corporation, under the registered Ontario business name Alliedly (BIN 1001778492). Questions, requests and privacy complaints can be sent to privacy@alliedly.ca; general support enquiries can be sent to support@alliedly.ca. We will verify the requester as needed and respond in accordance with applicable law.

Depending on how you use Alliedly, we may collect:

• Accounts and security: email address, account display name, authentication records, password-authentication data handled by our provider, multi-factor authentication settings where enabled, session and security information, and account activity needed to protect the service.
• Professional credential verification: the name shown on your credential, profession, credentialing body, registration or credential number, verification status, dates, correction requests and administrative review notes. These details are used for credential verification and related account administration. Alliedly does not currently ask you to upload certificate files, licence images or identity documents.
• Credential ownership verification: to check that a credential belongs to the person using the account, an Alliedly administrator may send a one-time code to a contact address the administrator has independently linked to the named professional (for example, a contact listed by a credentialing body, or a work address confirmed for that person), or may hold a short live call. We do not record calls or store the contact address used. We keep a record of the method used, the dates the check and its next review took place, a scrambled (hashed) copy of each code with its expiry and attempt count, and an administrator note describing the evidence reviewed. Codes expire after 10 minutes, work once and lock after 5 incorrect attempts. To prevent the same credential being claimed by more than one account, we keep a private one-way fingerprint of the credentialing body and registration number.
• Compensation and workplace details: your reported pay, pay basis and components, employer, province or location, work setting, experience, employment arrangements, benefits, scheduling and other fields you choose to submit through the compensation form. We record required acknowledgements associated with submission.
• Learning features: saved resources and topic interests if you use those features.
• Technical and security records: records reasonably necessary to operate and secure the service, including sessions, IP addresses or access logs where maintained by our infrastructure, and administrative audit records.
• Communications: information you send when requesting assistance, corrections, access, deletion or a response to a privacy concern.

Do not submit patient names, medical records, images or other patient-identifying information to Alliedly.

We use information to create and secure accounts; review professional credentials; process and verify the eligibility of compensation contributions; show permitted public compensation information; provide saved learning features; send necessary account and credential-correction messages; respond to requests; investigate misuse or security issues; and maintain the reliability of the service. We do not currently offer an opt-in marketing mailing list. Any future promotional email program will be handled separately under applicable requirements.

A contributor may submit salary information while their credential review is pending. That contribution is stored, but it does not count as a verified contribution until their credential is approved. Verification relates to the contributor's professional credential; Alliedly does not independently audit every reported wage or employer statement.

Community salary statistics. Separately from verified pay figures, Alliedly may publish Community Salary Insights based on voluntary, self-reported salary submissions. Any member with a confirmed email address may submit salary information after accepting the current Terms and Privacy Policy and confirming their profession. Administrator account approval and credential uploads are not required. Each submission is saved immediately with Pending Review status. An Alliedly administrator reviews each submission before it can be included in aggregate statistics. Pending and rejected submissions are excluded from all public salary statistics. The review screen shows only the pay and workplace details submitted. It does not show the contributor's name or email address. Self-reported submissions are not independently verified against professional registers. Only privacy-safe, aggregated and rounded statistics are published: by profession and province only, never by employer, for groups of at least 5 accounts, with additional suppression where a figure could reveal an individual contribution. Only contributors who gave the community statistics consent shown at submission are included. Individual submissions are never shown. Community statistics are not published until Alliedly separately activates them.

Salary records are stored separately from account names, emails and credential numbers, using private pseudonymous identifiers (including an account-level identifier used to count contributors and apply deletion) for internal eligibility and account functions. Technical separation does not prevent identification through the context of a public pay report.

Public pay figures are shown only as rounded aggregates for groups of at least 5 verified contributor accounts, counted once per account across years and professions. Each figure, including each benefit or premium, separately requires at least 5 contributors, and a yes/no benefit is shown only when at least 5 have it and 5 do not. Employers with fewer than 5 are not named, and individual salaries are never shown. Counting is per user account, which may not always correspond to a distinct real-world individual. Aggregates can still sometimes allow inferences by people familiar with a workplace. Names, email addresses and credential numbers are never shown with salary figures.

Please review the small-employer warning and acknowledgement on the contribution form before sharing pay information. You can contact us to request review or removal of information as permitted by law and the platform's technical processes.

Alliedly's active production database and application services use Lovable Cloud, with the database currently hosted in AWS us-east-1 (Northern Virginia, United States). Account, credential and salary information may therefore be stored and processed in the United States. Information processed there may be subject to US law and lawful access requests by US authorities. The locations of all service-provider backups and any additional processing locations have not yet been independently confirmed; we will update this statement when those details are established.

We use service providers for hosting, authentication, infrastructure and necessary transactional emails. When users open external educational links or play embedded YouTube videos, the external provider may collect information under its own privacy terms. We do not knowingly transfer credential numbers or individual salary records to learning-content providers through these features.

Alliedly uses account authentication, role-based authorization, restricted server functions and separation of account, credential and salary data. Administrative access is restricted. No online system is risk-free, and we cannot guarantee that information will never be accessed, disclosed or inferred without authorization.

Alliedly uses browser storage needed for sign-in sessions and some temporary user-interface functions. Our current application review did not identify advertising or third-party marketing trackers. External content and authentication infrastructure may process device or network information. If our tracking practices change, we will update this notice and implement any required choices.

We retain information for the purposes described above and as needed for legitimate security, operational and legal requirements, subject to applicable law. Routine cleanup of rejected credentials and superseded salary records is not currently automated; we do not promise fixed automatic purge dates that our systems do not yet enforce. Rejected salary submissions are removed from active statistics immediately and are kept, then deleted, under the same retention process as other rejected records.

When an account is deleted, the account-deletion process removes the sign-in account, credential record, role records, saved learning resources and topic interests. Before the sign-in account is removed, salary entries matched to the account through its private pseudonymous identifiers, from every contribution year, are marked unverified and no longer count toward verified public pay results.

Ownership verification codes and credential fingerprints associated with the deleted account are removed through the applicable deletion process. Credential ownership confirmation is subject to periodic review and may lapse until verification is renewed. Administrative records of ownership decisions, including evidence notes, are retained with other audit records.

Some information may remain after account deletion, including historical pseudonymous salary entries stored as unverified; administrative and security audit records; legal acceptance records containing the account's user ID, accepted document versions, acceptance event type and server-generated timestamp; and temporary backup copies. These retained records are not necessarily anonymous and should not be assumed to be irreversibly de-identified.

Database backups and recovery: Alliedly uses managed cloud infrastructure that maintains database backups for security, operational continuity and disaster recovery. Our cloud provider currently creates daily database backups and generally retains them for approximately 14 days. This is an operational rolling window managed by our infrastructure provider, not a guaranteed fixed maximum.

When personal information is deleted from Alliedly's active database, copies may remain temporarily in existing backups until those backups expire under the provider's retention procedures. Backups are maintained for security, operational continuity and disaster recovery, not for routinely accessing deleted personal information.

If a backup is restored, previously deleted information may reappear. We will take reasonable steps to reapply applicable deletion requests and retention requirements following restoration.

Backup retention periods and recovery arrangements are managed by our cloud provider and may change. We periodically review these arrangements.

If you have a request about retained information, contact privacy@alliedly.ca. We will explain what can be accessed, corrected or removed, subject to applicable law.

You may request access to personal information we hold about you, ask for correction, raise a privacy concern, or request account deletion or withdrawal of consent, subject to applicable law and legitimate retention requirements. Contact privacy@alliedly.ca. We may need limited information to verify your request and prevent unauthorized disclosure. Withdrawal or deletion may limit or end your access to certain features.

If you remain dissatisfied after raising a concern with us, you may contact the Office of the Privacy Commissioner of Canada or the privacy authority applicable to your province.

We may update this policy as our services and privacy practices change. We will display the revised date and provide additional notice or seek consent when required by law for material changes.