Privacy Policy

1. Who We Are

ScreenCraft is an app store screenshot designer built and operated by a solo developer. We help mobile developers create professional store listings for iOS and Android apps. This policy explains what data we collect, why we collect it, and how we protect it.

This Privacy Policy applies to the ScreenCraft web application accessible at screencraftapp.com (or any associated domain) and all related services. It does not apply to third-party websites or services we link to.

2. Data We Collect

2.1 Information You Provide

• Account information — your email address when you sign up. Optionally, a display name and profile picture you set in your profile.
• Project data — the screenshot projects you create and save, including layout configurations, text content, and element positioning.
• Uploaded assets — images you upload (app screenshots, icons, background images, custom device frames) are stored in private storage buckets accessible only to your account.
• Store credentials — App Store Connect or Google Play credentials you enter to publish screenshots (used once, then deleted) or to watch an app’s listing with Listing Watch (kept, encrypted, until you remove the app). See section 11.
• Payment information — payments are processed by Paddle (Merchant of Record). We store only the transaction status, reference ID, plan tier, and payment method type. We never see or store your card details, bank account, or e-wallet credentials.
• Feedback and reviews — when you send feedback or review an export, we store your message and, for a review, a 1–5 rating and — only if you tick the box — your permission to quote you on screencraftapp.com using your first name and the app you were designing. That consent is optional and off by default; you can withdraw it at any time by contacting us.

2.2 Data Collected Automatically

• Usage logs — we record export events (timestamp, plan tier, export count, file format) to enforce daily limits and detect abuse. No image content is logged.
• Account activity — when you act on your account (creating your account, signing in, signing out, changing your password, creating, duplicating or deleting a project, uploading an image, starting an export, or publishing to a store) we record what happened, when, which project it concerned, and the IP address and browser it came from. We use this only to help you when you contact support and to investigate abuse or unauthorised access. It is stored on our own database, never shared or sold, contains no image content, project content or passwords, and is deleted automatically after 90 days.
• Authentication tokens — session cookies and tokens required to keep you logged in securely.
• Device information — browser type, screen resolution, and operating system for rendering optimization.
• Sign-up measurement — on our marketing pages and sign-up page we record a few anonymous steps (page viewed, button clicked, demo played or opened, sign-up attempted or completed) with the page path, the referring site’s domain, any utm_source tag, and a random per-tab ID. We use this only to count how many visitors sign up. It is stored on our own database, never shared or sold, and contains no IP address or name; when you create an account, the completed step is linked to your account.

We do not use advertising cookies or analytics services that profile you across websites. To operate payments, our Merchant of Record, Paddle, loads its own client-side scripts for checkout and subscription management (including Paddle’s Retain functionality). These scripts are operated by Paddle under Paddle’s own privacy policy — see section 5 (Data Sharing).

3. How We Use Your Data

We use the data we collect for the following purposes:

• Service operation — saving projects, processing exports, rendering previews, and enforcing plan limits.
• Account management — authentication, password resets, and profile management.
• Communication — transactional emails such as account confirmation, password reset links, and payment receipts. We do not send marketing emails unless you opt in.
• Abuse prevention — export log analysis to detect and prevent rate-limit circumvention, credential stuffing, or other abusive behaviour.
• Refund processing — when you request a refund, we process your transaction reference, payment method, and account email to validate and fulfil the request in accordance with our Refund Policy. Refund records are retained as required by financial regulations.
• Service improvement — aggregated, anonymized usage patterns to improve features, performance, and reliability.

4. Legal Basis for Processing

We process your data based on:

• Contract performance — to provide the Service you signed up for.
• Legitimate interest — to ensure security, prevent abuse, and improve the Service.
• Consent — where required, we will ask for your explicit consent (e.g., marketing communications).

5. Data Sharing

We do not sell, rent, or share your personal data with any third party for marketing or advertising purposes.

We use the following sub-processors to deliver the service:

