Privacy Policy
Studio Makker LLC
Last updated: November 3, 2026
Introduction
Studio Makker LLC ("Studio Makker," "we," "us," or "our") operates the websites tryempress.dev and app.tryempress.dev (together, the "Site") and the Empress software-as-a-service platform (the "Service"). This Privacy Policy explains what information we collect, how we use it, and the choices you have.
Empress is a paid service for businesses in the United States and Canada (except Quebec). By accessing the Site or using the Service you agree to this Privacy Policy and to our Terms of Use . If your business has a plan, the Platform Terms also apply and control where they conflict with the Terms of Use. Our processing of personal information on behalf of a customer (its sites' content and its readers' data) is governed by our Data Processing Addendum , which is part of every customer's terms.
Our technology and how data flows
Empress is a multi-site operating layer: one application where a business operator can see, talk to, and operate across all of their websites. A workspace runs on one of two placements, and where data lives differs between them, so we state each plainly.
On a BYO workspace, the Service runs on the customer's own cloud account. When you connect Empress to your Cloudflare account, Empress provisions and operates your sites and their databases, storage, and supporting resources inside your own Cloudflare account under permissions you grant. The content, end-user records, and operational data for your sites are stored in cloud resources that belong to you, not in a central Studio Makker database. We hold only the information needed to run the orchestration layer and to bill you (described below).
On a pooled workspace, Studio Makker holds your sites' data on infrastructure it operates. Studio Makker provisions and operates your sites on Cloudflare capacity it owns. That means we hold, on our own Cloudflare account:
- your site content: pages, posts, media, settings and brand assets, in a database and object storage we provision for your workspace; and
- your readers' records: for each site, its readers' accounts (name, email address, whether the email is verified, and an optional profile image) and their sign-in sessions (a session token, its expiry, and, for security, the IP address and browser user agent the session was created from).
The data is the same as it would be on a BYO workspace; the difference is who runs the infrastructure it sits on. For your readers' data you are still the controller and we are your processor under the Data Processing Addendum. Because the infrastructure is ours, we can reach this data, and we do so only as operating and securing the Service requires: to run backups, to investigate abuse under the Acceptable Use Policy , to answer your support requests, and to suspend or tear down a workspace as the Platform Terms describe. Pooled workspaces share infrastructure and are kept apart logically, not by separate accounts.
We process customer data only to provide the Service. We do not sell customer data, we do not share it except as needed to provide the Service as described under "How we share information," and we do not use customer data to train artificial-intelligence or machine-learning models.
Information we collect
We keep collection to what the Service actually needs.
Signup information. When you sign up, we collect your email address, your company name if you give it, a tag for how you found us if you arrived from a campaign link, and a bot check run by Cloudflare Turnstile. We record that you accepted the Terms of Use and this policy: which version, when, and salted hashes of your IP address and browser user agent. Signup checks where you are; if you are outside the United States and Canada, or in Quebec, we keep only the email address you give us for our waitlist, and you can ask us to remove it at any time.
Operator account information. Empress uses passkeys rather than passwords. When an operator registers, we collect their name and email address, and we store the public-key credential created by their passkey. We do not collect or store passwords.
Billing information. When a member of a customer's workspace sets up payment, we collect the billing contact's name and email address, the company name, the billing address, and a tax registration number if the customer gives one. Payment details are entered into a form served by our payment processor, Stripe, and go directly to Stripe. We receive and keep only a reference to the payment method, its type, the card brand and last four digits or the bank name and last four digits of the account, the expiry date, and the status of each payment. We never receive or store full card numbers, card security codes, or full bank account numbers.
Bank account verification. When a customer pays by bank account, Stripe may verify the account through Stripe Financial Connections, which may ask the person to sign in to their bank through Stripe. Stripe receives the account and routing numbers and the data needed to verify the account, under its own terms and privacy policy. We receive only the reference and the last four digits.
Payment and invoice records. We keep a record of each invoice we issue (period, lines, total, status, date paid), each consent to automatic renewal (who gave it, when, the terms and disclosure version shown, the price shown, and salted hashes of the IP address and browser user agent), each billing notice we send, and any payment dispute.
Services invoices. Fees for paid custom work under a separate Build and Services Agreement are invoiced through Stripe, like plan fees, and kept with the payment and invoice records above.
Connected cloud-account information. When you connect your Cloudflare account, we receive, through Cloudflare's OAuth authorization, your account and membership details and the scoped permissions needed to provision and operate Workers, databases (D1), storage (R2), and key-value namespaces on your behalf, and read-only access to your account's analytics so we can show you your sites' traffic. We use these to run your sites and for no other purpose. Analytics about your sites' visitors are customer data we process for you under the Data Processing Addendum.
Content and instructions you provide. This includes the messages you send to the Empress assistant, the instructions agents send through the Empress connector, the brand and content settings you configure, and the site content you create or edit through the Service.
Waitlist and contact information. If you join the waitlist or contact us, we collect the email address (and any message) you provide.
End-user data on your sites. Sites you run through Empress may collect information from their own visitors and readers (for example, an email address used for reader sign-in via passkey, magic link, or an optional Google sign-in you enable, and the form submissions your sites receive). For that data, you are the controller and we act as your processor under the Data Processing Addendum, on either placement.
Automatically collected operational data. We log technical and security information such as IP address, timestamps, request and error logs, and basic device or browser information. We use this to keep the Service secure, debug problems, and prevent abuse.
We do not knowingly collect special categories of data or biometric identifiers, and we do not collect more personal information than is described here.
Cookies
The Site and the console use only the cookies they need to work: a session cookie that keeps you signed in, and a cookie that remembers which console your email address belongs to so the front door can take you there. We do not use advertising cookies, tracking pixels, or third-party analytics on the Site or in the console.
How we use information
We use the information above to:
- provide, operate, and maintain the Service and the sites you run through it;
- authenticate operators and protect accounts;
- provision and operate resources in your connected cloud account, or on our own infrastructure for a pooled workspace, at your direction;
- calculate and issue invoices, collect payment, and send receipts, renewal disclosures, renewal reminders, and notices about price changes and unpaid invoices;
- respond to billing questions and payment disputes, and prevent payment fraud;
- communicate with you about your account, including service and security notices;
- maintain the security of the Service, prevent abuse, and debug errors; and
- comply with tax, accounting and other legal obligations, and respond to lawful requests.
We do not use customer data for advertising, to build marketing profiles, or to train AI models.
How we share information
We do not sell, rent, or trade personal information. We share information only in these ways:
- Service providers (sub-processors). Vendors that host and run the Service may process data only to provide services to us and must keep it confidential. They are listed on our sub-processor page , which applies to both placements. We update that page before adding or replacing a sub-processor and give customers notice as the Data Processing Addendum describes.
- Payment processing. Stripe, Inc. processes payments, saves payment methods, verifies bank accounts and issues invoices on our behalf. Stripe also uses some of this information for its own purposes, such as fraud prevention and its legal obligations, as described in Stripe's privacy policy .
- At your direction. Where the Service connects to a third party you choose to enable, data flows to that third party according to your configuration and their terms.
- Legal and safety. We may disclose information if required by law or legal process, or where we believe in good faith it is necessary to protect the rights, property, or safety of Studio Makker, our users, or the public.
- Business transfer. If Studio Makker is involved in a merger, acquisition, or sale of assets, information may be transferred under the same commitments described in this policy.
AI features
The Empress assistant runs on a model that Cloudflare runs on its own infrastructure (Workers AI), through Cloudflare's AI Gateway. The prompts, context and tool results in a conversation go to Cloudflare to generate a response, and to no one else; they are never sent to the company that trained the model. AI Gateway keeps a log of each request, which records what the assistant was asked; we treat it as an operational log and keep it for 30 days. We do not use prompts, outputs, or any customer content to train models. Cloudflare's published terms for Workers AI state that it does not use inputs or outputs to train models.
If we ever move AI processing to a provider other than Cloudflare, we list it on the sub-processor page and give 30 days' notice before using it with customer data.
Taking your data with you
A workspace owner can start a full export at any time, from the console or through the Empress connector. We deliver it within 5 business days of the request, as a download link that expires 7 days after we send it, and an owner can ask for a fresh export at any time while the workspace exists (Platform Terms §8.6). It contains:
- the workspace: members and their roles, settings, sites, analytics, form submissions, and billing history; and
- every site: its theme source, its database as SQL, every stored file and object, every key-value entry, and its engine version and settings;
with a manifest of what is included and instructions for restoring it. An export never contains secrets, access tokens, or password or passkey material.
Data security
We maintain reasonable administrative, technical, and physical safeguards, including:
- Encryption in transit and at rest. All traffic uses HTTPS/TLS, and data stored in our cloud provider's databases and object storage is encrypted at rest by the provider.
- Phishing-resistant authentication. Operator access uses passkeys (WebAuthn) rather than passwords.
- Payment card data. Card and bank details are entered into Stripe's own form on our pages and go directly to Stripe, so they never reach our servers and we do not store, process, or transmit full card numbers.
- Least-privilege access. Access to systems and data is limited to what is needed to operate the Service, and privileged actions are logged.
- Tenant isolation. On a BYO workspace, each customer's sites and data run in that customer's own cloud account. On a pooled workspace, customers share our infrastructure and are kept apart logically rather than by separate accounts.
No system is perfectly secure, but we work to protect your information and to respond quickly if something goes wrong.
Data breach notification
If we become aware of a security incident affecting personal information, we will promptly investigate, take steps to contain and remediate it, and notify affected individuals and customers, and regulators where required, without unreasonable delay and in the manner required by applicable law. For data we process for a customer, the Data Processing Addendum sets how quickly we tell the customer.
Data retention
We retain personal information only as long as needed for the purposes described here or as required by law.
- Operator and member accounts: members' names, email addresses and roles are kept for the life of the workspace and deleted when it is torn down.
- Logs: server, application and AI logs, including AI Gateway request logs (which record what the assistant was asked), are kept for 30 days.
- On a BYO workspace, content and end-user data in your connected cloud account are retained according to your own configuration.
- On a pooled workspace, content and reader data are kept for the life of the workspace. When a plan ends, the console turns read-only and you can still take a full export; teardown then deletes them on the timeline the Platform Terms §5 and §8 set. A pooled workspace whose plan never became active (a signup that never finished) may also be torn down for inactivity, after notice, as the Platform Terms §22 describe; a paid or waived plan is never removed for inactivity. Copies in backups are deleted when those backups expire on their normal cycle.
We keep payment, invoice, consent and notice records for seven years after the end of the year they relate to, to meet tax and accounting obligations and to defend payment disputes and contract claims. They are the only records we keep after a workspace is torn down. We never keep card or bank numbers. Stripe keeps its own records under its own retention policy.
Your rights and choices
Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of your personal information, and to opt out of certain uses.
Data on your sites. For content and reader data on your sites, you are the controller, and the Service lets you export, correct and delete it directly; a full export is described above. Your readers should contact you first. If a reader writes to us, we pass the request to you and act on it only on your instruction, or where the law requires us to respond directly, as the Data Processing Addendum §7.1 describes.
Data we hold as controller. For your operator-account, signup and billing data, contact privacy@tryempress.dev or write to us at the address below. We will confirm we received your request, verify your identity using information we already hold, usually by asking you to confirm from the email address on the account (and we may ask for more where the request touches sensitive information), and answer within 45 days; if we need longer, we will tell you why within that time and answer within 45 more. You may use an authorized agent if you give them signed permission and confirm your identity with us. If we decline a request, we will say why, and you may ask us to reconsider by replying within 45 days; a different review of the decision follows.
We may decline a deletion request only where the law allows: for example, where we must keep information to complete a transaction you requested, detect or prevent security incidents or fraud, fix errors, or comply with a legal obligation such as keeping tax records.
We will not treat you differently for exercising any of these rights.
Marketing email. We send promotional email only where we have your consent or the law otherwise allows it, including Canada's anti-spam law where it applies. You can opt out at any time using the unsubscribe link. We will still send service, security and billing messages about your account.
California residents
In the past twelve months we have collected these categories of personal information, from you, from your use of the Service, and from Stripe and Cloudflare: identifiers (name, email address, IP address, account and session identifiers); commercial information (plan, invoices, payments); internet activity (request and error logs); and account sign-in credentials (passkey public keys). We use them for the purposes in "How we use information" and keep them for the periods in "Data retention." We use sign-in credentials only to sign you in and protect your account. We do not sell or share personal information, as the CCPA defines those terms, and we have not done so in the past twelve months.
Canada
We do not accept customers in Quebec until French versions of our terms exist, and signup refuses a Quebec address. If you are elsewhere in Canada, we collect, use and disclose your personal information with your consent and as Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) and applicable provincial law allow. You may access and correct your information, and withdraw consent subject to legal and contractual limits, by contacting us below. Your information is processed in the United States and on Cloudflare's global network, which may process it in other countries; wherever it is, it may be accessible to authorities under that country's law. We remain responsible for it.
Other places
Residents of other U.S. states with consumer privacy laws, including Nevada, may contact us using the details below; we will honor the rights those laws give you. We do not sell personal information.
Children
Empress is a business tool and is not directed to children. We do not knowingly collect personal information from children under 13 (or the equivalent age of digital consent in your jurisdiction). If you believe a child has provided us information, contact us and we will delete it.
Customers are responsible for complying with children's privacy laws, including COPPA, on their own sites. If you believe a child has given information through a customer's site, contact that site's operator; we will help the customer delete it.
International users
The Service is offered only to businesses in the United States and Canada (except Quebec), and signup turns away anyone else. We operate from the United States, and information we process is stored and processed in the United States and on Cloudflare's global network, where storage is not pinned to a region. We do not offer the Service in the European Economic Area, the United Kingdom or Switzerland. If that changes, we will put the required transfer safeguards in place first.
Changes to this policy
We may update this Privacy Policy from time to time. We post every version with its date. Changes to fees are governed by the Platform Terms, which control. When a change significantly affects how we use personal information, we notify you by email or in the Service before it takes effect, and where the law requires consent or an opt-out, we ask for it.
Contact us
Studio Makker LLC
882 Aileen St, Oakland, CA 94608
Email: privacy@tryempress.dev