Use the right authenticated path

Account access and data requests need more care than a general support message.

Recovery, deletion, correction, access, payment, and safety actions can affect different systems and require different levels of identity proof. Start with the exact action rather than sending a broad collection of personal data.

Start an account request Read the page

RecoveryUse the presented authenticated flow

Data requestState access, correction, deletion, or another exact action

SecurityNever send passwords or verification codes

Account access

Recovery should prove control without collecting unrelated identity data.

Use the sign-in or recovery path presented by MicoCam. A legitimate support process should not ask you to email a password or one-time verification code.

If access appears compromised, secure the connected email or sign-in provider, end suspicious sessions when the product offers that control, and describe the approximate time and symptoms without exposing credentials.

→Use the official recovery flow
→Secure connected accounts first
→Treat unexpected code requests as a warning

Data and payment scope

Name the request so the correct records and safeguards apply.

Access, correction, deletion, objection, export, and account closure are different actions. State the exact request and the account identifiers you already use, then wait for a proportionate verification step through the designated path.

Keep payment questions separate from general data requests. A date, amount, currency, status, and non-sensitive order reference are usually more useful than a full card image or bank statement.

→Separate account closure from a data-rights request
→Keep payment instruments out of ordinary email
→Expect legal or safety holds to be explained when relevant

Request clarity

Prepare an account or data request

State the minimum facts that identify the action without oversharing.

01
The exact action: recovery, access, correction, deletion, export, closure, or payment review.
02
The account contact or identifier already associated with MicoCam.
03
A safe reply method you still control.
04
Approximate dates and non-sensitive references relevant to the request.
05
No password, one-time code, full card image, or unrelated identity document.
06
Any accessibility need affecting the verification process.

Clear answers

Account and data boundaries

Should I email my password for account recovery?

No. Use the official recovery flow and never send a password or one-time code.

Is deleting an account the same as a formal data request?

Not always. State the exact outcome you want so the appropriate account and data processes can be applied.

What payment information is safe to include?

Use a non-sensitive order reference, date, amount, currency, and status. Do not email full card or bank details.

Scope the request

Ask for the exact action, then verify only what that action requires.

A narrow account or data request is easier to route, safer to verify, and less likely to expose unrelated information.

Start an account request