Fair Use Policy

Some OcuMap plan features are described as unlimited. This policy explains what that means in practice, and the rare circumstances in which we would ask a customer to change how they use the platform.

It applies to the number of projects and Features in an account, Published Viewers, and guest participation through Guest Posting. It does not change your rights or obligations under our Terms of Service, which govern if the two ever conflict.

On paid plans, we do not cap the number of projects you create, the number of Features you add to them, or the number of Published Viewers you publish. We do not meter how many people open a Published Viewer, or how many comments, annotations, measurements, or other items guests post to one.

These are deliberately uncapped. Documentation is only valuable when the people who need it can reach it, and we do not want the cost of sharing a project to scale with the number of people who read it.

Unlimited refers to counts, not capacity. Storage and team member seats are explicit plan limits, described in Section 03 and shown on the pricing page.

Storage allowances and team member seats are hard limits attached to your plan. They are not subject to this policy and are not described as unlimited anywhere. You increase them by adding capacity or by changing plans.

The Free plan includes 5 GB of storage, one team member, and one active Published Viewer, and publishes public links only.

If your usage exceeds your plan

If you change to a plan whose limits are lower than your current usage, we do not delete your files and we do not remove your existing team members. Your account enters a 30-day grace period with a persistent Over Plan Limit notice, and we block only the entitlement you have exceeded — exceeding storage blocks new uploads, and exceeding seats blocks new invitations. Everything already in the account stays available.

We send reminders when the change takes effect, 7 days before the grace period ends, 1 day before, and on expiration. If the account is still over its limits after 30 days, it is marked Overdue and our team is notified so we can contact you. Existing data and team members are not automatically deleted or deactivated.

A Published Viewer is a curated, read-only presentation of Features that already exist in your project. It references that content rather than duplicating it, and it does not give anyone outside your team access to your private project workspace.

Guests who open a Published Viewer do not need an OcuMap account and never consume a team member seat. Paid plans include unlimited Published Viewers under this policy; the Free plan includes one active Published Viewer.

You stay in control of every viewer you publish. You decide what it contains, whether it is protected by a password (available on paid plans), when it expires, and whether downloads are allowed. Unpublishing disables the link immediately without deleting the viewer’s configuration, and republishing reuses the same address.

When you enable Allow Guest Posting on a Published Viewer, people you share it with can contribute without an OcuMap account — comments, annotations, points, lines, areas, and measurements. The first time someone posts, they are asked for a name and email address, which is remembered for that session.

Guest Posts never change authoritative project data on their own. Every submission enters your Guest Posts queue as Pending, and nothing becomes part of the project until an administrator on your team approves it. Approved geometry and measurements become normal Features in their original context; approved text remains a comment. You can delete a pending post, or turn Guest Posting off entirely, at any time.

Guest participation is not metered and does not consume seats. We apply rate limiting and automated abuse controls to protect the platform, and those controls are designed not to interfere with normal professional use.

Uncapped does not mean unrelated. The following fall outside fair use:

• Distributing content unrelated to documenting a physical project, site, building, facility, or infrastructure.
• Using Published Viewers primarily as general-purpose file hosting, a media library, or a content delivery network.
• Automated or scripted traffic, including automated Guest Posting, scraping, or load generation.
• Spreading one organization’s work across multiple Free accounts to avoid storage or seat limits.
• Any activity that violates our Terms of Service.

Our first step is always a conversation. If activity on an account falls outside this policy, we contact the account owner and work toward a reasonable resolution — usually a plan change, or an adjustment in how the platform is being used.

Where the issue is guest activity on a Published Viewer, the tools in your own account are the first remedy: delete the pending posts, disable Guest Posting, add a password, or unpublish the viewer.

We restrict or suspend an account only where activity threatens platform stability, security, or other customers’ service, or where we are required to act.

If you believe this policy has been applied to your account in error, contact us and we will review it. If you are approaching your plan’s limits and want to discuss capacity, our team can help you find the right plan.