Privacy Policy

Who we are

Intenseloop, Inc. operates AppScreen at appscreen.pro and its Design Hub at appscreen.design.

Privacy questions: orp.neercsppa@troppus

This policy covers the editor, billing, sign-in, agent setup at /mcp, share links, the Design Hub, and related pages. Google, Stripe, and our email provider publish their own policies for the parts they run.

What AppScreen is not

• We do not sell your personal information
• We do not read your Gmail, Drive, Calendar, or other Google products
• We do not upload your canvas, screenshots, or project files unless you turn on cloud (Pro)

You can use the free editor without an account. Projects stay in this browser unless you export an image, download a project file, or, with Pro, turn on cloud.

What stays on your device

These stay in IndexedDB and local storage on your computer:

• Panorama layouts, layers, text, logos, uploaded images, and presets
• Theme, zoom, and view preferences
• Your AppScreen session token after you sign in (about 30 days)

Clearing site data for appscreen.pro removes local work. We cannot restore it unless it is also in your cloud.

What cloud keeps (Pro, only after you turn it on)

Cloud is off until you turn it on. When it is on, we keep in your account:

• Your works: layouts, text, settings, and the images in them
• A small preview image of each work
• Earlier versions of each work, for up to 30 days
• Your custom presets
• A snapshot of each work you share with a link

We use them only to show your works back to you on the computers where you sign in, and to show a shared snapshot to anyone who opens its link. We do not look at them, train models on them, or share them, unless the law requires it or you ask support to look at a specific work. If someone reports a link you shared, support looks at it and may remove the link. You can keep any single work in this browser only.

What share links publish (Pro, only when you create one)

Nothing is shared until you create a share link for a cloud work. The link publishes a snapshot of that work at appscreen.design/s/<name>-<token>, with its images and text as they were when you created or last updated the link. The name in the address starts as the work's name. Older appscreen.pro/s/ addresses redirect there.

• Anyone with the link can view the snapshot without an account
• Viewers can open their own editable copy unless you turn that off, and download the slides as PNG files if you turn that on. To do either, they sign in and confirm they are behind the app or have its owner's permission
• The page says "Shared by" and your first name, taken from your Google account name. You can hide it on each link. When it shows, the page's metadata for search engines also lists it as the author

A copy someone opens is saved in their browser, not in your account. We cannot delete copies other people made.

When you download or open a copy of a set someone else shared, we keep your confirmation: your account id and email, the link, the version of the set, whether you downloaded or copied it, the time, and the sentence you agreed to. We keep it for 3 years, even if you or the person who shared it delete your accounts, because we may need it to answer a claim about that use. Then we delete it.

Links are unlisted. We tell search engines not to index them unless you turn on Show in search engines. With that on, we list the link in the Design Hub's sitemap (appscreen.design/sitemap.xml) and send its address to IndexNow, which Bing, Yandex, and other search engines use to find new pages. We also tell IndexNow when a listed link changes or ends, but search engines decide when to drop it from their results.

The Design Hub at appscreen.design shows a set as soon as its owner turns on Show on appscreen.design. A listed set shows its slides, app icon, name, subtitle and category, and your first name unless you hide it, on the hub's pages, its feed and its search. Your public profile there shows the handle, name, bio, links and photo you give it; the photo is kept with your cloud images and anyone can load it while your profile shows it. Links made before the Design Hub launched are listed. Turn the switch off, or stop sharing, to take a set off the hub. Pages on the hub are cached for a few minutes, so a set can take that long to disappear.

We count how many times each link is opened and how many copies people open from it, and show those numbers only to you. Your own opens do not count. To avoid counting the same visitor twice, we keep the visitor's IP address in server memory for up to an hour. We never write it to disk. Per-IP rate limits on share links also run in memory. Open counts do not use cookies.

Anyone can ask for a set or profile on the Design Hub to be taken down at appscreen.design/takedown. The request sends support an email through SparkPost with the link, the name and email the person entered, their reason and the statement they confirmed, and their IP address and browser user agent. We reply to that email address.

Anyone can report a link from its page. A report sends support an email through SparkPost. It holds the link, your account and work ids, the reason the reporter wrote, and the reporter's IP address and browser user agent. Support may remove a link after a report, and the page then says it was removed after a report. We also record the report in UserPath on the sharer's account, with the link, its name, the work id and the reason, so we can follow up with the sharer. That record does not include anything about the reporter.

Deleting the work does not take its link down. Stop sharing to do that.

What we collect

Account

Sign-in uses Google Identity Services. Google sends us an identity token. From that token we store:

• Google’s user id for you
• Your email, only when Google marks it verified
• Your name and profile photo, so we can show them in the account menu and address mail. Your first name is also the "Shared by" name on share links

You can also sign in with a code we email you. We send six digits to the address you type; the code works once, for 10 minutes, and we keep it only in memory, hashed, until then. Signed in that way, we store your email as your account's address and nothing else about you. Google and an emailed code with the same address reach the same account.

We keep that profile on our servers so the same account can restore Pro on another browser.

Pro purchase

Stripe processes the one-time Pro payment. We receive confirmation that it succeeded, Stripe ids (customer, checkout session, payment intent), and enough metadata to tie the purchase to your account. We do not see your full card number.

We keep purchase and Stripe webhook records so we can grant Pro, handle refunds, and resolve billing questions.

Mail

After a purchase or refund we send a transactional email through SparkPost (MessageBird) to the address on your account. Stripe also sends its own receipt. Share link reports and email sign-in codes go through SparkPost too.

