Open MicoCam

Independent support

Tell MicoCam what happened, without sending what we do not need.

A useful request identifies the product task, the symptom or concern, the approximate time, and a safe way to reply. Choose a narrow category so the right handling path is clear from the beginning.

Email [email protected] Read the page
Use forNon-emergency MicoCam questions
Never sendPasswords, codes, full card details, or unnecessary private media
01

Write a useful request

Lead with the action you were trying to complete.

Choose product support, account access, payment, privacy, accessibility, safety, or another specific category. Describe what you expected, what actually happened, and the last step that worked.

Include your device and browser for technical problems, or a non-sensitive order reference for payment questions. Use the account-data route for formal rights or deletion requests so any identity check matches the action.

  • →Use a clear subject and one primary issue
  • →Include approximate time and reproduction steps
  • →State the outcome or next action you need
02

Keep the message safe

More evidence is not always better evidence.

Crop screenshots to the relevant interface and remove private messages, profile details, notification previews, and unrelated account information. Describe harmful content rather than forwarding it when a description is enough.

Do not use email as an emergency channel. For immediate danger, contact local emergency services or a qualified local resource. End and block ongoing unwanted contact before waiting for a reply.

  • →Never include a password or one-time code
  • →Do not email full payment-card or identity-document images
  • →Do not attach intimate or illegal material to a general request

Message outline

A support email MicoCam can act on

Use this order to keep the request readable and privacy-aware.

  1. 01

    Category and concise subject.

  2. 02

    Action you were trying to complete.

  3. 03

    Expected result and actual result.

  4. 04

    Approximate date, time, device, browser, and market when relevant.

  5. 05

    Non-sensitive reference and minimal cropped evidence when necessary.

  6. 06

    Preferred safe reply method and the outcome you seek.

Clear answers

Contact boundaries

Can I send my password so support can test the account?

No. Never send a password or verification code. Use the service's authenticated recovery flow.

Is email the right place for immediate danger?

No. End contact and use local emergency or specialist resources appropriate to the situation.

Can MicoCam support another company's account?

No. This contact route covers the independent MicoCam service only.

Continue with context

Choose the next useful page

01Help center

Try the closest self-service path first.

02Account and data

Use a scoped path for account-specific requests.

03Report and block

Act inside the product after harmful behavior.

Contact with context

Send enough to act, not enough to create a second risk.

Keep the request narrow, factual, and free of credentials or unnecessary private material.

Email [email protected]