Privacy Policy

Who we are

Momentem, a Gridwork company. The contracting entity behind this site is Gridwork Ltd, registered in RAK Innovation City, Ras Al Khaimah, United Arab Emirates, incorporated on 15 May 2026, with its registered office at Office A, Innovation City Business Center, Al Rifaa, Ras Al Khaimah, United Arab Emirates.

Our people work from Dubai, United Arab Emirates, and that is where an enquiry is read and answered. This policy covers momentem.ae and the enquiries it produces. It does not cover work carried out under a signed engagement, which is governed by that agreement.

We are the controller of the personal data described here. For anything to do with it, write to privacy@momentem.ae.

What we collect

Three categories, and nothing else through this site.

• ·What you tell us. Your name, work email address, company, your phone number if you choose to give it, and whatever you write in an enquiry, a booking or a conversation with Laik.
• ·What the booking needs. If you book an intro call we take the time you chose, your timezone, and what you said you want to build, so the engineer arrives having read it.
• ·Basic technical data. Pages viewed, approximate region, referrer and device type. We use it to understand which material is worth writing more of. It is not used to build a profile of you and it is not sold.

We do not ask for, and would rather you did not send, government identifiers, payment card details, health information or anything else sensitive. If a scoping conversation genuinely needs commercially sensitive detail, ask us for a non-disclosure agreement first and we will send one.

Laik, and what happens to what you type

Laik is the chat agent in the corner of this site. It is software, not a person, and it says so if you ask. It is worth being precise about what it does with your words, because it does more than a contact form would.

• ·What you type is sent to Anthropic, who run the model that produces Laik’s replies. Anthropic process it to generate a response and do not use it to train their models.
• ·The conversation is stored in our own database so a person can pick up where Laik left off, and so we can see when it has answered badly.
• ·If you give an email address or a phone number, that becomes an enquiry record, and it is passed to Klaviyo so we can reply and send you anything genuinely useful on what you are working on. Laik tells you what the address is for before it asks.
• ·If you book a call, the time, your name and your email go to Cal.com, which issues the calendar invitation and the meeting link.

Laik has a hard limit on how long a conversation can run and how much it can spend, and it hands over to a person when the answer matters and it does not have one. It cannot see anything about you that you have not typed into it.

If you would rather not talk to an agent at all, email hello@momentem.ae and you will get a person straight away. Nothing on this site is only reachable through Laik.

Why we hold it

Each category has one reason, and we do not repurpose it later.

• ·To answer you. If you send an enquiry or book a call, we hold what you sent for as long as it takes to have that conversation properly.
• ·To run the business. Records of who asked us for what, so we can tell whether we are useful to the people we say we serve.
• ·To send you things you asked for. Only where you have given us an address for that purpose, and every message carries a one-click unsubscribe that works.
• ·Because we have to. Where a law or a regulator requires a record to be kept for a period, we keep it for that period and no longer.

We do not sell personal data, we do not share it for anyone else’s marketing, and we do not run advertising pixels on this site.

How long we keep it

• ·An enquiry that goes nowhere: two years from the last contact, then deleted.
• ·A chat conversation: twelve months, so we can audit how Laik behaved, then deleted.
• ·Someone who becomes a client: for the life of the engagement and seven years after it, which is what UAE record-keeping expects.
• ·Marketing contacts: until you unsubscribe, plus a suppression record so we do not accidentally contact you again.
• ·Technical logs: thirteen months.

You can shorten any of these by asking. We will not argue about it.

Who else sees it

A short list, because a policy that names none is not describing a real system. Every one of these is reachable from a single enquiry, and each is bound by a contract that limits them to acting on our instructions.

Vercel

Hosting and delivery of this website. Data held in the European Union and United States.

Neon

The database holding enquiries and chat transcripts. Data held in the United States.

Anthropic

The model behind Laik, our chat agent. Data held in the United States.

Cal.com

Scheduling and calendar invitations for intro calls. Data held in the European Union and United States.

Klaviyo

Email and messaging to people who have asked to hear from us. Data held in the United States.

Google Workspace

Our email and calendars. Data held in the European Union and United States.

OpenStreetMap

The map on the contact page, loaded only when you open that page. Data held in the United Kingdom and European Union.

Some of these are outside the UAE. Where that happens we rely on the provider’s standard contractual protections and satisfy ourselves that the arrangement is lawful before using them. We will tell you which provider holds what if you ask.

Beyond this list, we disclose personal data only where a law or a court requires it, and we will tell you when that happens unless we are forbidden from doing so.

Client data during an engagement

This is the part that matters most to the people who hire us, and it is not really a website question, but it belongs here because people ask.

• ·Client data stays in the client’s environment. We build in your cloud account, against your systems, under your access controls.
• ·We do not use client data to train models, and we do not carry it from one client to another. What we carry is the engineering, not the data.
• ·Where a build sends data to a model provider, that is set out in the engagement, the provider is one you have approved, and the arrangement is configured so the provider does not train on it.
• ·Everything we build is yours: the repository, the evals, the infrastructure definitions. On the day an engagement ends you keep all of it.

The engagement agreement, not this page, is what governs any of that. Where the two disagree, the agreement wins.

Your rights

Whatever your jurisdiction, we will do the following on request, because it is the right way to behave and not because a particular law compels us.

• ·Tell you what we hold about you, and give you a copy.
• ·Correct anything that is wrong.
• ·Delete it, unless a law requires us to keep it, in which case we will tell you which one and for how long.
• ·Stop sending you things, immediately and permanently.
• ·Export what you gave us in a form you can take elsewhere.

Write to privacy@momentem.ae. We aim to answer within five working days and to have it done within thirty. You will not be asked to justify the request.

Security

Encryption in transit and at rest, access limited to the people who need it, multi-factor authentication on every account that touches production, and no shared logins. Our chat endpoint is rate limited per address and carries a hard spending ceiling so it cannot be used to run up a bill or scrape us.

IP addresses are stored only as a salted hash, which is all a rate limiter needs and nothing a leaked table could be used for.

If a breach ever affects your data, we will tell you what happened, what we know, and what we are doing about it, without waiting to be asked and without minimising it.

Changes and contact

When this policy changes materially we will change the date at the top and, where the change affects people already in our records, tell them directly rather than relying on them to re-read the page.

Write to privacy@momentem.ae and a person will answer. If you are not satisfied with how we have handled something, say so in the same thread and it will be escalated rather than closed.