Legal
Privacy Policy
Last updated: . Effective: .
This policy explains what personal information Photobooth Pricing collects when you use our website and app, why we collect it, who we share it with and the choices you have. We wrote it in plain language for photo booth owners and their teams.
1. Who we are
Photobooth Pricing (“we”, “us”) runs the pricing app at photoboothpricing.com. Photo booth businesses use it to work out their costs, build packages and set prices.
We handle personal information in line with Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA). We are responsible for the personal information we hold, and we have named a person to answer for our privacy practices. You can reach them at [email protected].
2. The short version
- We collect what we need to run your account, your studio and your team, and nothing for advertising.
- We do not sell personal information, and we do not use analytics or advertising trackers.
- Apps you connect, such as Claude, can only act on the one studio you choose, within your role’s permissions, and you can disconnect them at any time.
- Your package catalog is public only if you choose to publish it.
- Your data is stored with Google Cloud in the United States.
- You can ask to see, correct or delete your information by emailing [email protected].
3. What we collect and why
Account information
When you create an account we collect your name, email address and password. Your password is handled by Firebase Authentication, a Google service, which stores it in hashed form. We never see it. If you sign in with Google, we receive your name, email address and Google profile photo from your Google account.
We keep a profile for your account with your name, email address, profile photo link, the date you joined, the time you last signed in, and the studio, role and permissions you have. If you upload your own profile photo, we store that image.
Why: to create your account, sign you in, show who you are to your team and control what you can see and change.
Studio and team information
Each account works inside a studio. We store your studio’s name and logo, and a list of its team members with each person’s name, email address, role, permissions, invitation date, join date and the name of the person who invited them.
When a studio owner or admin invites someone, we store that person’s email address and send them an invitation email. If you invite someone, please only invite people you have a business reason to contact.
Why: to let studio owners build a team, give each person the right access and send the emails that make that work.
Your business data
This is the information you enter to price your packages: inventory items and their costs, markups, packages and their descriptions, booth setups, overhead costs, labor rates, event counts, currency settings and any images you upload. Most of it is business information, not personal information, but it can include personal details if you type them in, such as a staff member’s name in a note.
Why: this is the core of the service. We store it so the app can calculate your prices and show them to you and your team.
Change history
When a change is made to your studio through our API or a connected app, we record what changed (the value before and after), when it happened, and who made it: the account and its role, the API key, or the connected app.
Why: so changes made outside the app can be traced, and to help with support and security.
Technical information
- IP addresses. To stop any one source from overloading the service, our servers count recent requests per IP address (or per signed-in credential). These counts are held briefly in server memory and are not written to our database.
- Service logs. Google Cloud, which runs our servers, keeps technical logs of requests, which can include IP addresses and request times. We use them to keep the service running and secure.
- Browser storage. Firebase Authentication keeps you signed in using storage in your browser. The app also saves a few preferences there, such as the last section you had open. We do not use advertising or analytics cookies.
Emails we send
We send service emails only: email address verification and password reset emails (sent by Firebase Authentication), team invitations, and password reset links that a studio owner requests for a team member. We do not send marketing email.
4. How we use your information
We use personal information to:
- provide the app: sign-in, studios, teams, pricing calculations, published catalogs and, when you ask, AI-drafted package descriptions;
- send the service emails described above;
- keep the service secure, including limiting request rates and capping how many invitation emails an account can send each day;
- answer your questions and support requests; and
- meet our legal obligations.
We do not sell personal information, rent it, or use it for advertising. If we ever want to use it for a new purpose, we will ask for your consent first unless the law allows otherwise.
5. Connected apps and API keys
Connected apps, such as Claude
You can connect an AI assistant or other app to Photobooth Pricing, for example Claude through our Claude connector. This happens only with your consent:
- You sign in to Photobooth Pricing and approve the connection on our own consent page. The connected app never receives your password.
- Each connection is limited to the one studio you choose, and to what your role in that studio allows. A read-only connection cannot make changes.
- You can disconnect an app at any time under Connected apps in the app. Studio owners can see and disconnect every connection to their studio.
For each connection we store the app’s name and the web addresses it registered, your account, the studio, the permissions you granted, and when it was created and last used. The access codes we issue to the app are stored only as one-way hashes. Access tokens expire after one hour. A connection ends on its own after 30 days without use, and after 90 days at most, unless you reconnect.
When you use a connected app, the information it asks for, such as your packages, items, prices and settings, is sent to that app. What the app’s provider then does with it is governed by that provider’s own privacy policy and terms, not this one. For Claude, that is Anthropic. Please review the provider’s policy before you connect.
API keys
Studio owners and admins can create API keys to connect their own tools. For each key we store its name, the studio, the permissions it has, when it was created and when it was last used. The key itself is stored only as a one-way hash, so we cannot show it again after it is created.
6. Your published catalog
You can choose to publish your package catalog so your own website can show it. When you publish, the following becomes public at a web address anyone can read: your studio name, package names, client-facing descriptions, booth types, tiers, durations, prices, currency, package images and the names of included items.
The catalog never includes your costs, markups, margins, private notes, overhead, settings or team information. You can unpublish at any time, which removes the public copy.
If you add a deploy hook (a web address from a website host such as Vercel), we store it and call it when your catalog changes so your site can rebuild. We treat these addresses as secrets and only ever show their host name and last four characters.
7. Who we share information with
We share personal information only with service providers that help us run Photobooth Pricing, and only what they need to do that work:
- Google (Firebase and Google Cloud) hosts the website and app and provides sign-in, our database, file storage, server functions, and the verification and password reset emails sent by Firebase Authentication. Google sign-in is optional.
- EmailLabs, our email delivery provider, sends team invitations and owner-requested password reset links. It is based in Poland, in the European Union. It receives the recipient’s email address and the email’s content.
- Anthropic writes draft client descriptions when you use Auto-generate on a package. It receives your studio name, the audience you pick, and that package’s name, booth type, tier, duration, booth setup (its name, client-facing includes, staff roles, photo sharing, delivery, branding and included travel), included items with their categories, quantities and notes, and the package’s internal notes. If any of this text contains personal details, such as a staff member’s name, it is sent too. It does not receive your costs, prices, markups or account details. Anthropic is based in the United States.
- Fontshare serves the fonts on our pages, and SVG Repo serves the Google logo on our sign-in buttons. Your browser loads these directly, which shares your IP address and basic browser information with them.
We also share information when you direct us to, such as with a connected app you approve or a deploy hook you add, and when the law requires it, such as in response to a valid court order.
8. Where your information is stored
Our database, file storage and servers are run by Google Cloud in the United States. This means your information is stored and processed outside Canada, and it may be accessible to courts, law enforcement and national security authorities in the United States under US law. Our email provider processes information in Poland, in the European Union. Anthropic, which writes Auto-generate descriptions, processes information in the United States. The connected apps you choose may also process information outside Canada.
9. How long we keep it
- Account, studio and business data: for as long as your account or studio exists.
- Deleting your account: the Delete Account option in the app deletes your sign-in, your profile and your profile photo, and removes you from studios you belong to. For each studio you own that has other members, you choose to make one of them the owner or to delete the studio. Studios you delete, and studios with no other members, are deleted with their data, uploaded files, published catalog, API keys and connected app access. We email the studio’s members about either change. Deletion is immediate and can’t be undone.
- Change history: for as long as the studio exists.
- Connected app records: one-time sign-in codes expire after 60 seconds, unfinished connection requests after one hour, access tokens after one hour and connections after 30 days without use (90 days at most). Expired records are deleted automatically.
- Invitation email limits: to enforce the daily cap on invitation emails, we keep counters keyed by a one-way hash of the sender and recipient. They are deleted automatically after the 24-hour window ends.
- Rate limiting: request counts by IP address are kept only in server memory, for the length of the limit window.
We may keep information longer if the law requires it or to resolve a dispute.
10. Your rights under PIPEDA
Under PIPEDA you have the right to:
- Access the personal information we hold about you;
- Correct it if it is inaccurate or incomplete (you can change most of it yourself in the app);
- Withdraw your consent, subject to legal or contract limits. Some information is needed to provide the service, so withdrawing consent may mean you can no longer use it;
- Ask us to delete your personal information; and
- Complain to us, and to the Office of the Privacy Commissioner of Canada if you are not satisfied with our answer.
To make a request, email [email protected]. We may need to confirm your identity first. We will respond within 30 days, as the law requires.
If you are a team member, the studio owner controls the studio’s data. We may need to work with the owner to handle a request about information stored in their studio.
11. How we protect your information
- Information is encrypted in transit: our site, app and API are served over HTTPS, and our invitation emails are sent to our email provider over an encrypted connection. Google Cloud also encrypts stored data by default.
- Database and file storage rules limit access to members of each studio, according to their role and permissions.
- Passwords are handled by Firebase Authentication. Connected app tokens and API keys are stored only as one-way hashes, and deploy hook addresses are treated as secrets.
- Changes made through the API and connected apps are recorded in a change history.
- Request rate limits and a daily cap on invitation emails help prevent abuse.
No system is perfectly secure. If a breach of security safeguards involving your personal information creates a real risk of significant harm, we will notify you and the Office of the Privacy Commissioner of Canada as the law requires.
12. Age requirement
Photobooth Pricing is a business tool for people who are 18 or older. It is not meant for children, and we do not knowingly collect personal information from anyone under 18. If you believe a minor has given us personal information, contact us and we will delete it.
13. Changes to this policy
We may update this policy as the service changes. We will post the new version here and change the “Last updated” date. If we make a significant change, we will let account holders know by email or in the app.
14. Contact us
For privacy questions, requests to access, correct or delete your information, or complaints, email [email protected].
See also our Terms of Service.