Privacy Policy

Last updated: 2026-08-10

ShareApp is a desktop application that runs entirely on your computer. The developer operates no servers for it and collects no personal data from it.

1. Who this policy is from

This policy covers the ShareApp desktop application for macOS and Windows and this website. The software is published by Emine Osmanova ("the developer", "we"). Questions about this policy: support@ana-yurt.dev.

2. The short version

• There are no ShareApp accounts. You do not sign up, log in, or give us an email address.
• We operate no backend service for ShareApp. There is nowhere for your data to be sent to us.
• The app contains no analytics, telemetry, crash reporting or error-tracking of any kind.
• Your screenshots and recordings are written to your own disk.
• If — and only if — you configure a remote storage provider, the app uploads files from your machine straight to that provider, using credentials you supplied.
• We never receive your payment card details.

3. What the app stores, and where

Everything ShareApp keeps is kept locally on your computer:

• Captures. Screenshots, video recordings and GIFs are saved to the folder you choose in the app's settings.
• Settings. Preferences (save path, filename pattern, keyboard shortcuts, recording options, storage configuration) are stored in the application's settings file in your operating system's standard per-user application data location.
• Capture history. The app keeps a local list of recent captures, including file paths and small preview thumbnails, in that same local settings store, so it can show them in the app window.
• Storage credentials. FTP host, username and password; Amazon S3 access key ID and secret access key; Dropbox and Google Drive OAuth client IDs, client secrets and refresh tokens. These are written to the same local settings file on your machine. They are never transmitted to the developer, because there is no developer-operated server to transmit them to. They are sent only to the service they belong to (your FTP server, AWS, Dropbox, Google), by your own request, when you test a connection or upload a file.

Because these files live on your computer, deleting them is entirely under your control: remove the app's settings file and the captures folder, or use the app's reset-settings option, and nothing of it remains.

4. Storage providers you configure

ShareApp can save a capture to any of the following destinations. All of them are off by default except local disk, and each one only becomes active after you enter its configuration yourself.

• Local disk — the file is copied into your chosen folder. No network involved.
• FTP / FTPS — the app connects to the host, port and account you entered and uploads the file there.
• Dropbox — the app uploads to your Dropbox account through Dropbox's API, and can create a Dropbox shared link for the uploaded file.
• Google Drive — the app uploads to your Google Drive through Google's API. Note that when the app uploads a file it also sets that file's Drive sharing permission so that anyone with the link can read it; if you do not want that, do not use the Google Drive provider.
• Amazon S3 (and S3-compatible endpoints) — the app uploads to the bucket you named, using your access key. If you enable the "make public" option, the object is uploaded with a public-read ACL.

In every remote case the data goes directly from your machine to that third party. It does not pass through us. Once your file is in Dropbox, Google Drive, S3 or your FTP server, it is governed by that provider's own privacy policy and terms, and by whatever sharing settings you and that provider apply. We have no access to it and no ability to delete it for you.

One extra detail, for completeness: when you press "test connection" on the FTP provider and you have filled in a public "base URL", the app makes an HTTP HEAD request to that URL to check the uploaded file is reachable. That request goes to the address you typed, and nowhere else.

5. Connecting Dropbox or Google Drive (OAuth)

Connecting Dropbox or Google Drive opens a sign-in window inside the app that loads the provider's own authorisation page. You sign in with Dropbox or Google directly, in an isolated browser session that the app discards afterwards. The app captures the authorisation code that the provider redirects back with, exchanges it with the provider for a refresh token, and saves that token in the local settings file described above. Your Dropbox or Google password is never seen or stored by the app, and no token or credential is ever sent to the developer.

You can revoke this access at any time from your Dropbox or Google account security settings, independently of the app.

6. Network connections the app makes

We think you are entitled to a complete list. ShareApp makes network connections in exactly these situations:

1. Storage you configured. Connections to your FTP server, Dropbox, Google Drive, or S3/S3-compatible endpoint, to test a connection or upload a file. Local-disk-only users never trigger these.
2. OAuth sign-in. Connections to Dropbox or Google when you choose to connect one of those accounts.
3. Update check (DMG and Windows builds only). About ten seconds after launch, the app asks GitHub Releases whether a newer version has been published, and offers to download it if so. This is a real outbound connection to GitHub, and like any web request it exposes your IP address and the request itself to GitHub, whose privacy policy applies to it. The check reports no identifiers about you and sends us nothing — we do not receive or see it. Copies of ShareApp installed from the Mac App Store do not perform this check at all; Apple handles their updates.
4. Links you click. Opening a link from the app's About or settings screen (such as this page) hands it to your normal web browser.

There is no other outbound traffic: no usage reporting, no licence "phone home", no crash uploads, no advertising or tracking network.

7. Operating system permissions

• Screen recording. Required — it is how the app takes screenshots and records video. On macOS you grant it in System Settings → Privacy & Security → Screen Recording. The captured image or video is handled locally by the app and written to your chosen folder.
• Microphone. Optional, and only requested if you turn on audio capture for recordings. It is used solely to record the audio track of the video you are making. If you leave audio capture off, the app does not ask for or use the microphone.
• File access. The app reads and writes in the folder you pick for saved captures.

None of these permissions are used for anything beyond producing the capture you asked for, and nothing captured through them is transmitted anywhere except to the storage destination you configured.

8. This website

These pages are static HTML and CSS. There is no JavaScript, no cookies, no analytics, no embedded fonts, no third-party requests of any kind. The hosting provider may keep standard web-server access logs, which typically include IP addresses, as part of normal operation and security.

9. Purchases

ShareApp is a one-time purchase, sold through the Mac App Store and as a DMG through an external checkout provider linked from this site.

• Mac App Store. Apple processes the purchase. Apple's privacy policy governs it. We receive only the aggregate sales reporting Apple provides; we do not receive your payment details.
• DMG. The purchase is completed on the external checkout provider's own pages, under that provider's privacy policy. They handle payment and typically collect your email address in order to deliver the download and receipt. We never receive or store your payment card details.

10. Children

ShareApp is a general-purpose utility and is not directed at children. Since we collect no personal data at all, we do not knowingly collect personal data from children.

11. Changes to this policy

If this policy changes, the updated version will be published on this page with a new "Last updated" date. Material changes will also be noted in the release notes of the version they apply to.

12. Contact

Privacy questions, or requests relating to your rights under applicable data protection law: support@ana-yurt.dev. Data controller: Emine Osmanova. A postal address is available on request by email.