• Supabase — database hosting, authentication, file storage, and edge function hosting. Data stored in Supabase is protected by Row-Level Security policies. Supabase operates data centres in multiple regions.
• Paddle — payment processing for paid subscriptions (Merchant of Record). Paddle handles billing, taxes, and compliance. Subject to Paddle’s own Privacy Policy. Paddle processes card details, bank information, and other payment data; we only receive transaction confirmations.
• Vercel — application hosting and serverless function execution. Vercel processes minimal personal data (HTTP request metadata) to serve the application.

We may also disclose data if required by law, regulation, or legal process, or to protect the rights, property, or safety of ScreenCraft, our users, or the public.

6. International Data Transfers

Your data may be processed and stored in servers located outside your country of residence. Supabase and Vercel operate data centres in various regions. By using the Service, you consent to the transfer of your data to these jurisdictions, subject to the protections described in this policy.

7. Data Retention

• Account data — retained for as long as your account is active.
• Project data & uploaded assets — retained until you delete the project or your account.
• Export files — temporary files (PNG, ZIP) are automatically deleted within 7 days of generation.
• Publishing credentials — deleted as soon as the upload they were provided for finishes or fails.
• Listing Watch credentials — kept, encrypted, until you remove the watched app or delete your account. Pausing a watch or ending your Pro plan does not delete them (see section 11).
• Export logs — anonymized retention for up to 12 months for abuse detection and analytics.
• Account activity log — kept for 90 days, then deleted automatically. Deleting your account deletes it immediately.
• Feedback and reviews — kept for as long as your account is active.
• Payment records — transaction status and reference IDs are retained as required by financial regulations.
• Refund records — refund request details, including transaction reference, reason, and resolution, are retained for 24 months as required by financial regulations and for dispute resolution purposes.

If you delete your account, all associated data — projects, uploaded assets, stored Listing Watch credentials, and personal information — will be permanently deleted within 30 days.

8. Your Rights

Depending on your jurisdiction, you have the right to:

• Access — request a copy of the personal data we hold about you.
• Rectification — request correction of inaccurate or incomplete data.
• Erasure — request deletion of your personal data (right to be forgotten).
• Portability — export your project data in a portable format (JSON).
• Objection — object to the processing of your data based on legitimate interest.
• Withdrawal of consent — withdraw consent for marketing communications at any time via your profile settings.

To exercise any of these rights, please contact us via the email on our home page. We will respond to your request within 30 days.

9. Cookies & Local Storage

We use only essential cookies for session management (authentication tokens stored via Supabase Auth). We do not use advertising cookies or analytics services that profile you across websites. Paddle’s client-side payment scripts (section 5) may set their own cookies as needed for checkout, fraud prevention, and subscription management.

We use browser local storage to save your editor preferences (theme, tool sizes, last-used settings) for a better experience. This data stays on your device and is not transmitted to our servers. We also keep a small flag per account in local storage so the “how was your first export?” review prompt is shown at most once.

For the sign-up measurement described in section 2.2, we keep a random ID in your browser’s session storage. It is not a cookie, is not shared with other sites, and is deleted when you close the tab.

10. Security

We implement the following measures to protect your data:

• Encryption in transit — all data is transmitted over HTTPS with 256-bit SSL/TLS encryption.
• Row-Level Security (RLS) — database access is protected by Supabase RLS policies, ensuring your data is never accessible to other users.
• Secure file storage — uploaded assets are served through time-limited signed URLs.
• Authentication — powered by Supabase Auth with support for email/password and OAuth providers (Google, Apple, GitHub).
• Payment security — all payment processing is handled by Paddle (PCI-DSS Level 1 certified as Merchant of Record), which maintains its own security certifications and compliance programs.

While we take security seriously, no system is completely secure. We encourage you to use strong, unique passwords and enable two-factor authentication where available.

11. Store Credentials

