Product Architect Service Terms

Last updated: November 10, 2026 · Effective November 2, 2026

These Service Terms add to our Terms of Service for Product Architect (app.vektorforgeai.com), our product management Platform. They are part of the Agreement, and words such as Platform, Your Content, owner, editor, viewer, export, download, plan limits, AI features, external AI assistant and third-party services have the meanings in the Terms of Service. If these Service Terms conflict with the Terms of Service, these Service Terms control for Product Architect, as section 1 of the Terms of Service says. How we handle the information involved is described in our Privacy Policy.

1. Plans

Product Architect has a Free plan and the Pro and Team paid plans, billed as section 4 of the Terms of Service describes, and a Guided plan bought through an order form. The Plans and pricing page shows each plan’s limits, such as the number of products, AI actions, Deep Research runs, editors and viewers, change-alert channels, and whether the plan includes viewer downloads, clean exports, Jira and ClickUp pushes, and API access. Monthly allowances, such as AI actions and Deep Research runs, reset at the start of each calendar month (UTC). Exports made on the Free plan carry a small “Made with Product Architect” mark.

Add-on packs. On the Pro and Team plans you can buy one-time packs of extra AI actions or Deep Research runs, at the prices on the Plans and pricing page. Pack credits are used only after your plan’s monthly allowance is used up, the soonest-expiring first, and expire 12 months after purchase. Packs can’t be bought on the Free plan.

A shared product uses its owner’s plan: the owner’s editor seats, viewer limits and download settings apply to everyone the product is shared with.

You share a product by inviting people by email as an editor or a viewer. An invitation must be accepted before the product appears in that person’s account, and an invitation that isn’t answered expires after 30 days. Editors use the owner’s editor seats; on the Free plan, a product can be shared only with viewers, up to the number the Plans and pricing page shows. Owners are responsible for who they invite and for revoking access, as section 8 of the Terms of Service says.

3. Viewers, downloads and exports

What viewers can do. Viewers can see a product and comment on it, but not change it.
Downloads. A viewer can download or export a product only if the owner allows it and the owner’s plan includes viewer downloads. On the Free plan, viewers can only view.
Watermarks and records. Files a viewer downloads or exports show the viewer’s name, email address and the date. We record every export and download, and the owner can see who exported or downloaded what, and when.
Viewer access expires. A viewer’s access to a product expires when they haven’t opened it for 90 days. We email the owner a week before, and the owner can invite the viewer again.
No sharing outside Product Architect. Anyone a product is shared with may not copy, export, download or share its content outside Product Architect except as the owner allows.

4. AI features

Product Architect’s AI features include Arc, the AI coach; AI drafts and recommendations across your product documents; file import; feedback analysis of customer feedback you enter; and Market Research and Deep Research. Each use counts toward your plan’s AI actions or Deep Research runs, and daily AI usage caps apply. Our AI page describes these features and the information they use.

5. Third-party services and API access

Jira. On plans that include it, you can push requirements to Jira using your own Jira credentials.
ClickUp. On plans that include it, you can push requirements to a ClickUp List using your own ClickUp API token.
Slack and Microsoft Teams. On plans that include change alerts, you can send summaries of changes, including the names of the people who made them, to the channels you choose.
API keys and MCP. On plans that include API access, you can create API keys to read and update your products from your own software or to connect an external AI assistant through our Model Context Protocol (MCP) server. When you create a key you choose whether it is read-only or can also make changes, and how long it lasts (30, 90 or 365 days); it stops working on that date. Each key can reach only the products its owner can edit, is limited to 120 requests a minute, and can be revoked at any time in Settings; every change made with a key is recorded in the document’s history. Section 9 of the Terms of Service applies to every key.
Metric intake addresses. On plans that include API access, an owner or editor can turn on a private intake address for a metric, so their own software or an automation service such as Zapier or Make can send the metric’s readings to Product Architect. The address works like an API key: readings sent to it are saved as the person who set it up, it should be kept secret, and Section 9 of the Terms of Service applies to it as it does to keys. It accepts one reading per metric per day (a later one that day replaces it), is limited to 60 readings an hour, and stops working when it is replaced or turned off, when that person can no longer edit the product, or while their plan doesn’t include API access. Automation services you use to send readings are third-party services under their own terms.
Metrics from Stripe. On plans that include API access, an owner or editor can connect a product to their own Stripe account with a Stripe restricted key that has read-only access, so Product Architect can fill metrics such as monthly recurring revenue, subscription counts, net revenue and customer count. You confirm you’re allowed to share that Stripe account’s data with us for this purpose. We only read from Stripe, never change anything there, and save only the totals. Readings are saved as the person who connected; syncing pauses when Stripe refuses the key, when that person can no longer edit the product, or while their plan doesn’t include API access. Stripe is a third-party service under its own terms.

6. Feature suggestions and reports

Feature suggestions you post are visible to other Product Architect users so they can vote on them; your name and email are shown only to our staff. Section 10 of the Terms of Service covers how we may use them.
Report an incident. Use the “Report an incident” form for bugs and service incidents, and tick “Possible security issue” for a suspected Security Incident. Reports are visible only to you and our staff.

7. Deleting a product

The owner can delete a product at any time. Deleting it permanently removes it, with its documents, version history (including named versions and baselines), AI conversations and research, for everyone it is shared with. A deleted product cannot be restored, so export anything you want to keep first. Individual requirements, roadmap items, sprints and tasks can be brought back for 30 days after they are deleted, as our Privacy Policy describes. What happens to Your Content when an account is deleted is described in our Privacy Policy.