Trust and reference
Privacy policy starter
Copy-paste clauses that accurately describe a Vaulter-built app's data handling, ready to adapt for your own app.
Your app collects data, so it should tell its users what and why. Vaulter's own privacy page explains what the platform does; this page helps you write the part that is yours. Below is a starter set of clauses that describe, accurately, how a Vaulter-built app handles data. Copy what applies, fill the brackets, delete what does not.
How to use it
Ask the agent to add the page and paste your assembled text:
Add a privacy policy page at /privacy, linked from the footer, with this text: ...
Keep it honest by construction: only include clauses for things your app actually does, and update the page when the app changes.
The clauses
Who we are and what we collect
[App name] is operated by [your name or company, contact email]. When you
create an account we collect your email address, which we use to sign you
in and to contact you about your account. Depending on how you use the
app, we also store the information you enter into it, such as
[bookings you make / documents you upload / orders you place].
The sign-in identity
Include this one; it describes a real property of every Vaulter app with sign-in:
Sign-in for this app is provided by Vaulter (vaulter.run), the platform
it is built on. If you use other Vaulter-built apps with the same email
address, you have a single sign-in identity across them; the data you
create in each app remains separate and is only available to that app.
Analytics
For apps on a paid plan (Free apps collect no analytics and can skip it):
We collect basic, first-party visitor analytics: which pages are visited
and approximate visitor counts. This data is collected by the platform
the app runs on, is shown only to us, and is not shared with advertising
networks.
Payments
If you take payments through Stripe:
Payments are processed by Stripe. Your card details are entered on and
handled by Stripe's systems and never touch ours; we receive
confirmation of payment and the billing details needed for receipts.
Stripe's privacy policy applies to the payment itself.
If your app sends email beyond sign-in codes:
We send transactional email related to your use of the app, such as
[booking confirmations / receipts]. We do not sell or share your email
address for marketing by others.
Other connected services
One honest sentence per service your app uses, in the same shape:
[Feature] is provided through [service name]; the data involved is
[what is sent], and [service name]'s privacy policy applies to their
processing of it.
Your rights
You can ask us for a copy of the data we hold about you, or ask us to
delete your account and data, by contacting [contact email]. We will
respond within [30] days.
When such a request arrives, the data-request section of the privacy page is your playbook for actually fulfilling it.
Frequently asked
Do I legally need a privacy policy?
If your app collects any personal data (an email address counts) and serves people in the EU, UK, California, and many other places, some disclosure duty almost certainly applies. A short, truthful page is cheap insurance either way; users trust apps that state their terms.
Should I mention Vaulter by name?
Yes, in the sign-in clause, because the shared identity is a property your users can observe. Elsewhere "the platform the app runs on" is fine.