Privacy Policy

1. Scope

This policy describes information handled through Solara Creator Suite's public pages, buyer accounts, seller workspaces, checkout, and support features. Sellers may separately collect and use customer information for their own business. Their practices and Stripe's payment processing are not governed solely by this policy.

2. Information provided by you and sellers

• Accounts: usernames, email addresses, password hashes, account status, notification choices, and any profile or contact details you provide.
• Seller applications and content: business descriptions, contact methods, selling platforms, application notes, menus, profile images, listings, announcements, tags, and promotion submissions or proof files.
• Commerce and business records: customer names and contact information, products, quantities, prices, payment status, order notes, delivery or tracking information, and service-subscription records. Sellers may enter customer records manually, even when the customer has no platform account.
• Community and support: follows, reviews and ratings, leaderboard participation, notifications, support tickets, seller feedback, and correspondence you submit.

Do not submit information you lack permission to share, or include sensitive documents, passwords, or full payment card details in notes, uploads, tickets, or feedback.

3. Technical and payment information

The app uses session cookies for sign-in and request protection. It stores certain interface choices, such as navigation and list filters, in your browser's local storage. Hosting and service providers may process request information, such as IP addresses, browser details, and diagnostic logs, when serving or protecting the site.

Stripe handles payment details through its payment interfaces. The app keeps payment-related references and status information, such as checkout identifiers, connected-account identifiers, subscription status, and order totals; its checkout does not ask you to enter full card numbers into Solara's forms. Stripe processes information under its own Privacy Policy.

4. Why information is used

Information is used to create and secure accounts, review seller applications, publish requested content, facilitate purchases, maintain seller business records, administer billing and promotions, deliver notifications, respond to support requests, investigate misuse, and operate and improve the service.

Where applicable data-protection law requires a legal basis, processing may be necessary to provide the requested service or fulfill a contract, meet legal obligations, pursue legitimate operational and security interests, or act on consent where required. The appropriate basis depends on the information, feature, and applicable law.

5. Public information and recipients

Public seller profiles may show display names, usernames, contact methods, descriptions, menus, images, tags, announcements, availability, and ratings. Public products, reviews, and public leaderboard entries are visible to visitors; opted-in seller metrics may appear on global leaderboards. Public material can be copied, indexed, or shared by others. Remove unnecessary personal information before publishing it.

Sellers receive information needed for their orders and customer relationships. Administrators can access information needed for application review, support, moderation, account management, and platform operation. Other buyers do not receive access to your private seller workspace or account settings.

Service providers may process information to host the application and uploaded media, deliver email, or process payments. Depending on deployment, email may use SMTP or Brevo and uploads may use local or object storage. Analytics pages load Chart.js from a third-party CDN, which may receive request metadata. These providers may operate in countries different from yours.

Information may also be disclosed when required by law or reasonably necessary to address fraud, security incidents, disputes, or protection of users' rights. Do not assume public content or seller-held records can be recalled from every recipient.

6. Notifications and browser controls

Account settings offer optional email preferences by notification type. Admin accounts have separate choices for application, support, feedback, and promotion alerts. In-site alerts and email are separate channels, and disabling banners does not delete notifications. Authentication and password-reset messages are distinct from optional update preferences.

You can clear local storage and cookies using browser controls. Doing so may reset saved filters or sign you out; blocking essential cookies may prevent account functions from working.

7. Retention and account deletion

Information is kept while needed for the account, requested features, business records, support, security, or applicable legal and dispute obligations. There is no single retention period for all data. Read in-site notifications are eligible for cleanup after 30 days; unread notifications and other records follow their own lifecycle.

Buyer account settings provide account deletion. Deletion removes the buyer sign-in account and associated account features, but seller-held customer and order records can remain after their link to the buyer account is removed. Seller billing, independent seller records, payment-provider records, and any operational backups or logs are not necessarily erased by a buyer account deletion.

8. Your choices and requests

Use account settings to update supported profile fields, notification choices, and download the available JSON account export. The export covers the records exposed by that tool and is not a promise that every operational log or provider-held record is included.

Depending on your location and applicable law, you may have rights to access, correct, delete, restrict, object to processing, or receive certain information in a portable form, and to withdraw consent where processing relies on it. Contact us for requests the account tools do not support. We may need to verify your identity and consider applicable exceptions. You may also have the right to complain to your local data-protection authority.

Contact the seller directly for information they hold independently, and the payment provider for information it controls. Avoid sending sensitive identity documents unless specifically requested through an appropriate channel.

9. Security and age eligibility

The app hashes passwords and uses account permissions and request-protection mechanisms. No internet service can guarantee absolute security. Use a unique password, protect your email account, and report suspected unauthorized access promptly.

The service is intended for people legally able to enter the relevant account and purchase agreements, not for children using it without appropriate authority. Contact us if you believe an account contains information collected from a child inappropriately.

10. Changes and contact

This policy may change with platform features or operating practices. The date above identifies the current version. Significant changes may also be communicated through available account or platform notifications.

For privacy questions, account requests, or concerns, visit Contact us or use the published details below.