Newsletter

If you sign up for AppScreen news in the site footer, your email, your name if you give it, and where you signed up go to UserPath, which keeps our email list and sends the newsletter from news.appscreen.pro. A new account joins the same list: the first time you sign in, your account's email and name go to UserPath the same way. Signing in again never adds you back. Every newsletter has an unsubscribe link, and unsubscribing stops them for good unless you sign up again.

If you write orp.neercsppa@troppus, we keep the thread so we can answer you.

Product analytics

We run product analytics with UserPath. Your browser sends page views, billing steps (paywall view, checkout start, checkout complete, and the reason Stripe's form gave when it refused a card), what you do with cloud and the works library (for example turning cloud on, opening a work saved on another computer, resolving a conflict, restoring a version, or downloading your works; the action and counts only, never your designs or their names) and, when an agent is connected over MCP, which editor tools it ran (tool names only, never your designs) through our own /events endpoint. Export events also carry a yes or no flag for whether the work is a copy opened from a share link.

Our server also sends some data to UserPath directly: checkout start, purchase, and refund (amount and currency), a payment that failed (Stripe's reason codes and message, the currency and the card's country, never the card itself), when you turn cloud on or off (with how much storage you use), and a report someone made about a share link of yours (the link, its name, the work id and the reason, without anything about the reporter), together with your browser's user agent, IP address, and approximate location (country, region, city), so these events join your visit. When you sign in or return signed in, our server tells UserPath your AppScreen account id, name, email, Google profile picture (avatar), plan (Free or Pro, and a coupon if you used one), and whether cloud is on.

Analytics cookies are not ad cookies. Signing out starts a new anonymous UserPath session.

Moving between appscreen.pro and appscreen.design

When you follow a link between our two sites, the link carries your UserPath visitor id, so both sites count one visit. If you are signed in, it also carries a one-time sign-in code: it works once, within a minute, and signs the same account in on the other site. Both sites remove these from the address bar as the page loads.

Agent connections

Connecting an AI client through MCP uses the same Google sign-in. We issue a short-lived access token so that client can call tools in your open editor tab. We do not send your canvas to an agent server as part of that flow. The client you choose has its own privacy terms.

Fonts

When you pick a typeface, the editor may load it from Google Fonts. Google may log that request under its policy.

Server logs

Our host may keep ordinary request logs (IP address, user agent, time, path) for security and uptime. We do not use them for advertising.

Who processes data for us

• Google — sign-in and optional font files
• UserPath — product analytics (page views, billing events, account id, name, email, avatar, plan), and the newsletter list (email, name, signup source)
• Stripe — checkout, receipts, refunds
• SparkPost — purchase and refund email, email sign-in codes, and share link reports to support
• Cloudflare — DNS and traffic to the site

If you list a share link in search engines, we send its address to IndexNow, which passes it on to Bing, Yandex, and other search engines that take part.

AppScreen itself is hosted on servers in Germany. Google, Stripe, SparkPost, UserPath, and search engines may process data in the United States or other countries under their own terms.

How we use data

• Run the editor and keep you signed in
• Keep your works in your cloud when you turn it on
• Show the works you share at their links, and count opens and copies for you
• Handle reports about share links
• Unlock Pro on the same Google account
• Process payments and refunds
• Send purchase and refund mail
• Answer support
• See whether billing flows work

We do not use this data for third-party advertising, and we do not sell it.

Cookies and similar storage

On appscreen.pro and appscreen.design:

• _up.sid — UserPath analytics session
• _up.aid — your AppScreen account id for UserPath, once you sign in
• Local storage — session token, theme, and editor preferences
• IndexedDB — projects and presets

Google’s sign-in button and Stripe’s checkout form may set cookies on their domains. We do not control those.

How long we keep data

• Account and purchase records: while you have an account, and as long as we need them for billing, tax, or law
• Support email, including share link reports and takedown requests: as long as needed to resolve the thread
• Analytics events: as long as useful to understand billing reliability
• Local browser data: until you clear it
• Cloud works: until you delete them. Trash and earlier versions: 30 days
• Share link snapshots: until you stop sharing, we remove the link after a report, or we delete your cloud works. Deleting the work alone does not remove them
• Visitor IP addresses for share link counts: in server memory only, for up to an hour
• If you turn off cloud, or Pro ends after a refund, your cloud works stay readable for 30 days so you can download them, then we delete them. Our backups age out 14 days after that
• MCP access tokens: until they expire, you sign out, or you disconnect the client

Your choices

• Use the free editor without signing in
• Sign out from the account menu to drop the session in this browser
• Clear site data to remove local projects
• Unsubscribe from the newsletter with the link in any issue
• Stop sharing a link to take its page down. Copies people already opened stay in their browsers
• Turn off cloud from the account menu, keep a single work in this browser only, or export all your works as one file from the works library
• Email orp.neercsppa@troppus to ask for a copy of your account data, or to delete the account

If we delete an account, Pro on that Google id ends, its cloud works are deleted within a day, and our backups age out within 14 days. We may retain billing records where the law requires it. Projects saved only in a browser stay on that device — clear them there.

If you live in a place that grants access, correction, deletion, or portability rights, use that same address. We will handle the request as the law requires.

Children

You must be at least 18 to use AppScreen. We do not knowingly collect personal information from anyone under 18. If you think we have, email us and we will delete it.

Changes

We may update this policy. The date at the bottom of this page is the latest version. If a change is material, we will say so on this page.

Contact

Intenseloop, Inc. orp.neercsppa@troppus