plugin.space / Flows

Flows by plugin.space

Terms of service

The conditions for using Flows and its optional account service.

Version 1.10 · 7 November 2026

Service provider and payments

Michał Drożdżyński
ul. Bojowa 10c, 44-193 Knurów, Polska
Polish tax identification number (NIP): 9691629431
michal@drozdzynski.pl

These terms cover Flows by plugin.space, provided by the operator identified above. New Pro subscriptions are sold through Link using Stripe Managed Payments. The Stripe entity identified at checkout acts as merchant of record and handles payment, applicable indirect taxes, invoices and transaction support under the terms shown at checkout. We remain responsible for providing Flows and for our service obligations.

What the service provides

Flows creates and presents portable flow documents with optional screenshots, source references, user-role definitions, draft test scenarios, use cases and quality-review suggestions. Local viewing requires a compatible local execution environment; the launcher reuses Node.js 22.13 or newer or downloads a verified runtime on first use, which may need internet access. Capture additionally requires a browser runtime and authorised access to the application being captured. You provide your own AI host account and any permissions it needs.

Optional cloud storage keeps snapshots and discussions for verified accounts. Owners can share selected saved flows with specific teammate email addresses or enable a view-only link that anyone holding it can open without signing in. Owners control that selection and can revoke invitations or disable link access. Cloud features are available only when the account service is configured. Local use does not require a cloud account.

Generated drafts, roles and exports

Mapped journeys and role definitions can include supplied requirements, observed behaviour, inferences and proposed designs. Review their source references, conditions and unresolved questions before relying on them. User types and permissions in a role audit describe the product being mapped; they do not grant access to Flows or establish that the product’s access controls are correct.

Test scenarios are draft instructions generated from the mapped routes and test hints. Coverage refers to that map, including any uncovered transitions and unreachable steps; it is not a guarantee of complete application coverage or a passing test result. Use cases and quality evaluations propose activities and criteria for review. Flows does not run the exported tests, conduct user research, score an experience or validate an AI output during generation.

Functional scenarios can be exported as JSON or Midscene Test YAML, and use cases and quality suggestions as JSON or Markdown. Role filters also apply to these exports. Review the selected scope, actions, assertions, prerequisites and safe test data before using an export. Running it in another tool is a separate action under that tool’s setup, permissions and terms, and may change the target application. Do not put credentials or real customer information in scenario instructions.

Your materials and permitted use

You retain ownership of your code, flow documents, screenshots, role evidence, test and research materials, and comments. You authorise us to store and process uploaded material only as necessary to provide, secure and support the service. Upload only material you may lawfully use and share. Do not upload secrets, restricted personal information, unlawful content or malicious files, or attempt to access other users’ data.

You may install and run the supplied Flows plugin for personal, internal business and authorised client work, and make backup copies. Rights in third-party components remain governed by their own licences. These terms do not grant ownership of our code or branding, or restrict rights mandatory law grants you. Sharing your own flow documents is allowed.

Accounts and connections

Keep your account access secure. Sign-in happens on the account website. A local Flows connection grants access to your permitted flows and discussions; it cannot create subscriptions or change billing. Connecting enables private cloud saving for opened and newly created flows, including captures and source references, according to your account plan. Automatic first saves and later updates run while the viewer or panel is active. Explicit per-flow opt-outs are preserved, and automatic updates can be disabled at any time. Sharing requires a separate choice. Local viewer connections expire within 24 hours. Assistant (MCP) connections last up to 30 days and read your permitted flows. A separate sharing authorisation lets owners manage the selected flows, grant or revoke email access, and enable or disable access for anyone with the link in the hosted panel. Including retained history for invited people is an additional choice. Hosted MCP cannot edit saved flow content, comment or delete flows; these actions remain available on the account website or through your trusted local Flows environment. Panel-only labels rely on your host enforcing them; they are not a guarantee against a compromised or untrusted host. The hosted service checks sharing permission, connected account and ownership. You can disconnect the current connection in the plugin and review or revoke individual or all local and assistant connections in your account settings. You remain responsible for actions you authorise and recipients you choose.

Optional paid service

Flows has two plans, Free and Pro. Pro is the optional paid plan and is ordered separately on the account website. Before an order is confirmed, its price, currency, recurring period and total payable are shown. Only an explicit purchase starts a paid subscription. Saving a card or connecting the plugin does not itself start one. We do not charge automatic usage overages.

The current Pro price is USD 5 per month, plus applicable taxes, renewing monthly until cancelled. Managed Payments calculates applicable taxes and may present the price in your local currency. The final currency and total are shown before you confirm the purchase. Changes to price or material conditions require advance notice and the rights required by applicable law.

You can request cancellation through michal@drozdzynski.pl or use the billing management controls on your account website. Link also provides subscription and transaction support for purchases sold through Link. If an automatic renewal payment is still being processed, access continues for up to 24 hours after the paid period and ends at once if that payment fails. Cancellation stops future renewals; access already paid for continues until the paid period ends unless a refund, statutory remedy or agreed closure requires otherwise. Current snapshots remain readable and exportable after paid access ends; further saves depend on your current entitlement.

Local library

