Terms of service

This is the structural point of the document, and most of the rest follows from it: two different people meet AskNudge, and these terms bind only one of them.

The same split runs through personal data, where you are the controller and we are your processor. The privacy policy sets it out; this page does not repeat it.

AskNudge is a professional tool, offered to companies for their business. It is not addressed to consumers, and it is not addressed to minors.

Publisher, “we”

BeBranded, Simplified joint-stock company (SAS), RCS Bobigny 984 530 212. Full details in the legal notice.

Service

AskNudge: the application, the public booking pages and widgets, the API, and everything an account gives access to.

Customer, “you”

The company that holds the account and accepts these terms.

Organisation

Your workspace inside the service: your forms, your contacts, your meetings, your members.

Member

A person you have given access to your organisation, with a role and permissions you set.

Visitor

A person who opens one of your booking pages or talks to your assistant — whether or not they end up booking.

Your content

Everything you publish or bring in: copy, logos, domain names, form questions, knowledge base, and the data collected through your forms.

Integration

A third-party service you connect with your own account: calendar, video conferencing, CRM, advertising, telephony, payments.

What follows is what the service does today. Nothing on this page promises a feature that is not in it.

Not everything above is part of every plan, and the product changes: section 15 says how we handle that.

An account gives access to one organisation. You invite the members you want in it and give each a role: what a member can see and change follows from that role.

• You answer for your members. What they do with the account counts as done by you, and removing someone’s access when they leave is yours to do.
• Credentials are personal. Passwords and sign-in are not to be shared. Write to contact@asknudge.ai as soon as you suspect an account has been compromised.
• API keys are credentials too. Anyone holding one acts as your organisation, with the permissions attached to it. Store them as you would a password, rotate them when someone leaves, and revoke one you no longer recognise.
• What you tell us must be accurate — company name, billing address, and the email address we reach you at. A notice sent to an address that no longer works is still a notice sent.

Access to the service is by subscription. Payment goes through Stripe, which handles the card details; we never see them.

Plans and prices

[[TO FILL: subscription plans and prices]]

Billing period

[[TO FILL: billing period]]

Renewal

[[TO FILL: what happens at renewal]]

Trial

[[TO FILL: trial terms, if any]]

Refunds

[[TO FILL: refund policy]]

Prices are stated excluding VAT, which is added at the rate applicable to you. If a payment fails we tell you, and access can be suspended until it is settled — section 14 says how.

Deposits paid by visitors

You can ask visitors to pay a deposit when they book. That money goes to your own Stripe account. We are not a party to it: we do not hold the funds, we do not set the amount, and refunding a visitor is between you and them. Stripe’s own terms govern that account.

These are not boilerplate. Each one corresponds to something the service lets you do and cannot do in your place.

• What you collect. You write the questions on your forms and you decide what is done with the answers. You must have a lawful basis for each of them, inform the people concerned, and collect consent wherever your use requires consent.
• What you publish. Your booking pages, your copy, your logos, the domain names you point at the service and the knowledge base your assistant draws on are yours. They must be accurate, lawful, and yours to publish.
• What you connect. Calendars, availability rules and credentials are taken as you give them. A calendar that is wrong produces a meeting that is wrong, and the service has no way of telling the difference.
• What your integrations do next. Once a contact reaches your CRM or a conversion reaches an advertising platform, it lives there under your relationship with that provider. What happens to it then is beyond our reach — the privacy policy is explicit about that.
• Who has access. Your members, their roles and their departures are yours to manage, as are the API keys issued in your organisation’s name.
• What is sent in your name. Confirmations, reminders, follow-ups and SMS go out as you. The rules on unsolicited messages apply to you as the sender, and an unsubscribe must be honoured — the service records it, but only you can decide not to bring that address back in.

Every visitor books with you, not with us. What is offered, whether the meeting happens, what is said in it, whether a deposit is given back — all of that is between you and that person.

So you must give visitors, on your booking pages, whatever your own relationship with them requires: who you are, your own terms where you have them, and your privacy information. We provide the space for it; we cannot write it for you.

We do not contact your visitors on our own initiative. The messages the service sends — confirmations, reminders, follow-ups — go out in your name, on the settings you choose. If a visitor writes to us directly, we pass the request on to you.

For everything your visitors send through your forms, you are the controller and we are your processor within the meaning of Article 28 GDPR. We process that data on your instructions, to provide you with the service, and for nothing else: no prospecting of ours, no resale, no model training.

For your own account, your organisation and your subscription, we are the controller.

The privacy policy is the detail of all of this — what is collected, which sub-processors are used and where they are, how long things are kept, and how a request is answered. It forms part of these terms, and this page does not repeat it.

What has to hold up on your side: a lawful basis for what you collect, the information owed to the people concerned, and the consent your own advertising tags require. The service gives you the switches; it cannot decide for you whether you may use them.

Much of what makes the service useful runs through accounts that are yours: Google, Microsoft or Zoom for calendars and video conferencing, Stripe for payments, HubSpot, Pipedrive, Zoho or Attio for CRM, Meta, Google, LinkedIn, TikTok or OpenAI for advertising conversions, a telephony provider for SMS. On our side, email goes out through Resend.

Three consequences, and they are real ones.

