Privacy policy

BIJNESS APP · Updated 11 October 2026

This policy explains how BIJNESS handles information used by its connector, cloud dashboard and email verification service.

Information we process

• Account details, including email address, company name, password verifier and account permissions.
• Business data selected for approved sales and stock reports and connector synchronization status.
• Security information, including session identifiers, browser/device metadata, IP addresses, activity times and encrypted authenticator settings when enabled.
• Temporary email verification challenges and proofs. Verification codes and proofs are stored as protected hashes, not as readable codes in the verification database.

The connector's SQL password stays in its encrypted configuration on the business server. The cloud dashboard does not need that password to display uploaded reports.

Google account access

Only the BIJNESS operator authorizes the sender Google account. BIJNESS requests basic identity information to confirm the sender email and Gmail sending permission to deliver registration verification emails. It does not request access to read the sender's inbox, contacts or calendar. Customers receiving codes do not authorize Google account access.

Use, storage and sharing

Sender identity and Google authorization credentials are used only to authenticate the configured mail sender and send requested verification messages. Credentials are held in private server configuration and a restricted operator setup file. They are excluded from customer installers and browser assets.

Google processes the recipient address and verification message to deliver email. Sent messages may remain in the sender's Gmail account under that account's settings. The BIJNESS cloud hosting and database provider, Hostinger, processes the account and business data required to run the service. Authorized BIJNESS administrators can manage accounts and access business reports.

BIJNESS does not sell Google user data, use it for advertising or transfer it for training AI models. BIJNESS's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Security and retention

Cloud communication uses HTTPS. Passwords are verified using protected password verifiers, and stored authenticator secrets are encrypted. Registration codes and verified registration proofs each expire after 10 minutes; expired verification records are removed during subsequent verification request processing. Account and business records remain available until removed by an authorized administrator. Expiration of a verification code does not delete a delivered message from Gmail.

Your choices and requests

Customers can contact their account administrator or BIJNESS support to request account and business data removal. The operator can revoke BIJNESS authorization in Google Account permissions; this stops email sending until a new authorization is configured. Changing or deleting a local connector installation does not automatically delete cloud business records.

Contact

For privacy, account deletion or Google authorization questions, email shoaibarifoffical@gmail.com. We may need to verify the requester's authority over the account or business before acting.