PublicViews

Unreviewed draft · not in force

A lawyer has not read this page.

This document was drafted in-house, against how the product is actually built, so that a lawyer has something specific to review. That review has not happened yet. It is not in force, it is not a contract, and nothing here binds you or us. It will change before launch. If you need something you can rely on today, write to help@publicviews.app and ask for it.

Drafted 20 August 2026 · never reviewed · never in force

Terms of service

What we provide, what you are responsible for when you publish somebody else's data, and what happens at the edges: a failed payment, a downgrade, a disconnect, an ending.

1. Who is agreeing to what

These terms would sit between PublicViews, operated by Dialed Technologies, and the person or organisation holding a PublicViews account. If you accept them on behalf of a company, you are saying you can bind that company.

They do not apply to a viewer: someone who opens a page a publisher sent them. A viewer has no account and no agreement with us. Their relationship is with whoever shared the link.

2. What the service is

PublicViews connects to an Attio workspace you control and publishes a chosen slice of it as a web page. You choose the source, the layout, which attributes are visible, which are editable, and who can open the link.

Four limits belong in the description rather than in a support article:

  • Pages are served from a cache, checked on a schedule. We check Attio at the interval your plan sets and every page shows when it last updated. Nothing here is event-driven, so a change in Attio reaches the page at the next check rather than immediately.
  • A viewer’s edit never reaches Attio on its own. It becomes a pending change you approve. There is no setting that skips this.
  • We are a publishing layer, not a system of record. Attio holds your records. We hold a cache and your configuration.
  • Some things on the pricing page are not built yet, including custom domains, billing itself, per-viewer row scoping and single sign-on. The roadmap says which is which, and we will not charge for something that does not exist.

3. Your account

Keep your credentials to yourself, tell us promptly if you think an account has been reached by somebody else, and make sure everyone you add to a workspace is someone you would trust with what that workspace publishes. You are responsible for what your account does.

4. Your data, and your authority to publish it

This is the clause that matters most on this product. You keep every right in the records you publish, and you grant us only the permission we need to run the service for you: to read them from Attio, cache them, render them on the pages you publish, and delete them when you say so.

You confirm you are allowed to publish what you publish. The people in a CRM did not usually put themselves there. Before you make a page public, you are the one who has to be satisfied that you have the right to show those records to that audience, that you have any consent or notice your own obligations require, and that no attribute on the page is one you are not permitted to disclose. We give you the tools to check, every attribute starts hidden, and the exposure preview shows you the real page. We cannot make the judgement for you.

For personal data inside those records, you are the controller and we are the processor. The data processing agreement sets out those terms.

5. What you may not do

  • Publish content that is unlawful, or personal data you have no right to disclose.
  • Use the service to send unsolicited bulk email, or to host phishing or malware.
  • Try to reach another customer’s data, another view’s records, or any part of the system your account is not entitled to. Testing your own account’s boundaries and telling us what you find is welcome; doing it to somebody else’s is not.
  • Scrape or bulk-download published pages other than your own.
  • Resell or white-label the service as your own product without a written agreement. Using it for your clients under your own branding is exactly what it is for and is not this.
  • Work around plan limits, rate limits, or the approval step on an edit.

If something you publish is unlawful, or is putting the service or other customers at risk, we may pause it. We will tell you what and why, and where there is a choice we will pause rather than delete.

6. Viewers

Viewers are never charged and there is no cap on how many you have, on any plan. There is a monthly page view guardrail per account, currently 10,000 on Free, 100,000 on Pro and 1,000,000 on Business. Crossing it starts a conversation and an email; it does not block your page. A published page failing in front of your client is the worst thing this product can do, and no margin is worth it.

7. Plans and payment

Plans and prices are on the pricing page. Paid plans are billed in advance, monthly or annually, and annual billing is priced at ten months. Prices exclude tax unless stated. Upgrades apply immediately and are prorated.

The free plan is not a trial. It does not expire, we do not ask for a card, and if it covers what you need you can stay on it.

Billing is not switched on yet. Until it is, nothing on this site charges anyone, and these payment terms describe how it will work rather than how it works.

8. Downgrades and failed payments

A failed payment gives you seven days with everything running, with a notice in the dashboard and emails along the way. After that, and on a voluntary downgrade, free-plan limits apply by these rules:

  • Views over the new limit are paused, never deleted. A paused view shows an unavailable page rather than an error, and resuming it is one click once you are back over the line.
  • The badge comes back.
  • New edits cannot be submitted, and edits already waiting for you are kept so you can still approve them.
  • A custom domain redirects to your publicviews.app link for 30 days, then stops. A client-facing link should not die the same day a card does.
  • Gates stay closed. An access mode your plan no longer covers becomes more restrictive, never open: a domain allowlist becomes a password prompt. We never open a page because a payment failed.
  • A view relying on per-viewer scoping is paused rather than served unscoped. It is the one downgrade that takes a page down, and it is deliberate.
  • Records above the new cap stop syncing; what is cached is not truncated.
  • Older analytics become unreadable rather than deleted for 90 days, so an upgrade restores them.

9. Ending it

You can cancel at any time and it takes effect at the end of the period you have paid for. You can delete your account whenever you like, and doing so deletes your cached records and your configuration. Attio keeps every original record either way, because we never held it.

We may end an account for a serious or repeated breach of section 5, or if we stop offering the service. If we stop offering it, we will give reasonable notice and will not keep charging for a period we cannot serve.

10. Intellectual property

We own the software, the site and the brand. You own your data, your configuration, your logo and your branding, and you allow us to display them on the pages you publish. Free views carry a small “Made with PublicViews” badge; every paid plan removes it.

If you send us an idea or a request, we may act on it without owing you anything for it. We will not quote you, name you or use your logo without your written permission.

11. Attio

PublicViews is independent. It is not affiliated with, endorsed by, or sponsored by Attio, and Attio is a trademark of its owner. We use their public API as any third-party developer does. Your agreement with Attio is yours, and if they change their API, their plans or their permissions model, that may change what this service can do.

12. Availability, warranties and liability

There is no service level agreement today. Nothing is measured and no uptime figure is published, which the status page says plainly. The service is provided as it is, without warranties beyond those the law does not let us exclude.

The limitation of liability, the indemnities, and the exclusions that would normally sit here have deliberately not been drafted. Writing a plausible-looking liability cap without a lawyer is how a company ends up with a clause that does not do what it appears to do. This section is one of the open items below.

13. Changes to these terms

We will update the date at the top when these change, and email account holders about a change that materially affects them. Continuing to use the service after that is how you accept it. If you do not, cancel.

14. What is still missing

  • Governing law and venue. Not chosen.
  • Limitation of liability, the cap, and the exclusions. Not drafted.
  • Indemnities in both directions. Not drafted.
  • Dispute resolution, and whether arbitration applies.
  • The exact legal entity name, company number and registered address.
  • Consumer-law carve-outs for whichever jurisdictions end up applying.
  • Tax handling, including VAT and sales tax, once billing is switched on.

Until a lawyer has completed those, this page describes how we intend to behave. It is not a contract and it is not in force.