Skip to legal content

Privacy Policy

A plain-language account of what stays in your browser, what limited information reaches AppScreenie, and which outside services are involved.

Effective

1. Who is responsible

The controller for the processing described in this policy is Jurica Kalamir, the operator of AppScreenie. Privacy questions and requests can be sent to hello@appscreenie.com.

This policy applies to appscreenie.com, the public website, the browser-based editor, and information received through AppScreenie’s published contact and support channels.

2. Privacy at a glance

  • AppScreenie currently has no user accounts or cloud project storage.
  • Projects, uploaded images, custom fonts, and previews normally stay in your browser profile.
  • If you explicitly enable AI editing, bounded project text and metadata are shared with OpenAI's browser agent for that tab.
  • AppScreenie does not use advertising, behavioral tracking, product analytics, or marketing-email tools.
  • AppScreenie does not sell personal data or share it for cross-context behavioral advertising.
  • Limited technical data is processed to deliver and secure the website. Supabase receives requests for the public support feed, and Google receives requests when Google Fonts are used.
  • AppScreenie receives contact or Ko-fi supporter information only if you choose to contact or support the project.

Technical requests are necessary to deliver and secure the website. Contacting AppScreenie, supporting it through Ko-fi, and requesting a public supporter credit are optional. Browser-local storage is needed for requested project-save functions; blocking it can prevent those functions from working.

3. Data that stays in your browser

The editor stores project documents, uploaded screenshots and images, imported font files, generated previews, and revision information in browser storage such as IndexedDB. AppScreenie does not receive this content during ordinary editor use.

In a supported browser, you may explicitly enable AI editing for the current tab. AppScreenie's Site tools can then send OpenAI's browser agent bounded project information needed for the actions you request, including project and screen names, canvas text, layer and asset metadata, current settings, and revision information. The tools also return bounded command or undo results. Project text and filenames can contain personal information, so review a project before enabling this optional feature.

These Site tools do not send screenshot, image and font file bytes, desktop file paths, export files, or a raw project file to the agent. If the agent asks for screenshots, you must click the local file control, choose them yourself, and approve their assignment. The selected files remain in browser-local project storage. Permission is not saved and ends when you disconnect, close the tab, or leave the editor.

OpenAI's browser may separately process information it can observe on the visible page, outside the results returned by AppScreenie's Site tools. OpenAI controls that browser-side processing under its own terms and privacy notice. Do not enable AI editing for a project whose content you do not want the browser AI to receive.

These local project stores are described in the Cookie & Local Storage Policy.

Because AppScreenie cannot see browser-local project data, it cannot retrieve, inspect, restore, or delete that data for you. You can delete projects from the Projects page or clear AppScreenie site data in your browser settings.

4. Website and security data

When you request a page or asset, ordinary internet infrastructure processes technical information needed to deliver and protect the Service. This may include your IP address, approximate city or country derived from it, requested URL, request time, response status, browser and device characteristics, referring page, and security or diagnostic information.

AppScreenie is hosted using Vercel. Vercel processes website traffic and service-generated information as described in its Privacy Notice. AppScreenie does not add an analytics identifier to this data or use it to build visitor profiles.

5. Google Fonts

The editor offers Google Fonts. When the editor loads the font catalog or a Google font used by a project, your browser requests metadata, stylesheets, or font files directly from Google. Those requests can include your IP address, browser information, referrer information, and the requested font resource.

Google processes that information under its own Privacy Policy. AppScreenie does not receive a list of your Google Font requests from Google. You may instead import a supported font file that you are entitled to use; imported fonts remain in browser-local project data.

6. Contact and support information

If you email AppScreenie, the operator receives your email address, name if supplied, message, attachments, and related correspondence. Please do not send secrets or sensitive personal data that are not needed to answer your request.

If you choose to support AppScreenie on Ko-fi, Ko-fi and its payment providers process the transaction. Depending on your choices and the payment method, AppScreenie may receive your display or legal name, email address, message, contribution details, transaction status, and limited payment-related records. AppScreenie does not receive your full payment-card number.

Ko-fi explains its role and the information shared with creators in its Privacy Policy. Payment providers have their own privacy notices. The AppScreenie website links to Ko-fi but does not embed a Ko-fi tracking or payment script.

Depending on Ko-fi, PayPal, the payment method, and the supporter's settings, the operator may also receive a country, postal address, or other limited billing or contact detail made available for the transaction. AppScreenie does not request shipping details for a contribution and uses any such information only for support administration, legal records, fraud prevention, or a requested membership benefit.

For an eligible public donation or membership payment, Ko-fi also sends AppScreenie's Supabase Edge Function a webhook. After validation, the public record contains only a random record ID, an activity type, the payment amount and currency for a donation or the membership tier, and the payment time. The public record does not contain the supporter's name, email address, message, Ko-fi profile, payment URL, transaction identifier, shop items, or shipping information.

Separately, a private Supabase table stores Ko-fi's stable message identifier so repeated or delayed webhook delivery does not publish the same activity twice. Browser visitors cannot read that table. The small identifier is retained without scheduled deletion to preserve that duplicate protection, unless correction or removal is required for legal, privacy, or data-quality reasons.

This public support activity is deliberately readable by anyone through the Supabase Data API and Realtime feed. When a visitor opens the Support or Support activity page, the visitor's browser connects directly to Supabase, which receives ordinary technical connection information. The public activity record is kept permanently unless it needs correction or removal for legal, privacy, or data-quality reasons. Requests can be sent to hello@appscreenie.com.

