DEV

Help

Getting started guide

All topics

  • What is Kennu?

    Kennu prepares meetings between organizations. Before the meeting, everyone gets a briefing: who will be in the room, what each organization does, and what the meeting is about.

    After the meeting you stay connected to the people you met. When someone changes roles or a team updates what it offers, you see it.

  • How does signing in work?

    Kennu has no passwords. Enter your email and we send you a sign-in link. The link works once and expires after one hour; you can open it on any device.

    No email? Check your spam folder, make sure the address is spelled correctly, and request a new link. New here? The same link creates your account.

  • How do I create a meeting?

    Open Meetings and choose New meeting. Add a title, date, time and purpose, pick colleagues, add external attendees by name and email, and choose the content that fits the conversation.

    Everyone in the meeting sees who will attend and the content you shared. You can edit or cancel the meeting at any time.

    Paste the meeting link (or the ready-made invitation text) into your Zoom, Google Meet or Teams invite. Everyone on the Kennu attendee list opens the briefing with it; anyone else can only request access.

  • How do templates work?

    A template is a set of content for a recurring type of meeting — for example an interview in HR or a partnership kickoff — plus a default duration and purpose. Create templates under Content → Templates; department members manage their department's templates.

    When you create a meeting, choose "Start from a template": its content, duration and purpose are preselected and you can still change everything. Templates point to modules, so briefings always show the latest version.

  • How do I plan a follow-up?

    On the meeting page, choose "Plan follow-up". The new meeting starts with the same attendees and content, one week later — adjust what you need.

    The briefing shows "Follow-up to …" with a link to the previous meeting, but only to people who attended it. New attendees see a normal briefing.

  • How do I know who has read the briefing?

    On your meeting page you see who opened the briefing and when — so you can skip the round of introductions with confidence.

    Send the briefing from the same page. Guests get a personal link; colleagues get a heads-up. Use Resend if someone can't find the email.

  • I got a meeting invite — what now?

    Open the link in the email. The first time, it signs you in and shows the briefing right away: who will be in the room and what the other side shares. Add your name and role so they know who you are.

    The link is personal. After the first use, or if you already have a Kennu account, you sign in with your email as usual. Guests never pay.

    Already on Kennu? New invitations also appear on your dashboard. The others only see your profile once you open the briefing.

  • How do I share my company's content in someone else's meeting?

    Context flows both ways: as a guest you can add your own organization's content — company overview, services, contacts — to the briefing you were invited to.

    Open the briefing and use “Share your side”: tick the modules you want to share and save. Everyone in the meeting sees them under your organization's name; you can change the selection at any time.

    Not on Kennu with your company yet? “Create organization” in the briefing sets it up in a minute and brings you right back. The organizer can't change what you share, and you can't change theirs.

  • Can I ask questions before a meeting?

    Yes. Every briefing has “Questions for the meeting”: add a question or a topic you'd like to cover, so everyone can prepare. All attendees see it — guests included.

    Organizers mark questions as covered, can remove them, and can switch questions off for a meeting on its page. They get at most one email a day about new questions.

    It's deliberately not a chat: questions are for preparing the meeting, not for discussing it in writing.

  • Why can't I open a meeting link someone forwarded?

    Meetings are private: only attendees can open them, even with the link. If you're not on the list, you can ask the organizer for access with a short note.

    The organizer approves or declines. You get an email either way; if approved, the briefing opens with your account.

  • What are connections?

    After a meeting has taken place, you're connected to the people from other organizations you met, and to those organizations. Colleagues from your own organization aren't connections — you find them under Organization.

    A connection shows what the meeting already showed you: the person's current profile, the meetings you had together, and the content their organization shared with you. Nothing else becomes visible.

    Mute a connection to stop update emails about it, or remove it to hide it. If you meet again in a later meeting, you're connected again.

  • How do updates from my connections work?

    When someone you're connected to changes their profile — a new role, new contact details — or their organization changes content it shared with you, Kennu shows it under “What's new” on Connections and on your dashboard.

    Only real changes count: confirming that content is “still correct” or fixing a typo twice in a row doesn't flood you. Opening a connection marks its updates as seen.

    You get at most one update email a day, never about muted connections. Switch update emails off in your profile, or with the unsubscribe link in any email.

  • Who can see a meeting?

    Only its attendees and the people who manage it (the organizer and your organization's owners and admins). Meetings are never searchable, and the meeting link alone grants no access.

    External attendees are stored as name and email only, until they join Kennu.

  • How do I set up my organization?

    Open Organization in the menu and create it with a name and website. You become its owner.

    Add departments (for example Legal or Sales) so each team can keep its own content, then invite colleagues and assign them a department.

  • How do I invite colleagues?

    Owners and admins invite colleagues by email under Organization. Each invite is personal: it only works for the address it was sent to and expires after 14 days.

    Roles: owners manage everything, admins manage members and all content, members maintain their own profile and their department's content. During early access, everyone can organize meetings.

  • Why add a backup owner?

    A backup owner is like two-factor authentication for your organization. If you're away, leave the company or lose access to your email, a second owner can still manage members, roles and content.

    You're asked for one when you create the organization; you can skip it and add one later under Organization → Invite colleagues, with the role Owner. Only owners can invite owners.

  • What do department managers do?

    Each department can have managers — at least two are recommended, so the department keeps running when one is away (like a backup owner, but for a team). Managers have equal rights.

    Managers invite colleagues into their department (optionally as managers too), add members without a department to it or remove them from it, and name or remove other managers. They also maintain the department's content and templates, like every member of the department.

    Owners and admins name the first manager: under Organization, invite someone with “Department manager” ticked, or use “Make manager” next to a member. Roles, departments themselves and removing people from the organization stay with owners and admins.

  • What is content and who maintains it?

    Content modules describe your organization: About us, Products & services, Contacts by topic, or anything custom. Each belongs to the whole company or to one department.

    Owners and admins can edit everything; department members edit their department's modules. Each module shows when it was last updated, so you can spot stale information before sharing it.

    You can attach PDF files and images (up to 10 per module, 10 MB each), for example a product sheet. Editable formats like Word or Excel aren't accepted, and files are always downloaded, never opened in the browser.

  • How do freshness reminders work?

    Content goes stale: people change roles, offerings change. Kennu reminds whoever looks after content when it hasn't been updated or checked for a while — by default every 6 months.

    Department managers set the interval for their department (3, 6 or 12 months, or no reminders) on the Content page; owners and admins set it for company-wide content. Departments without a manager are looked after by owners and admins.

    Nothing to change? Click “Still correct”: the content counts as checked, and your connections don't get an update. When picking content for a meeting, organizers see what's due and can ask for a review with one click.

    You get at most one reminder email a week, and you can switch it off in your profile. Your own profile asks “still correct?” every 6 months.

  • Who can see my profile?

    Only people you share a meeting with, and people you're connected to through a meeting. Your profile is never public or searchable.

    You maintain it once; every meeting shows the latest version. Your photo is stored privately and shown through short-lived links.

  • How do I change my photo or details?

    Open Profile in the menu. Change any field and select Save. To change your photo, select Change photo (JPG, PNG or WebP up to 2 MB) — it's saved right away.

    Name and role matter most: they're what people see first in a briefing.

  • What are signed-in devices?

    Devices shows every browser where your account is signed in, with an approximate location and when it was last active.

    Don't recognize one? Select Sign out next to it, or sign out all other devices at once. They're signed out immediately.

  • How do calendar and Zoom integrations work?

    Organizers can connect Google Calendar (including Google Meet), Microsoft Outlook (including Teams) or Zoom under Settings → Integrations.

    Every few minutes Kennu looks at meetings you organize in the next 60 days. A meeting with at least one person from outside your organization becomes a briefing draft, with the attendees, date and time. Meetings with colleagues only, recurring series and all-day events are skipped.

    Nobody hears from Kennu until you add content and send the briefing. Then the briefing link is added to the calendar event or the Zoom agenda, so everyone finds it where the meeting is.

    Until you send the briefing, the draft follows changes in your calendar (time, title, cancellation). Disconnect any time: Kennu deletes its stored access. Owners and admins see all connected accounts under Organization → Integrations.

  • How do I change the language?

    Use the language menu at the top of the page. When you're signed in, the choice is saved to your profile and also used for emails from Kennu.

    Kennu is available in English, Spanish, French and German.

  • What's in the activity log?

    Kennu records who did what and when: sign-ins, invites, role changes, content edits, meetings, briefings sent and opened, access requests and more. Entries can't be changed or deleted.

    Owners and admins see their organization's log under Organization → Activity, with filters for person, type, meeting and date. Organizers see each meeting's activity on its page. Everyone sees their own under Profile → Your activity, including who opened briefings they're part of.

    IP addresses are stored only for sign-ins and denied access attempts, and are never shown in the app. When someone deletes their account, their entries stay but no longer identify them.

  • How do I connect Kennu to other tools (API, webhooks, AI assistants)?

    Owners and admins find everything under Organization → Developers: create API keys (full access or read only), add webhook endpoints, and see the log of API requests. The full reference is at kennu.io/docs/api.

    With the API your CRM or calendar tooling can create meetings, add attendees and content, send the briefing and see who read it. Webhooks tell your systems when that happens; deliveries are signed so you can verify them.

    AI assistants that support MCP (such as Claude) can use Kennu too — “who am I meeting tomorrow?” — through the MCP server with an API key. A read-only key lets an assistant read but not change anything.

  • What do the metrics show?

    Metrics (under Organization; owners and admins, and department managers for their own department) answer one question: do people read the briefing before the meeting? The read rate counts attendees who opened it before the meeting started, for colleagues and guests separately.

    You also see how many meetings had a briefing sent, the median time from sending to first opening, and how much of your content is up to date. Filter by period and department.

    Metrics are aggregated — they never show what one person did. Who opened a specific briefing is on that meeting's page.

  • How do I verify my company's domain?

    Under Organization → Domains, add your domain (e.g. company.com). Kennu shows a TXT record: add it at your domain provider, then click “Verify DNS record”. DNS changes can take a few minutes.

    Once verified, briefings show “Verified” next to your organization — guests know the content really comes from you. A domain can be verified by only one organization.

    Optionally, let people with an @company.com address join without an invite, or limit organization invites to your domain. Meeting guests are never affected.

  • What happens with my data?

    Your data is used to run Kennu, nothing else. There is no advertising, no tracking cookies and no session recording; page statistics are anonymous and cookieless.

    Important actions — like sign-ins and profile changes — are recorded in a security log; a view of your own account activity is coming. Delete your account at any time under Profile → Delete account; for a copy of your data, write to legal@kennu.io.

  • Do invited guests pay?

    No. People you invite to a meeting never pay — they sign up from the invite with just a name and a role.

    Kennu is free during early access. Later, only the people who organize meetings will need a paid seat.

Privacy policy

Effective October 18, 2026

In short: Kennu collects only what you and your organization choose to enter, and shares it only with the people you meet. Your profile is shown to colleagues in your organization, to attendees of meetings you take part in and, later, to your connections. Meetings are never public or searchable. We do not sell data or share it with advertisers, and we use no tracking cookies.

The English version of this policy is legally binding.

1. Who we are

Kennu is operated by Concept & Code, LLC, a U.S. limited liability company. Privacy contact: legal@kennu.io. For users in the EEA and the UK, Concept & Code, LLC is the data controller for accounts and for operating Kennu. For the content an organization puts into Kennu (its content modules, attachments and meetings), we process data on the organization's behalf as its processor; organizations can request a data processing agreement at legal@kennu.io.

2. Data we collect

2.1 Account data. Your email address. Kennu has no passwords: you sign in with one-time links sent to your email.

2.2 Profile. Name, role, short intro, optional photo, contact details (email, phone, LinkedIn, website) and preferred language, as you enter them. You can change or remove them at any time.

2.3 Organization and content. Organization name and website, departments, members and their roles, and content modules (text and attachments; PDF and images only).

2.4 Meetings. Title, time, duration, purpose, attendees, the content shared, and whether each attendee has opened the briefing (so organizers know who is prepared).

2.5 People invited to a meeting. When an organizer invites you, they provide your name and email address. Until you open the briefing, we store only these for that meeting and use them to send you the invitation. Adding your address never reveals to the organizer whether you already use Kennu; your profile is shared only once you open the briefing yourself.

2.6 Access requests. If you open a meeting link not addressed to you and ask for access, the organizer sees your name, email and optional note.

2.7 Security and audit log. We record important actions (for example sign-ins, profile and content changes, invitations, and denied access attempts) with time and the account involved, so organizations and you can see who did what. For sign-ins and denied access attempts we also store the IP address and browser (user agent). For each signed-in device we store an approximate location (city and country) so you can recognize your devices.

2.8 Usage statistics. Cloudflare Web Analytics counts page views without cookies and without identifying you. We do not use session recordings, heatmaps or per-person click tracking.

2.9 Payment data. Kennu is in early access and free of charge; we collect no payment data. Before any paid plan starts, we will update this policy and name the payment provider.

3. How we use your data

PurposeDataLegal basis (GDPR)
Providing Kennu: profiles, organizations, content, meetings, briefings2.1–2.4, 2.6Contract (Art. 6(1)(b))
Inviting people to meetings2.5Legitimate interests of the organizer and us in preparing the meeting (Art. 6(1)(f))
Transactional emails: sign-in links, invitations, meeting notices, updates you opted in to2.1, 2.5Contract (Art. 6(1)(b))
Security, audit log, abuse prevention, bug fixes2.7Legitimate interests (Art. 6(1)(f))
Aggregate usage statistics2.8Legitimate interests (Art. 6(1)(f))
Legal complianceas requiredLegal obligation (Art. 6(1)(c))

3.1 Emails. Transactional emails are sent as part of the service. Update emails contain real changes only, at most one digest per day, and you can turn them off. We send no marketing emails without your opt-in consent.

4. Third-party service providers

  • Supabase: database and authentication. Stored in a U.S. region.
  • Cloudflare: hosting and delivery (Workers), file storage (R2), anonymous web statistics.
  • Resend: sending emails. United States.

All act as processors on our behalf under data processing agreements.

5. Data retention

  • Active accounts: while the account is active.
  • Deleted accounts: deleting your account in Kennu (Profile → Delete account) is immediate and irreversible; requests sent by email are actioned within 30 days. Audit log entries are kept, with personal identifiers replaced by a pseudonym.
  • Invited people without an account: as long as the meeting exists.
  • Attachments: until they are removed or their content module is deleted.
  • Audit log: 24 months.
  • Sign-in sessions and device locations: until you sign out or the session expires.
  • Backups: encrypted backups may persist for up to 90 days after deletion.
  • Legal holds: longer where required by law.

6. Your rights

You have the right to access, correct, delete and export your data, to restrict or object to processing, and to withdraw consent. You can edit your profile and delete your account at any time in Kennu (Profile → Delete account). For a copy of your data, write to legal@kennu.io. Requests are free and non-discriminatory. If you are in the EEA or the UK, you may also lodge a complaint with your local data protection authority.

7. U.S. state privacy rights

California (CCPA/CPRA): you have the right to know, delete and correct your personal information. We do not sell personal information or share it for cross-context behavioral advertising. Requests: legal@kennu.io.

8. Children's privacy

Kennu is a service for professionals and is not directed to children under 16. We do not knowingly collect their data and delete it when we learn of it.

9. Data security

TLS in transit and encryption at rest; row-level security on every database table; files stored privately and served only after an access check; personal invite links are single-use and bound to an email address; secrets kept in server-side vaults; an append-only audit log; restricted access to production data. Report suspected security issues to support@kennu.io.

10. International data transfers

Concept & Code, LLC is based in the United States, and processing takes place there. For transfers of personal data from the EEA and the UK we rely on standard contractual clauses or other lawful transfer mechanisms.

11. Cookies and local storage

Essential cookies only: your sign-in session, your chosen language, your time zone (to show meeting times correctly) and, briefly, where to return after signing in. No third-party tracking or advertising cookies, so no cookie consent is required.

12. Changes to this policy

We signal material changes by updating the effective date and, where appropriate, by email. Continued use after changes take effect means you accept the updated policy.

13. Contact

Privacy and legal: legal@kennu.io · Support: support@kennu.io · Mail: Concept & Code, LLC (address on file with registered agent)