since 2008

Contact Nimi

Contact channels

LEGAL NOTICE - READ CAREFULLY

Before contacting us, please review our privacy policy to understand how your personal data may be processed. By choosing to contact us through any available channel, you acknowledge that you have read the relevant privacy information and consent to receiving a reply.

Read before contacting

Before contacting, we kindly ask you to please:

  • Ensure that question you want to ask has not been already answered.
  • Message includes recommended details.

Social media

Notice:

Information above is non-binding and intended for general information purposes only and has been provided in good faith. All trademarks and registered trademarks are the property of their respective owners. There is no affiliation with, nor authorization, sponsorship, or approval by, the respective owners of these trademarks.

YouTube™ is a trademark of Google LLC in the United States and other countries.

Direct contact channels

In , the General Data Protection Regulation (GDPR) became legally binding across the European Union.

To ensure full compliance and avoid any risk of violating these regulations, direct contact channels have been removed from public display. These contact methods remain valid and fully operational, but are now treated as private channels and are therefore no longer listed openly.

Submitting project error reports

To report an error generated by the project — rather than a custom report — please use the report project issue form.

Report project issue

Frequently asked questions

Questions

3

Answers

3
What details should be included when contacting?

When con­tacting about projects most important­ly please specify valid project name e.g.:

  • Incorrect ✗:
    Nimi
  • Accept­able:
    NP
  • Correct ✓:
    Nimi Places

If you are requesting an technical support please provide a clear ​and detailed descrip­tion of issue you are writing about ​and include follow­ing details:

  • Project version e.g.:

    • Incorrect ✗:
      new­est
    • Accept­able:
      from last week
    • Correct ✓:
      20080808
  • Name, version ​and bitn­ess (like 32-bit, 64-bit) of used operating system.

  • If applic­able — receiv­ed error details e.g.:

    • Incorrect ✗:
      desc. large screenshot of receiv­ed error message box
    • Accept­able:
      Module XYZ could not be initialized
    • Correct ✓:
      0x00000

  • Steps to reproduce issue e.g.:

    • Incorrect ✗:
      clicked Y
    • Correct ✓:
      enabled X, Y ​and Z, then clicked Y

Last­ly, ​in general avoid:

  • Using acronyms, jargon, non-standard abbrevia­tions.
  • File attachments.

Quicker ​and better reply

Properly composed message will help us to provide quicker ​and better response.

What if I did not receive any reply?

You might not receive a reply:

  • If you choose e-mail as con­tact mean — then we might be unable to reply, as reply is being reject­ed by the mail server.

  • Your message might have been dis­card­ed as being invalid.

    Writting a valid message

    By including recommend­ed details there is less chance to write invalid message.

When will I receive a reply?

Messages are replied ​on a daily basis. If message is a part of already start­ed corr­espondence ​or addr­esses complex matter — it might require additional process­ing time.

Quicker reply with social media

Social media have shorter propaga­tion delay as being ​on the same network, thus can be replied sooner.