FAQ

MeetingAgreement helps people make expectations and ground rules clear before a meeting or another important interaction. The organizer prepares an agreement, and participants receive a link or QR code where they can easily see what applies and accept the same version. Clear expectations create better conditions for trust.

A meeting tool may provide video calls, chat or scheduling. MeetingAgreement does not host the meeting. It clarifies the ground rules participants agree should apply to it.

No. An NDA and MeetingAgreement serve different purposes. MeetingAgreement should not be presented as a replacement for an NDA, a contract or legal advice. They may be used together when appropriate.

MeetingAgreement does not automatically determine the legal effect of an agreement. That may depend on its content, context, parties and applicable law. Anyone needing an assessment of legal effect should seek qualified legal advice.

MeetingAgreement cannot technically prevent someone from breaking what the participants agreed. If someone knowingly acts against an agreement they personally accepted, they also break the trust on which that agreement is based. The accepted agreement remains as a record of what the participants agreed, which version was accepted, who accepted it and when. For example, if the participants agreed that the meeting must not be recorded and someone records it anyway, that person has acted against the agreement. Any further consequences depend on the situation. Employment agreements, NDAs or other confidentiality agreements, internal policies, other contracts and applicable law may be relevant and, depending on the circumstances, may lead to employment-related, contractual or other legal consequences. MeetingAgreement does not determine whether a breach of contract or law has occurred and does not replace legal advice.

Yes. For the agreement to be complete, every active participant must explicitly accept the same current version. Each participant responds for themselves, and silence never counts as acceptance.

The agreement is then not marked complete. A participant can decline or propose a change, after which the organizer needs to resolve the issue, publish a new version or end the process.

Yes. A participant can ask for clarification or propose a change instead of accepting. If the agreement changes, participants review and respond to the new version.

A published version is not rewritten afterwards. If rules, participants or relevant meeting details change, the organizer publishes a new version for participants to consider.

No. A participant can open the link or QR code, see what applies, identify themselves and respond without first creating an account. The participant list builds as people respond. An account can be optional for someone who wants to collect received and self-created agreements in one place.

No. MeetingAgreement is not a recording, video or transcription tool.

No. MeetingAgreement does not store a meeting’s audio, video, transcript or conversation. What may be retained is the agreement and the information needed to show who accepted which version and when.

Yes. The agreement can explicitly state that the meeting must not be recorded, so every participant sees and accepts that ground rule before the meeting. This does not by itself determine what the law permits in a particular situation or jurisdiction.

Yes. The agreement can explicitly state whether and how AI may be used, for example for transcription, summarization or other processing. Such use should be clear to participants and included in the version they accept.

MeetingAgreement does not create transcripts or AI summaries. It helps participants agree in advance whether other tools may create such material, who may access it and how it may be used. The agreement does not itself determine what the law permits.

Yes. The agreement can explicitly state what material may be shared, by whom and with whom. The wording needs to fit the meeting and any other policies or agreements.

Yes. An organization can use shared templates and specify rules arising from its policies. It should be clear which rules apply, why they are included and what participants are expected to accept before the meeting.

An organization administrator may have access to agreements owned or managed by the organization, according to its policies and permissions. A user’s personal or earlier agreements do not become visible merely because the user belongs to the organization. The visibility that applies should be clear to the user.

As a starting point, a user has their own agreements. An agreement created in an organizational context may instead be organization-owned and managed according to the organization’s policies and permissions. Ownership and applicable visibility should be clear before the agreement is created or sent.

Yes. A personally owned agreement should not become visible to an employer or another organization merely because the user belongs to it. An organization-owned agreement is instead subject to the visibility and permissions clearly stated by the organization.

No. MeetingAgreement is a web-based service and requires no separate installation. It opens in a browser on a phone, tablet or computer.

Yes. The web interface is designed for phones, tablets and computers. No separate mobile app is needed.

MeetingAgreement can be used alongside Teams, Zoom and other meeting tools, but it has no direct integrations with them.

No. MeetingAgreement does not offer a public API.

No. A participant responds to the agreement through the link or QR code and does not need BankID.

The Security page describes verified safeguards, access and organizational visibility.

Read the security information

MeetingAgreement processes the information needed to create, manage and accept agreements. The service does not record or store the meeting conversation. The Privacy page explains what personal data may be processed, why it is needed and which rights you may have.

Read the security information