Privacy Policy

1. Introduction

Mockupster is an online mockup platform for discovering scenes, customizing designs in a browser-based editor, saving projects, and exporting mockup images. This Privacy Policy explains what information the current Mockupster application handles, why it is used, and which service providers help operate it.

Mockupster is available at https://mockupster.com. This policy describes the application as it is currently implemented; features and providers may change as the product develops.

2. Information we handle

Account information

When you sign in, Mockupster receives account identifiers from Supabase Auth. Depending on how you sign in, this can include your email address and, when provided by Google, your name and profile image. Supabase also assigns an account ID used to associate your projects and uploaded artwork with your account.

Projects and artwork

When you save a project, Mockupster stores its name, creation and update timestamps, and editor settings such as the selected scene, canvas dimensions, background, placement, scale, rotation, perspective, and a reference to an uploaded asset. Project records are stored in the Mockupster Supabase database.

When you upload an image while signed in, the application sends the image to a Mockupster Cloudflare Worker, which stores it in Cloudflare R2. The current editor accepts PNG, JPEG, and WebP images up to 12 MB. Exported PNGs are rendered in your browser and downloaded or copied to your clipboard; the export action does not upload the rendered image to Mockupster.

Browser and authentication data

The application stores the Supabase sign-in session in your browser’s local storage so you remain signed in. It also uses session storage temporarily for the Google sign-in verifier and the page to return to after authentication. The selected language and some editor preferences are stored locally in your browser.

Requests to Mockupster, Supabase, Google, and Cloudflare necessarily carry technical request information such as network address and browser request details to those services. The application code does not include an analytics or advertising SDK, a payment processor, or a separate product telemetry service.

3. Google Sign-In and Google user data

If you choose Google Sign-In, Google and Supabase Auth handle the authentication flow. Mockupster receives the basic account information returned for sign-in—typically your name, email address, profile image when available, and a Google/Supabase account identifier. Mockupster uses this information to authenticate you, associate your Mockupster account with saved projects, and show your account identity in the interface.

The current application starts Google authentication through Supabase and does not request access to Gmail, Google Drive, Google Calendar, contacts, or other unrelated Google services. It does not use Google account information to access those services.

Supabase processes authentication information on Mockupster’s behalf. The account session returned after sign-in is stored in your browser’s local storage so authenticated features can work. Mockupster does not use Google profile information for advertising in the current application.

4. How we use information

The current product uses information to authenticate accounts, display the signed-in profile, provide the editor, save and reopen project settings, store and retrieve uploaded artwork, and deliver exports requested by you. Account and request information may also be processed as needed to maintain the service, protect authenticated routes, and troubleshoot failures.

5. Cookies and browser storage

The Mockupster application code does not set advertising or analytics cookies. It uses browser local storage for the authentication session, language choice, and editor preferences, and session storage for short-lived sign-in flow data. Clearing site storage signs you out and may reset locally saved preferences.

Supabase and Google operate their own authentication pages and may use their own technologies while you complete sign-in. Their handling is governed by their respective privacy notices and settings.

6. How information is shared

Mockupster does not sell personal information as part of the current service. Information is processed by providers needed to operate the features you use:

• Supabase provides authentication and the PostgreSQL database used for saved projects.
• Cloudflare serves the application and Worker routes and stores uploaded artwork in R2.
• Google participates when you choose Google Sign-In and returns the basic account information described above.

Information may also be disclosed if required by law or when necessary to protect the service, its users, or others. The current codebase does not integrate advertising networks or data brokers.

7. Storage and security

Saved project records are kept in Supabase and the Worker checks the authenticated Supabase user before serving, storing, or deleting an uploaded asset. Project database policies restrict access to the owning account. Uploaded objects are addressed using a path scoped to that account and are accessed through the authenticated Worker route.

These controls reduce unauthorized access but cannot guarantee that any online service or transmission is completely secure. The exact region, backups, and platform-level retention settings for the Supabase and Cloudflare accounts are not defined by the application source code.

8. Data retention

The current application does not implement a scheduled data-retention period or a self-service account deletion flow. Saved records and uploaded assets remain in their respective services until they are removed through an available account or infrastructure operation. The application does not currently guarantee that deleting a project record also removes its separately stored R2 object.

Before Mockupster launches broadly, an official privacy contact and a documented process for handling access and deletion requests should be configured. No fixed retention duration is stated because one is not currently implemented.

9. Your choices and requests

You can sign out from the account menu. You can change the basic name, email, or profile image associated with Google through your Google account, subject to what Google returns to Supabase. Editor preferences stored in this browser can be cleared by removing Mockupster site data from your browser.

Mockupster does not currently provide an in-app control to download all account data or delete an account. A public privacy contact channel must be configured before users can submit account access, correction, or deletion requests.

10. Children’s privacy

Mockupster is a general-purpose design tool and is not designed specifically for children. The application does not include an age-verification flow. If you believe a child has provided personal information to Mockupster, please use the official privacy contact channel once it is published so the request can be reviewed.

11. International users

Mockupster is intended for users in different countries. Supabase and Cloudflare may process information in locations determined by the project and service settings. The exact data regions and any applicable transfer arrangements cannot be verified from the application code alone.

12. Changes to this policy

This policy may be updated as Mockupster’s features or data practices change. The effective date at the top of this page will be updated when the policy changes. Material changes should be communicated through the website or another appropriate product notice.

13. Contact Mockupster

The project currently has no public privacy or support email address configured in its website or source code. An official contact method must be added here before launch so users can send privacy, account access, and deletion requests.

Website: https://mockupster.com