Free local use includes 3 active flows across projects in the library on one computer, without an account, card or time limit. Pro removes the local flow count limit after connecting your account. Local and cloud slots are separate. Archive a local flow to free a slot; archiving preserves the local files, but the flow must be restored when there is room before opening or exporting it in Flows. When Pro access ends, up to 3 local flows stay active; the remaining local files are preserved, but their flows must be restored to an active slot before opening or exporting them in Flows. Nothing is automatically deleted. Confirmed local access can continue offline for up to 7 days, never beyond the paid period. Local sign-out clears cached access; remote revocation is applied on the next online check.

Fair use

Cloud storage, on Free and on Pro, is intended for ordinary creation, updates and collaboration. Storage, snapshot and discussion allowances below still apply. We use internal service safeguards, including controls on unusually large libraries and bursts of writes or invitations, to prevent spam, automated bulk generation and disruption. Exact detection thresholds are not published. If a safeguard is triggered, we may temporarily pause new creations or writes and explain the restriction. Existing reading, export, deletion, access revocation and cancellation remain available. Contact us if ordinary use is affected so we can review the restriction; a technical threshold alone does not establish abuse or authorise additional charges. Material changes to the purchased service require advance notice and the rights required by law.

Storage and availability

Free needs no payment card and includes 3 cloud flows, 32 MiB of active storage and no limit on invited viewers. Pro includes 256 MiB of storage and no limit on invited viewers; cloud activity is subject to fair use safeguards. Storage covers current and historical snapshots, screenshots and comments. Snapshots include supported source fields for role audits, test hints, user stories and quality-review hints. Generated scenario and suggestion lists are reconstructed from those fields when viewed or exported, rather than stored as duplicate cloud content. Pro records up to 20 previous versions per flow within this storage allowance. On a further changed save, the oldest previous version is removed. Owners with active Pro access can also permanently remove individual previous versions to free space. Identical saves do not add a version. Sharing covers the selected current snapshots and their future saved updates; newly created project flows are not automatically added to that shared selection. Anyone with an enabled public link can view those snapshots, their source and role/test materials, and their current captures without an account. Public links do not expose discussions or retained version history. Returning a project link to invited-only access prevents further anonymous use of the old public link. Review the selected flows and their contents before sharing. The owner must separately include history to grant access to retained earlier versions and screenshots while the owner has active Pro access. Revoking access does not retrieve copies a recipient already obtained. Each snapshot must be under 4 MiB (the exact request limit is 4,190,208 bytes); each flow supports up to 1,000 comments of 4,000 characters, with a 3 MiB discussion budget. MiB means 1,048,576 bytes. Storage is measured from the database JSON representation of snapshots and the JSON text of comment bodies and author names, plus 512 bytes per comment for metadata.

Recording, viewing, comparing and removing versions, including viewing historical captures, require the flow owner’s active Pro plan. After Pro access ends, history is locked; previous versions are retained and become accessible again when the owner renews Pro. Up to 3 selected flows remain active, and their retained previous versions count toward active Free storage. Other saved flows and discussions remain readable and exportable; they are not automatically deleted and do not count toward active Free storage. The entire retained library cannot grow beyond 256 MiB, even when the active selection changes. Existing collaborators retain read access; all invited viewers can comment on active flows, including on Free. The owner can remove existing grants. On Free, a new cloud flow requires the total saved-flow count to be below 3. On Pro, new cloud flows must fit the storage allowance and service safeguards. Updating an existing active flow does not consume another slot. Exceeding an allowance blocks the affected operation without automatic charges. An owner can delete a saved flow at any time; this removes its snapshot, screenshots, comments, sharing records and version history from active cloud storage and does not affect local files.

Availability can be interrupted by maintenance, faults or provider outages. Keep your own copies of important materials. We may restrict abuse or an immediate security threat proportionately and explain the restriction where lawful. These terms do not promise unlimited resources or permit undisclosed automatic charges.

Consumer rights, withdrawal and complaints

If you are a consumer entitled to withdraw from a distance service contract, you generally have 14 days from its conclusion. Send a clear statement to michal@drozdzynski.pl or the postal address above; a sample is available on the support page. We confirm receipt and handle refunds within the applicable legal deadlines. Simply using the service does not waive mandatory rights.

Where you expressly request service before the withdrawal period ends, any amount payable on withdrawal is limited to what applicable law permits. Consumers and other persons protected by mandatory law retain their rights concerning conformity, remedies and updates. Report a complaint to michal@drozdzynski.pl with the issue and requested outcome.

Privacy and closure

The privacy policy explains information handling and retention. Contact us to request account closure or a complete export. Flow JSON and scenario or research exports do not contain every screenshot, discussion or account record. Closure is handled separately from cancellation, including required accounting retention.

Security incidents

Report suspected unauthorised access or disclosure to michal@drozdzynski.pl promptly, without sending credentials or unnecessary sensitive content. We investigate and take appropriate containment and remedial measures. We notify affected controllers, people and authorities where and when applicable law requires, as explained in the privacy policy. Your choice to upload or share is not consent to unauthorised disclosure. Your duty to review your materials does not remove our own security, data-protection or liability obligations.

Responsibility and applicable law

Polish law applies without removing mandatory protections available under the law applicable to a consumer. Nothing here excludes liability or remedies that cannot lawfully be excluded, requires consumers to use a foreign court, or removes their right to seek help from a competent authority. We remain responsible for obligations imposed on us as the service provider.