Skip to content

Security and data.

Where your images go, who can see them, and how long we keep them.

Your images, from upload to deletion

Your photos arrive in London, are processed in Romania and return to London for collection. Photos and finished images are deleted after 30 days; separate opt-in training copies follow the rules below.

  1. 1

    Your system

    sends a photo

  2. 2

    Our servers, London

    receive it

  3. 3

    Processing, Romania

    makes the finished image

  4. 4

    Our servers, London

    keep it for 30 days

  5. 5

    Your system

    collects it through a link that expires after 24 hours

  • Your images are processed in Romania (European Union) and stored in London.
  • Your photos and finished images are deleted 30 days after the job. Separate opt-in training copies follow the training rules below.
  • We don't use your images to improve our AI unless an owner of your account switches that on.
  • Our data processing agreement is the European Commission's own standard clauses, accepted with one tick when you sign up.

Training is off unless you switch it on

Only an account owner can opt in. Training copies are kept in a separate company archive and never used in marketing.

  • "Help improve Motuva with our photos and images" is off unless an owner of your account switches it on. It never applies to images sent before.
  • While it's on, we keep a copy of each photo you send and its finished image, with camera and location data removed, in a separate archive for your company.
  • We use those copies only to improve Motuva's image processing. We never sell or license them, publish them or use them in marketing.
  • For those copies we are the controller, and our privacy notice explains how we handle them.
  • Switching it off, or closing your account, deletes your company's archive within 30 days.

We never use your images in our marketing, whether training is on or off.

An account owner chooses. No earlier images are included.

Access, delivery and recovery

A password and email code protect your team’s access. Restricted keys and signed notifications connect your systems. Staff access needs a reason and leaves an audit record.

Signing in

Your team uses a password and a fresh code sent to work email. Five roles control access.

API keys

A key is shown once. Restrict its steps, daily image allowance and internet addresses. Revoking it stops it at once.

Keeping customers apart

Application checks and database rules each restrict access to the caller’s company.

What our staff can and can't do

Staff image access requires a recorded reason. Staff cannot sign in as you or see your passwords, keys or codes.

Uploads and the images we return

Photos arrive by upload, with file-type and size checks. Returned images have camera, location and other hidden metadata removed.

Webhooks

Signed HTTPS notifications let your system check the sender. Your system collects images separately through the API.

Encryption and hosting

Connections, stored data and backups are encrypted. Enterprise runs on its own server and database.

Backups and incidents

Database backups last seven days, with a second-region copy in Ireland. Owners receive incident emails and the hub shows service status.

Logs

Your activity log records account actions. Application logs exclude passwords, keys, secrets and download links.

Our papers and your questions

Read the Terms, Data Processing Agreement, data-handler list and privacy notice. Signed copies are available for procurement. Send security questionnaires or concerns to hello@motuva.com.

A security questionnaire, or a problem to report?

Send your questionnaire through Talk to us or to hello@motuva.com. If you think you've found a security problem, tell us at hello@motuva.com first and give us a chance to fix it.

Start with 50 free test images. No card.

Start freeTalk to us