Data Deletion

1. Scope

This Data Deletion policy applies to services operated byAlleria AI, Inc., including PriorityEngine, the BSOS Developer Portal and the BSOS Partner Channel.

Deletion controls differ between services because the products serve different purposes and maintain different operational, security, commercial and audit records.

Deleting a specific item, disconnecting an integration and closing an account or organization are different actions and may have different effects.

2. PriorityEngine email disconnection

A connected Gmail or IMAP account may be disconnected from PriorityEngine.

When an inbox is disconnected, PriorityEngine deletes the stored connection information used to access and maintain that provider integration.

After disconnection, PriorityEngine stops importing new messages from that provider and will not resume access or import unless the account is explicitly connected again.

3. PriorityEngine Permanent Delete

Permanent Delete is anowner-restricted, manual and irreversibleoperation.

Team members cannot perform Permanent Delete.

Before the operation is executed, PriorityEngine displays a confirmation warning explaining that the action is destructive and cannot be undone.

The workspace owner must explicitly confirm the operation before deletion begins.

Deletion sequence

After confirmation, PriorityEngine first attempts to permanently delete the selected email from the connected email provider.

If the provider deletion succeeds, PriorityEngine then removes the email from the PriorityEngine inbox.

If the provider deletion does not succeed, PriorityEngine does not represent the operation as a successfully completed Permanent Delete.

4. PriorityEngine team access

PriorityEngine separates workspace administration from normal team collaboration.

Team members may work with permitted email workflows, including replies, follow-ups and internal notes, but cannot perform owner-restricted destructive operations.

The workspace owner remains responsible for administrative, subscription and destructive controls for the workspace.

5. PriorityEngine account and workspace closure

Full account or workspace closure may require an administrative process rather than a single destructive action inside the inbox.

A closure request may involve removal or deactivation of account access, connected integrations and service data according to the nature of the account and applicable obligations.

Certain information may need to remain after account closure where reasonably necessary for:

• security and fraud prevention;
• billing and transaction records;
• accounting obligations;
• legal or regulatory requirements;
• dispute resolution;
• audit and service-integrity records.

Retained records are not intended to be used to continue normal operation of a closed account.

6. BSOS Developer Portal account and organization closure

The BSOS Developer Portal is an OEM and infrastructure-management environment. Organization closure is therefore handled through an administrative or contractual process rather than automatic self-service destruction of the organization.

A BSOS organization may have applications, API credentials, capacity allocations, usage records, provisioning records, security incidents and contractual history associated with it.

Some of these records may need to remain after access is terminated in order to preserve security, operational, commercial or legal history.

7. BSOS API credentials

BSOS API credentials may be disabled, suspended, rotated, replaced or revoked according to the applicable credential lifecycle.

Revocation prevents the affected credential from remaining valid for authorized API access according to its lifecycle state.

The complete API secret is not stored by the BSOS Developer Portal. The Portal stores a cryptographic hash and operational identifiers required to administer the credential.

Historical credential identifiers, lifecycle events or security records may remain where necessary to preserve audit and security integrity.

8. BSOS usage records

The BSOS Developer Portal maintains operational usage records needed to administer capacity and processing entitlements.

These records may include execution identifiers, organization, application, API-key identifiers, environment, processing units, runtime or engine versions and timestamps.

The BSOS usage ledger is not designed as storage for the business content submitted to the BSOS Runtime for processing.

9. BSOS Customer Data

Customer Data submitted through BSOS remains the customer's data.

Alleria AI, Inc. processes Customer Data only as necessary to provide, operate, secure and maintain the BSOS service and according to the applicable commercial or data-processing agreement.

Data-return, deletion or retention obligations for an OEM customer may also be governed by an applicable Master Services Agreement, Order Form or Data Processing Agreement.

10. BSOS Partner Channel account records

Partner Channel records may include partner account information, organization information, invitations, terms acceptance, Client Links, attribution records, confirmed sales, commissions and payout records.

Because these records may document contractual and financial activity, not every record is automatically destroyed when a user stops using the Partner Channel.

11. Partner Channel sensitive payout data

Sensitive payout-submission information is handled separately from the permanent payout and commission audit records.

Depending on the payment destination, this temporary submission may include:

• legal payee information;
• registration information;
• tax information or tax identifiers;
• bank-account or IBAN information;
• BIC or SWIFT information;
• routing or clearing information;
• bank name and bank country.

The Partner Channel is not used as permanent storage for sensitive payout-submission data after that payout lifecycle is completed.

12. Partner accounting and banking records

Deletion of sensitive payout information from the Partner Channel does not mean that all evidence of the underlying payment disappears.

Alleria AI, Inc. may retain accounting records, transaction evidence and other information required to document commission payments and comply with financial, accounting or legal obligations.

Beneficiary or banking information may also remain in the systems of the company's bank or payment provider where those systems retain beneficiary information for legitimate banking or payment purposes.

Those records are separate from the sensitive payout submission temporarily stored in the BSOS Partner Channel.

13. Why some records may be retained

A deletion request does not always require destruction of every record connected to a prior service relationship.

We may retain limited information where reasonably necessary for:

• legal or regulatory obligations;
• tax and accounting requirements;
• payment and transaction history;
• security investigations;
• fraud prevention;
• credential and access auditing;
• contract enforcement or dispute resolution;
• documenting confirmed partner sales and commissions;
• maintaining system and service integrity.

Where information is retained for these purposes, retention does not mean that a closed account remains active or that the information continues to be used for ordinary product operation.

14. Data deletion requests

Where deletion is not available through a direct product control, a user, customer or authorized organization representative may contact us to request deletion or closure.

We may need to verify the identity and authority of the person making the request before acting on it.

For organization accounts, we may also need to confirm that the requester has authority to act for the applicable workspace, organization or contractual customer.

15. How to submit a request

Data deletion or account-closure requests may be sent to:

Alleria AI, Inc.
Email:hello@priorityengineai.com

Please include enough information to identify the relevant account, workspace or organization, but do not send passwords, complete API secrets, bank-account credentials or unnecessary sensitive data by email.

16. Verification and processing

Before processing a deletion or closure request, we may request reasonable verification to protect accounts and organizations against unauthorized deletion.

The scope and timing of a deletion request may depend on the type of data, service involved, contractual relationship and any applicable legal or regulatory requirements.

Where information cannot immediately be deleted because it must be retained for a legitimate legal, financial, security or contractual purpose, it may remain limited to that purpose.

17. Mandatory privacy rights

Nothing on this page limits data-protection or deletion rights that cannot lawfully be excluded or restricted under applicable law.

Depending on your location and applicable law, you may have rights relating to access, correction, deletion, restriction, portability or objection to certain processing.

Additional information is available in ourPrivacy Policy.

18. Security of deletion operations

Destructive actions are treated separately from ordinary user workflows.

Where a deletion action could materially affect business data, credentials or organization access, the service may require appropriate authorization, confirmation or administrative review before execution.

Additional information about our security approach is available on our Security page.

19. Changes to this Data Deletion policy

We may update this page when our deletion controls, retention practices, service architecture, contractual model or legal requirements change.

The current version will be published with an updated "Last updated" date.

20. Contact

Questions about deletion, retention or account closure may be sent to:

Alleria AI, Inc.
Email:hello@priorityengineai.com