How can we help?

An email address. Sign up, create a workspace, and paste in a transcript or your rough notes. There's nothing to install and no bot to add to your calendar.

A workspace holds a set of meetings and everything they produce — summaries, decisions, action items, files and comments. Most teams use one per team or per client, so the context stays together and permissions can be set once.

No bot ever appears in your meeting. On every plan, including Free, you can record from your own browser — your microphone, or a tab's audio plus your microphone — behind a consent step, and Scripta transcribes it. You can also bring a transcript or notes from whatever you already use.

Any recorder you already use will export one — Zoom, Google Meet, Teams, Otter and Fireflies all do. Your own rough notes also work; the summary is less complete, but decisions and action items still come through.

Good enough to review, not to trust blindly. Every item is shown next to the part of the conversation it came from, so a ten-second check confirms it. Everything is editable — you can reword, reassign or delete anything.

Yes. The generated version is a starting point, not a locked record. Edits are yours and won't be overwritten by a re-run.

The interface is English only today. Transcript handling depends on the underlying model rather than a fixed list, so other languages may work but aren't something we currently claim support for.

A decision records what was agreed and why, so nobody relitigates it later. An action item is work with an owner and a due date. Most meetings produce both, and they behave differently — one is a record, one moves.

You can record an email address as the assignee whether or not that person has a Scripta account. They'll only see the workspace if you invite them to it.

Record the new decision rather than editing the old one. Keeping the superseded version and its reasoning is what makes the log useful — a record where reversals have been tidied away teaches a new joiner nothing.

A place to file decisions and their work across the meetings that touched them. A project has a name and a summary, optionally an owner, a due date, a priority and milestones, and shows a health chip worked out from its own rows — at risk, stale, nothing linked yet, or on track. There is deliberately no status dropdown and no progress percentage: the chip is computed, and a percentage would be a number nobody could stand behind.

The things that need a person: decisions that are drifting, stale or have no owner; recordings that failed; projects at risk or gone quiet; and, on two further tabs, what extraction or the Scripta AI Agent has proposed but nobody has filed. Every item is worked out fresh from the record on each load, so it leaves on its own once the underlying thing is fixed. Accept files a proposal through exactly the same action you would use by hand; Dismiss is the only other write.

From your meetings. People lists your team (accounts with a role, with the profile fields they chose to fill in) and Contacts (everyone else who was in a meeting, by email address). Companies are derived from participants' email domains — a domain, its people, the meetings they were in and what those meetings decided. Free-mail domains and your own team's domain are left out, and nothing here is typed in by anyone.

Yes. When you upload a PDF, Word, PowerPoint or text file, Scripta reads its text and stores it beside the file, so the search box finds documents by what they say and shows the matching passage. Search covers projects, tasks, meetings, decisions and documents; it does not search raw transcripts. An editor can also ask Scripta to check a document against the meetings that came after it and report what has since changed — findings only, nothing is altered.

Yes. Invite them as a guest and choose their level: view only, comment, or full edit. Guests see only the workspaces you invite them to.

Viewers read. Commenters read and comment. Editors change meetings, decisions, action items and files. Admins additionally manage members. Access is enforced in the database itself, not just in the interface.

There is an unlisted one, on paid plans. A meeting's minutes can be sent as a link protected by a passcode (or, if you choose, link-only or Scripta-users-only), the reader needs no account, and you can see whether it was opened, regenerate the passcode, or disable the link at any time. It is unlisted rather than public — never indexed by search engines — and the Free plan can read everything inside the workspace but cannot publish a link.

Only people you've added to that workspace. Every table enforces row-level access rules in the database, so a request for a workspace you're not a member of returns nothing rather than relying on the interface to hide it.

No. Your meeting content is not used to train models.

Not individually yet. You can remove files, tasks, decisions, comments, milestones and recordings one at a time, and cancel a meeting. Deleting your whole account (Settings → Data) removes the workspaces you own and everything in them — unless colleagues are still members of one, in which case the deletion is refused rather than destroying their work.

No. Scripta is early and we won't claim a certification we don't hold. Content is encrypted in transit and at rest, and access is controlled per workspace — that's the honest current state.

Yes, with no card required. Meetings are unlimited; what the free plan meters is AI work — 2 AI write-ups a month and 225 minutes of browser recording (about five 45-minute meetings) — on one workspace for one person.

Nothing is taken away. You can keep creating meetings, typing notes, pasting transcripts and writing minutes by hand; only the AI write-up and recording are refused until the allowance renews, and the screen says so at the point you press. Upgrading lifts both allowances immediately.

From billing settings, at any time. Access continues to the end of the period you've already paid for.