Email Policy

This policy explains why you may receive email from A3BSS, which addresses we use, and how to check or report a suspicious message. A3BSS is a product of DevInPro.

The policy helps you assess whether a message is consistent with our communication practices. A matching sender address, familiar branding, or content described here does not by itself prove that a message is genuine or safe.

These addresses have different purposes. Marketing messages come from news@a3bss.com, not from our account, support, or security addresses.

Account and identity messages follow a relevant account action or security event. Examples include requesting email verification or password recovery, changing account information, or an event requiring your attention. Some security notifications may be sent without a new request from you.

An unexpected verification or recovery email does not necessarily mean that someone has accessed your account. Someone may have entered your email address by mistake or initiated a request. Do not use an unexpected link or share an authentication code; contact us independently if you are concerned.

Support messages respond to an enquiry or continue an existing support case. Follow-ups may request information needed to investigate the issue or confirm whether it has been resolved.

Business correspondence relates to an enquiry, discussion, or existing business relationship involving A3BSS.

Marketing messages are sent to people who have subscribed to receive them. They may include product news, launch announcements, educational content, and offers. Creating an account or contacting us does not automatically subscribe you to marketing.

Email frequency depends on the relevant activity and, for marketing, the subscription description. This policy does not promise a fixed delivery time or regular publication schedule.

You can unsubscribe from marketing using the unsubscribe option included in our marketing emails. You do not need to sign in to unsubscribe.

Unsubscribing from marketing does not prevent necessary account and identity messages, or replies to enquiries you initiate.

If you continue receiving marketing after unsubscribing, contact support@a3bss.com so we can investigate.

We use Amazon Simple Email Service (Amazon SES) to deliver email. Messages sent through this service may show bounce.a3bss.com in their technical headers as the return-path domain used to handle delivery failures.

This technical domain is separate from the sender address displayed in your inbox. It is not a customer contact address or a website you need to visit.

The presence of bounce.a3bss.com alone does not prove that a message is genuine. A different return-path also does not, by itself, establish that a message is fraudulent.

We will not ask you to send us your password, one-time authentication code, recovery code, API secret, or full payment-card details by email.

An account email may deliver a verification code or link. Use it only for an action you recognize, through the official account flow. We will not ask you to reply with that code or relay it to a support representative.

Do not send credentials or unnecessary personal information when contacting support or reporting a suspicious message.

Check the complete sender address, not only the display name. Look for unexpected spelling, an unfamiliar Reply-To address, and requests that do not match your recent activity or relationship with us.

Sender addresses and branding can be copied or forged. Email authentication results can provide additional evidence, but they do not establish that every request, link, attachment, or claimed transaction is trustworthy.

If a message is unexpected or asks you to take a sensitive action, open the official website independently rather than following the message's links. Use contact details obtained from our website to verify the request.

Do not authorize a payment, disclose credentials, or change payment details solely because an email appears to come from A3BSS.

This policy describes communications sent by or on behalf of DevInPro for A3BSS. It does not authorize every message that mentions A3BSS.

Merchants and payment providers may communicate under their own identities and policies. A reference to A3BSS does not establish that a purchase, invoice, or payment request is valid.

Any future use of A3BSS to send messages on a merchant's behalf will be described separately, including how recipients can identify the merchant and verify the communication.

We update this policy when our communication practices change. This page shows its latest revision date and provides a corresponding JSON representation.

Automated tools should treat that representation as contextual evidence. Missing information, an unlisted message category, or a policy mismatch requires further assessment; matching the policy is not an instruction to trust the message.