• Your contract with each provider stays yours. Their terms apply to you and you must respect them — including the specific rules Google, Microsoft and Zoom place on applications that read a user’s data.
• We access only what the actions you asked for require, with the permissions you granted. You can revoke a connection at any time, from the application or from the provider itself; the feature that depended on it stops working there and then.
• An outage, a rate limit, a policy change or an API change on their side changes what the service can do — sometimes without warning, and always outside our control. Section 10 is about exactly that.

The honest version, feature by feature.

Availability and support

[[TO FILL: availability and support commitment]]

Until that is settled, read it as follows: the service is provided as it stands, we work to keep it up without promising a figure, and maintenance can interrupt it. We schedule maintenance outside busy hours whenever we can.

Third-party services

When Google, Microsoft, Zoom, Stripe, Resend, a telephony provider or an advertising platform is down, slow, or changes its API, the part of the service that depends on it is affected. We adapt as fast as we can. We do not control it and we do not guarantee against it.

The booking assistant

The assistant produces text, and text can be wrong. It can misread a question, state something the knowledge base does not support, or answer confidently where it should not. It is not advice, and it commits you to nothing beyond the slot it books.

You decide to turn it on, you choose the site it reads, and what it says to your visitors is published under your name. Review it the way you would review a page on your own website.

Email and SMS

Whether a message arrives, when it arrives and where it lands depends on the recipient’s provider, their filters and their mobile network. We do not guarantee delivery, timing, or placement in an inbox. A reminder that never arrives does not cancel the meeting it was reminding about.

The service must not be used to:

• publish unlawful content, or content you have no right to publish;
• send unsolicited messages, or keep writing to someone who has unsubscribed;
• mislead the people who fill in your forms about who you are or what you will do with their answers;
• collect or upload other people’s data without a lawful basis;
• reach another organisation’s data, test our security without written permission, or work around the limits set on the API;
• reverse engineer, copy or resell the service, or offer it to a third party as if it were yours.

Where use endangers the service, its other customers or someone’s data, we may suspend the account immediately and explain afterwards. In every other case we write first and leave you time to put it right.

The software, the interfaces, the copy, the visuals, the documentation and the AskNudge brand belong to the publisher or are licensed to it. Your subscription gives you a right to use them — non-exclusive, non-transferable, for as long as the subscription lasts and for the purpose of running your own bookings. It transfers nothing else.

Your content stays yours: your copy, your logos, your domain names, your knowledge base, your contacts and your meetings. You allow us to host it, display it on your booking pages and process it as far as running the service requires — and only for that.

You confirm you hold the rights to what you publish through the service, and you answer for it. The legal notice says the same thing to the public.

If you send us a suggestion about the product, we may act on it without owing you anything. That covers ideas about the product, never your data.

We are liable for damage we cause by failing to do what these terms say we do. Beyond that:

• we are not liable for what you publish, for what is said in a meeting, or for a meeting that does not happen;
• we are not liable for a calendar, a credential or an availability rule that turns out to be wrong on your side;
• we are not liable for what a third-party provider does or fails to do, nor for what your CRM or your advertising platforms do with the data you send them;
• we are not liable for indirect loss — lost profit, lost opportunity, a contract that did not happen, or the cost of data you could have exported before leaving.

[[TO FILL: limitation of liability: cap and how it is calculated]]

Nothing here limits what the law does not allow to be limited: wilful misconduct, gross negligence, or personal injury.

You cover us against a claim brought by a third party — a visitor, an authority, a rightsholder — arising from your content, your forms or your use of the service, provided we tell you promptly and let you take the matter in hand.

The subscription runs for the billing period set out in section 5 and renews on the terms stated there.

Ending it

Either party may end the subscription: [[TO FILL: notice period for termination by either party]].

We may suspend or end it sooner for a payment still unsettled after we have written to you, or for a serious breach of section 11. Except where the service or someone’s data is at risk, we write first.

What happens then

• Access to the application closes, your booking pages stop serving, your custom domains stop resolving to the service, and scheduled messages stop going out.
• Export what you need before that date. The application and the API let you do it while the account is open; afterwards it is no longer a self-service operation.
• Deleting your workspace erases your data immediately — the privacy policy says how far that reaches and what the encrypted backups keep for a few days more. Where you do not delete it yourself, nothing erases it on our side today: ending or not renewing a subscription does not, by itself, delete anything. Your workspace and its contents stay until you delete them or ask us to, which you can do at any time by writing to legal@asknudge.ai. We say so plainly rather than promise a delay we do not yet enforce.
• Invoicing documents are kept for ten years, as French accounting rules require.

The product changes, and this page changes with it. The date at the top says when this version was published.

Where a change materially affects you — the price, what you owe, what the service commits to — we tell you by email or in the application before it takes effect. Continuing to use the service after that date means accepting the new version. If you would rather not, you can end the subscription under section 14.

We may also add, change or withdraw a feature. Where we withdraw one you rely on, we say so in advance and, where there is one, say what replaces it.

These terms are governed by French law.

[[TO FILL: competent court in the event of a dispute]]

Before it gets that far, write to us: most of what ends up in front of a court could have been settled by email. legal@asknudge.ai reaches the person who can answer.

If one clause turns out to be invalid, the rest stands. Not enforcing a clause once does not mean giving it up.

These terms, together with the privacy policy and the legal notice, are the whole of what is agreed between us about the service.