Privacy Policy

What we collect

• Account data — your name, business, email, and login, so the platform works.
• Usage data — how the product is used, to keep it fast and fix problems. We use privacy-first analytics with no cross-site tracking and no advertising cookies, which is why this site has no consent wall.
• Payment metadata — Stripe processes all card payments. We never see or store your clients’ card numbers.

Your clients’ data

When your clients book, view galleries, or pay, that data belongs to you. You are the controller; we are a processor acting on your instructions. We use it only to operate the service for you. We do not market to your clients. We do not sell their data. We do not use your client list to sell anything to anyone. That is the Independence Pledge, stated as policy.

Subprocessors — the whole list

These are every third party that can hold or process data from the platform. Each acts on our instructions and under contract with us. If we add one, this list changes with it.

• Google Cloud / Firebase — hosting, authentication, database and file storage. United States.
• Stripe — payments and subscription billing. Card numbers go to Stripe directly and never touch our servers.
• Resend — delivery of the transactional email your studio sends.
• Mux — storage, encoding and streaming of video: tours, reels, and any video delivered through a gallery or property page.
• Cloudflare — DNS and content delivery for custom domains and public property pages.
• Google Maps — address autocomplete, map previews and travel-distance checks.
• Google Analytics for Firebase — aggregate product-usage measurement inside the app.
• Plausible — cookie-free analytics on this marketing site only. It never sees app or client data.

Not used, and therefore not listed: SMS/text messaging, and AI image or content services. Those integrations are not provisioned, so no data reaches them. We don’t sell data to anyone, and there are no advertising networks in the product.

Calendar providers depend on what a studio chooses to do. Everyframe publishes a private schedule feed a studio can subscribe to from their own calendar app; if they do, whoever runs that calendar — Google, Apple or Microsoft — fetches and stores those shoot entries, which include the property address. Nothing reaches a calendar provider unless the studio sets that subscription up from their own account.

Need a signed Data Processing Addendum for a brokerage or franchise client? Write to us and we’ll put one in place.

Cookies

Essential cookies keep you signed in and keep the site secure. This marketing site’s analytics (Plausible) set no cookies at all, which is why there is no consent wall; inside the app, aggregate usage is measured with Google Analytics for Firebase. No advertising or cross-site tracking cookies anywhere.

Keeping it, and leaving with it

We retain data while your account is active. Here is exactly what leaving with it looks like today, rather than a promise we’d have to hedge later:

• Export. Clients, shoots, invoices, team and tax summaries export as CSV from the Console, and delivered media downloads from its gallery. There is no one-button archive of an entire workspace yet — ask and we’ll produce one for you.
• Deletion. Removing a client removes that client record. It does not by itself erase their past bookings, invoices, signed agreements or delivered media, which stay as your business records.
• Full erasure. For a workspace, or for one person across all of it, email us. We do this by hand today, so allow up to 30 days.
• Backups. We don’t offer point-in-time restore. Keep your own copies of anything you can’t lose.

Security

Each studio’s data is isolated at the database layer and enforced by security rules. Payments are handled by Stripe, so card data never touches our servers. Branded email is sent from your own DKIM-verified domain. Read more on our security page.

Your rights & contact

You can ask us to access, correct, export or delete the personal data we hold about you, and depending on where you live you may have further rights — we honor them. Some of these we action by hand rather than with a button; see the section above for what that means in practice. Requests about a studio’s client belong with that studio, who is the controller; if one reaches us we pass it on and help them answer it. Reach us at hello@useeveryframe.com.

This page is the public summary. The operative policy is the one presented in the app when you create a studio account, and it is versioned there.