ScreenCraft uses your App Store Connect or Google Play access in two places, and handles them differently. Publishing uses one-time credentials that are deleted as soon as the upload ends. Listing Watch, a Pro feature, keeps the credentials for each app you choose to watch, encrypted, until you remove that app.

11.1 Publishing: used once, never kept

• One-time only. Your private key, service account JSON, or Google Play access token is encrypted (AES-256-GCM, per-record random salt and IV) for the single upload job you start, then deleted from our database as soon as that upload finishes or fails.
• Connecting with Google. The Google Play option can sign you in with Google instead of a key: you grant the Manage your app’s listings scope on Google’s own consent screen, and we receive a short-lived access token (about an hour) that exists only for that upload.
• Nothing kept for publishing. A publish never saves your store access for reuse: no publish credential outlives its upload, and you provide the credentials again for each upload.

11.2 Listing Watch: kept until you remove the app

Listing Watch checks an app’s live store listing on a schedule (about once a week per app) and whenever you choose Run now. Scheduled checks run without you, so when you add an app to watch, its credentials are stored:

• What is stored. For App Store Connect: the API key ID, the issuer ID, the .p8 private key, and the app’s bundle ID. For Google Play: the app’s package name and exactly one credential, either the refresh token Google issues when you connect Google Play for Listing Watch (it lets checks run while you are away) or the service account JSON you paste instead.
• How it is protected. The private key, refresh token, and service account JSON are encrypted at rest (AES-256-GCM, per-record random salt and IV). They are never shown back to you or sent to any browser (the Listing Watch pages show only the key ID and the bundle ID or package name), and only our background worker decrypts them, at the moment a check runs. They are never written to logs or to check reports.
• Read-only use. A check only reads your listing. It never uploads, changes, or deletes anything in App Store Connect or Google Play.
• How long it is kept. Until you remove the app from Listing Watch or delete your account. Pausing a watch only stops scheduled checks; the credentials stay stored. If your Pro plan ends, scheduled checks stop, but the stored credentials stay until you remove the app. Remove stays available on the Free plan.
• Removing it. Remove, on the watched app’s page in Listing Watch, deletes the app together with its stored credentials from our database.

11.3 For publishing and Listing Watch

• Your Google account. When you connect with Google, we store nothing about your Google account, not even your email or name. You can revoke ScreenCraft’s access at any time at myaccount.google.com/permissions.
• Limited Use. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
• Least privilege. App Store Connect keys need only the App Manager role. Google Play service accounts need only Manage store listings (read & write) permission.
• Revocation. You can revoke a key at any time in App Store Connect (Users and Access → Integrations) or Google Cloud Console, or revoke a Google connection at myaccount.google.com/permissions. Access is cut instantly, including for any watched app that uses it.
• Audit trail. Every credential use is logged with timestamp and action type, including saving or removing a watched app and every Listing Watch check, plus your IP address when you start the action yourself.

12. Children’s Privacy

The Service is not directed to children under 13 years of age. We do not knowingly collect personal information from children under 13. If we learn that we have collected data from a child under 13, we will delete it promptly. If you believe a child under 13 has provided us with personal data, please contact us immediately.

13. Third-Party Links & Services

The Service may contain links to third-party websites or integrate with third-party services. We are not responsible for the privacy practices of those third parties. We encourage you to review their privacy policies before providing them with any personal information.

14. Data Breach Notification

In the event of a data breach that poses a risk to your rights and freedoms, we will notify you via email within 72 hours of becoming aware of the breach, in compliance with applicable data protection laws. The notification will include the nature of the breach, the categories of data affected, and the measures we are taking to address it.

15. Changes to This Policy

We may update this policy as the Service evolves. When we make material changes, we will update the “Last updated” date at the top of this page. For significant changes that affect how we handle your data, we will provide notice via email or an in-app notification. We encourage you to review this page periodically.

16. Contact

If you have any questions about this policy, wish to exercise your data rights, or need to report a security concern, please reach out via the contact details on our home page.