LogoMarkPress

Privacy Policy

1. Our Privacy Commitment

MarkPress is engineered around a fundamental privacy principle: your photos and batch images are processed entirely in your browser. Unlike conventional cloud services that upload your creative assets to remote servers, our processing pipeline runs locally on your machine via client-side canvas technology. Source photos and exported ZIP files are not uploaded for processing. Account services, payments, and Pro cloud logo storage use online services as described below.

2. Information We Collect

We collect only the minimal data necessary to provide account functionality, authenticate sessions, and deliver requested features:

  • Account Information: We store your email address, name, profile image if provided, and authentication records. Email/password accounts use a password hash, not your plain-text password. Third-party sign-in uses account identifiers and authentication tokens. Session and request information, such as IP addresses and browser details, may be processed for authentication, rate limiting, and security.
  • Cloud Logo Storage: For Pro users, logos used in a successful export can be saved to the cloud so you can reuse them. We store the logo file, name, content hash, and usage information linked to your account. Saved logos are displayed using file URLs; do not treat those URLs as confidential storage. You can delete saved logos from Studio. Free users' logos are not saved to the cloud.
  • Billing Information: Our payment provider processes payments and manages billing. Account details may be shared with that provider to create a billing customer, including during signup when billing is enabled. We store plan, payment-provider identifiers, subscription status, and billing dates to manage access. We do not store your full payment card details.
  • Support & Inquiries: If you email our support team at help@markpress.app, we retain your email and correspondence to resolve your request.

3. What We Never Collect or Access

  • Your Batch Photos: Source photos are processed locally, not uploaded to our servers. They may also be stored in your browser to restore Studio after login or checkout.
  • Exif or Metadata Harvesting: We do not log, sell, or analyze the metadata of your processed photos.
  • Cross-Site Advertising Trackers: We do not deploy third-party advertising tracking scripts or sell user data to data brokers.

4. Cookies and Local Storage

We use cookies and browser storage, including local storage, session storage, and IndexedDB, for:

  • Maintaining authenticated sessions and remembering the sign-in method.
  • Remembering your UI theme preferences (Dark / Light mode).
  • Remembering your choice to proceed on a mobile screen.
  • Saving source files, logos, fonts, and Studio settings locally before login or checkout so your work can be restored. Recovery snapshots expire after two hours for restoration purposes; expired data is not necessarily removed from your device immediately. You can remove local data through your browser's site-data controls.

Service providers help us operate authentication, hosting, databases, email delivery, logo storage, billing, optional sign-in, and font loading. Loading external services can send technical request information, such as your IP address and browser details, to those providers; their own privacy policies also apply.

5. Data Security

Local image processing reduces the need to send source photos to a server. Account and cloud-logo services still require storing data online. We use authentication and access checks to protect account features, but no service or storage method is completely secure. Keep your credentials secure and avoid using Studio on shared devices for sensitive material.

6. Account Deletion

You can delete your account using the Delete account button in Account Settings. If you need help, email us at help@markpress.app. Some records may need to be retained for legal, billing, or security obligations. Deleting your account does not automatically clear data stored in your browser; use your browser's site-data controls to remove it.