Reference

Legal terms for your b612 account

We set out how your account is handled, which law applies to access, and how we manage data, cookies and requests for change.

TermsPrivacyCookiesAccess
b612 Legal terms for your b612 account
REQUEST PATHS

How to send legal requests

If you need help with terms, privacy wording or a data request, we keep three paths open inside your account flow.

In-account form Send correction, access or deletion requests from the form inside your account. That keeps the request tied to the right profile and helps us apply the clause that fits your region.
Written email If you want a written trail, email support from your account area with the page name, the account detail involved and the change you want. We use that record to match your request.
Formal record For a legal dispute, open a support ticket and ask for a dated record of the issue, the clause involved and our reply. We keep the chain clear so you can refer back to it.
DATA AND LOGS

How we handle your records

We collect only the data needed to run your account, confirm requests and keep the records the law asks us to keep.

Data use

We use your account name, contact details and activity logs to handle access, support, fraud checks and record keeping. We do not use more data than we need for the request in front of us.

Cookies

Cookies keep your session active, remember language choice and store basic page state. They do not change the legal terms that apply to your account, and you can clear them through browser settings.

Login security

We ask you to protect your password, device and one-time checks. If a login looks unusual, we may pause access until the account details are confirmed and the session is reset.

Retention

Records are kept for the period needed for support, dispute handling, audit or legal duty, then removed or anonymised when that period ends. We do not keep files longer without a reason.

Change requests

If your details change, send the update from the account form so we can compare it with the record we already hold. We may ask for proof before we edit sensitive fields.

Who to contact

For privacy, access or complaint matters, the support route in your account is the fastest way to reach the right team. Add the account email and the clause you want us to check.

Common questions on rights and data

These answers cover local access, data use, cookies, retention and change requests. If a rule differs by region, the local rule applies first, and we answer from the clause linked to your account. We may ask for proof before changing records, and we keep a written trail so you can follow what was asked, checked and updated at any stage of the request.

The terms linked to your account region apply first. If a rule is updated, we use the version in force when you access the site, unless the new wording says it works differently.

Access depends on local law and is available only where local law permits it. If a page or feature cannot be shown in your region, we keep it out of the account flow.

We keep the data needed to run the account, answer requests and meet legal record duties. That usually means contact details, session logs and the history of changes tied to your profile.

Cookies help the site remember your session, page state and language choice. They do not change the legal position on access or eligibility, and you can clear them in your browser at any time.

Yes. Send the request from your account form or support path, name the detail that needs changing and add enough context for us to match it to your record. We may ask for proof.

We keep records only for the time needed for support, dispute handling, tax or legal duty, then remove or anonymise them when that period ends. If a longer hold is required, we say why.

Use the support route in your account and choose the legal or privacy path if it is shown. That sends the case to the team that can check the clause, the record and the reply date.