Privacy policy

We handle account and studio information, such as names and email addresses, and the information photographers and their clients provide: inquiries, contact details, notes, events, photographs, contracts, signatures, questionnaire answers, invoices, and related activity. Shared links expose the content the photographer chooses to share, subject to the link's access settings. Anyone receiving a shared link may be able to access that content.

We also handle technical information needed to operate and protect the service, including request and error logs, session information, and local browser storage. Browser storage supports sign-in, saved preferences, and local workspace operation. Technical providers may process network information, such as IP addresses, when delivering the service.

When you sign in with Google, we receive a verified Google account identifier, email address, and basic profile information to identify your account and support sign-in. Regular Google sign-in does not request Gmail sending permission. When you choose Sign up with Google, we also ask for optional Gmail sending permission; you can skip it and still create your studio. You can also choose Connect Gmail in Settings or the email review dialog later. If you approve Gmail sending, we request only the gmail.send permission in addition to basic identity information. We do not request permission to read your inbox or delete your messages.

Gmail access is used to send messages you review and explicitly choose to send with Google. If you create and activate a workflow containing email steps, you also authorize RoselStudio to send those configured messages automatically when the workflow's conditions and timing are met. These messages can be sent by the server while the app is closed. The recipient, subject, and body are transmitted to Google for delivery. Connecting Google alone does not send an email or activate a workflow. Google acceptance of a message does not guarantee delivery to a recipient's inbox.

Google access and refresh tokens are encrypted on the server and stored separately from workspace exports. We retain connection information while it is connected, and retain send-attempt status, a content hash, and Google's message identifier to report outcomes and prevent accidental duplicate sends. The sending integration does not store an additional copy of the message body in its delivery receipt; content you save in your workspace remains part of that workspace.

We do not sell Google user data, use it for advertising, or use it to train artificial intelligence models. RoselStudio's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Human access to Google user data is limited to circumstances permitted by that policy, such as support with your consent, security investigations, or legal requirements.

We use information to provide the workflows you request, authenticate users, save studio records, deliver shared pages and photographs, process payment updates, prevent abuse, troubleshoot problems, and respond to support requests. We do not sell your personal information.

Service providers process information needed to deliver their services. These include Amazon Web Services for hosting, storage, and authentication; Google when you connect Google or send through Gmail; and Stripe for connected-photographer onboarding and online payments. Stripe handles payment credentials; RoselStudio handles invoice amounts, payment identifiers, statuses, and related history. These providers also have their own privacy policies. We may disclose information when required by law or needed to protect the service and its users.

We retain studio records to provide the service and preserve the workflows and history you save. You can manage saved records through the available app controls. For account deletion or other data requests, contact support@roselstudio.com from your account email. We may need to verify your identity and clarify which studio or records your request concerns. Some records may need to be retained for security, legal, or financial-record obligations, and backup copies may persist until replaced under the applicable backup process.

To disconnect Gmail, use Settings → Integrations & Google → Google & Gmail → Disconnect. We stop manual and automated Gmail sending and ask Google to revoke RoselStudio's permissions for that Google account. Because Google shares these permissions across studios, this also disconnects Gmail sending in other studios using the same Google account. You must reconnect and grant permission before sending again. A message already submitted to Google may still be delivered, and Google's permission removal may take time to appear.

If Google cannot confirm permission removal, sending stays stopped and we show a retry option. Encrypted credentials are retained only to retry revocation and removed after Google confirms it. You can also revoke access in your Google account's third-party connections. Disconnecting Gmail does not delete your studio, saved email drafts or history, previous messages in Gmail, or the linked Google identity used to sign in. Google may ask you to authorize sign-in again. We retain the linked email address, identity and delivery metadata as described above. Contact support to request removal of retained Google identity or delivery metadata.

Photographers choose the client information and photographs they upload and share. If you are a photographer's client and have a question about a gallery, agreement, questionnaire, or invoice, contact the photographer first. You can also contact us about RoselStudio's handling of your information. Photographers are responsible for having appropriate permission to upload and share their clients' information.

We use measures such as encrypted network connections, server-side access controls, and encrypted Google tokens to protect information. No service can guarantee absolute security. We may update this policy as the service changes; the effective date above identifies the current version.