BoardFlow Beta Plan Limits
beta-plan-limits-v1 · 2 October 2026. This dated schedule supplements the accepted Beta Terms only after it is made available and your acceptance is recorded. It does not change earlier acceptance records or the Project Data Agreement.
1. Owned projects
Each account may own up to three projects. Co-owned projects count toward each owner's limit. Projects joined only as a collaborator do not count. Archiving a project does not release an ownership slot. Ownership changes are subject to the receiving owner's applicable allowance.
2. Stored images
Each account has 50 MB of stored-image capacity across its owned projects combined, not per project. One MB means 1,000,000 bytes. All stored project images count, including unused gallery and wardrobe/reference images. Images uploaded by collaborators count toward the owning accounts' allowances. The same file counts once for each owning account, not once for each shot that references it.
New beta uploads are automatically resized and compressed for preview, with a maximum longest edge of 720 pixels and a maximum stored size of 256 KiB (262,144 bytes). The app normally aims for a smaller file. Keep original-resolution files separately: downloadable images are the versions stored by BoardFlow, not a promise to preserve originals. Existing stored images are not silently recompressed.
This allowance concerns stored image files, not an unlimited allocation of database history, download traffic or recovery backups. Applicable service-security and misuse restrictions remain governed by the Beta Terms; this is not permission to disregard data-return, deletion or mandatory legal duties.
3. Reaching an allowance
At the applicable limit, additional project creation, ownership acquisition or image uploads may be blocked. Reaching a limit does not itself trigger a charge or deletion. Existing viewing, export and deletion remain available subject to project permissions, beta expiry and lawful security restrictions. Removing an unused stored image releases its live-file usage; detaching it from a shot alone does not.
Existing projects and stored images are preserved when this schedule is introduced. Acceptance does not delete existing excess content. Further additions remain restricted while an applicable allowance is exceeded. Previously recorded longer beta grants are not shortened.
4. Free beta and future plans
The current private beta is free, not a promise of a permanent free tier. Initial access remains 180 days from the recorded original beta start, with one 90-day extension after qualifying feedback under the Beta Terms. This schedule does not restart that period or create another extension.
Paid plans may be introduced separately. Their prices, applicable taxes, allowances, billing periods and cancellation conditions will be disclosed before purchase. Your beta does not automatically become a paid subscription; charging requires your express agreement. No future price or higher-resolution entitlement is promised by this schedule.
5. Changes and document priority
Your applicable limits are recorded in this dated version. Publishing a different pricing or limits page does not by itself change your accepted allowance. Material contractual changes follow the notice and recorded-acceptance process in the applicable Beta Terms. A declined change does not remove existing return or deletion obligations.
The Project Data Agreement prevails over conflicting processing provisions. Mandatory rights remain unaffected. This schedule sets plan allowances only; it does not replace the Beta Terms, Privacy Notice or Project Data Agreement.