7. Optional supporter credits

Active monthly supporters may choose to be credited publicly. Only the approved name and, depending on the credit level, an approved logo and website link are published. A public credit is based on your consent. Supporting AppScreenie without a public credit remains possible.

Approved credit details are kept in version-controlled site source or public site assets and are included in website deployments. This means GitHub, the hosting provider, and their subprocessors may process the approved name, link, or logo while providing repository, build, security, and deployment services.

You can withdraw permission by emailing hello@appscreenie.com. The current public credit and active site-source entry will be removed within a reasonable publication cycle. Historical versions, build records, security archives, or backups can remain for longer under restricted access and provider retention practices. They will not be reused to republish the credit and will be erased, anonymized, or further restricted where applicable law requires it.

8. Why information is processed

PurposeInformationLegal basis where GDPR applies
Deliver and secure the ServiceRequest, device, and diagnostic dataPerformance of the Service agreement and legitimate interests in reliable, secure operation
Provide editor fontsTechnical requests sent to GoogleLegitimate interests in providing the requested creative-tool functionality
Provide optional AI editingBounded project text, metadata, settings, commands, and resultsSteps taken at your request when you enable the feature for the current tab
Respond and administer supportCorrespondence, supporter, and transaction recordsSteps at your request or performance of a membership agreement, legitimate interests in responding and administering support, and legal obligations such as accounting
Publish public support activityActivity type, donation amount and currency or membership tier, and payment timeLegitimate interests in acknowledging support and maintaining a transparent support history
Publish a supporter creditApproved name, logo, and linkConsent, which you may withdraw

Information may also be processed where necessary to comply with law, respond to lawful requests, prevent fraud or abuse, and establish, exercise, or defend legal claims.

9. Who receives information

Personal information is disclosed only as reasonably necessary to:

  • Vercel and infrastructure providers that deliver and protect the website;
  • Supabase for the public support-activity database, browser reads, Realtime updates, and Ko-fi webhook processing;
  • GitHub and related version-control or build providers for approved supporter-credit source and assets;
  • Google when your browser requests Google Fonts catalog, stylesheet, or font resources;
  • OpenAI when you enable AI editing and use Site tools in its supported browser;
  • Ko-fi and payment providers when you choose to visit Ko-fi or make a contribution;
  • professional advisers or service providers bound by appropriate duties, if reasonably needed; and
  • courts, regulators, law enforcement, or other parties when required by law or necessary to protect legal rights and safety.

AppScreenie does not sell personal data, operate a data-broker business, or disclose personal data for targeted advertising.

10. International processing

Vercel, Supabase, GitHub, Google, OpenAI, Ko-fi, payment providers, and their subprocessors may process information outside Croatia or the European Economic Area. Their notices describe where they operate and the transfer mechanisms they use. Where AppScreenie is responsible for an international transfer, it will use a mechanism permitted by applicable law, such as an adequacy decision or contractual safeguards where required.

11. How long information is kept

  • Browser-local projects remain until you delete them, clear site data, or the browser removes them. AppScreenie does not control that period.
  • Hosting and security data is kept under the hosting provider’s operational and security retention settings. AppScreenie does not copy it into a separate analytics database.
  • AppScreenie does not keep a separate server copy of Site-tool project content or results. OpenAI's retention of browser-agent activity is governed by the OpenAI product and account you use.
  • Contact correspondence is kept for as long as reasonably needed to answer, maintain necessary records, and resolve related issues.
  • Support and transaction records are kept for the periods required by accounting, tax, fraud-prevention, and other applicable laws.
  • Sanitized public support activity is kept permanently unless a record must be corrected or removed for legal, privacy, or data-quality reasons.
  • Public supporter credits remain while the relevant support is active and permission remains in place. The current public credit and active site-source entry are then removed within a reasonable publication cycle. Restricted version history, build records, and backups may remain longer under provider retention practices and are not used to republish the credit.

Information may be retained longer where reasonably necessary for a legal claim, dispute, security investigation, or binding legal duty.

12. Your privacy rights

Depending on applicable law, you may have rights to access, correct, erase, restrict, or receive a portable copy of personal data, and to object to certain processing. Where processing is based on consent, you may withdraw consent at any time without affecting earlier lawful processing.

Send a request to hello@appscreenie.com. Enough information may be requested to verify the request without collecting more than necessary. Because ordinary projects remain in your browser, AppScreenie cannot provide or erase them on your behalf.

You may also complain to the Croatian Personal Data Protection Agency (AZOP) through its complaint procedure, or to the competent authority where you live or work.

13. Security

AppScreenie uses measures intended to reduce privacy and security risk, including browser-local project processing, HTTPS in production, restrictive browser security headers, bounded file handling, and limited third-party connections. No online or local-storage system can be guaranteed completely secure. Keep independent project backups and protect access to your device and browser profile.

14. Automated decisions

AppScreenie does not use personal data for profiling or decisions that produce legal or similarly significant effects. It does not use visitor personal data to train an AppScreenie AI model.

15. Children

AppScreenie does not intentionally seek personal data from children. Anyone who cannot independently agree to the applicable terms should use the Service only with a parent or guardian's permission and should not purchase support memberships or request a public credit unless permitted under Ko-fi's terms and applicable law.

16. Changes and contact

This policy will be updated before AppScreenie introduces materially different processing such as user accounts, cloud project storage, advertising, analytics, marketing email, or another third-party data service. The effective date at the top identifies the current version.

Questions or requests can be sent to hello@appscreenie.com.