Sonith Manakkat

Privacy policy

Privacy Policy: Share to GitHub Issue

Effective date: 2026-10-16 App: Share to GitHub Issue, version 0.1.0, package com.sonith.sharetogithubissue Developer: Sonith. Contact: sonythm@gmail.com

The developer runs no server for this app and receives none of your data. The app sends data to GitHub only, using a personal access token that you provide, and only to do what you ask.

What the app does

You share text, a link or a screenshot from another app. The app builds a GitHub issue from it and sends it to GitHub with your token.

Network: the one host

The app connects to one host only: api.github.com, over HTTPS. Each request carries your token in the Authorization header. Requests:

  • GET /user: checks the token. GitHub returns your username and avatar link.
  • GET /user/repos: lists the repositories you can access (names, whether private, whether issues are on).
  • GET /repos/{owner}/{repo}/labels: lists the labels of a repository you pick.
  • POST /repos/{owner}/{repo}/issues: creates the issue. Sent: the title, body and labels you chose. The body holds the text or link you shared, any template text, and a table of device details.
  • PUT /repos/{owner}/{repo}/contents/.github/issue-attachments/...: commits each screenshot you attach, as a resized JPEG, with the commit message "Attach <file name> from Share to GitHub Issue".

Device details in the issue body: phone model, Android version, the app you shared from (if known), this app's version, screen size and language. You can remove any of them in the Device sheet before sending.

What you send is stored by GitHub under your account and governed by GitHub's privacy statement. Screenshots committed to a public repository, and issues in a public repository, are public.

The app also opens links in an in-app browser tab (the GitHub page for creating a token, an issue page, the privacy policy). Those pages are run by GitHub, not by the app. The app also checks whether the phone is online, to send queued issues. That check sends nothing.

The app has no analytics, no advertising, no crash reporting and no other network calls.

What the app stores on your phone

  • GitHub token: in the Android secure store (expo-secure-store), which encrypts it with a key held in the Android Keystore.
  • In a local database in the app's private storage: your issues (text, labels, device details, status, and any error from GitHub), queued and failed issues, copies of resized images you attached, your repository list, default repository and labels, your body template, your GitHub username and avatar link, and settings.

The database is not encrypted by the app. It relies on Android's app-private storage.

Notifications

Notifications are local. The app makes them on your phone. There is no push service.

  • The app asks for the Android notification permission (POST_NOTIFICATIONS) when needed. Android 13 and newer shows a prompt.
  • Types: issues sent, an issue could not be sent or the token has a problem, and an optional reminder that issues are waiting (off by default).
  • The text can include the repository name, an issue title and the error from GitHub, for example "App crashes on login" was not sent. It can show on your lock screen if your phone is set to show notifications there.
  • You can turn each type off in the app, or all of them in Android settings. Delete all data cancels them.

Permissions

  • INTERNET and ACCESS_NETWORK_STATE: to reach api.github.com and to know when you are back online.
  • POST_NOTIFICATIONS, RECEIVE_BOOT_COMPLETED, VIBRATE: for notifications.
  • Storage permissions limited to Android 12 and older (up to SDK 32): added by a library.
  • Share target: the app appears in the Android share sheet for text and images. It receives only what you share to it. It does not access your photos, camera, contacts, location or microphone.

Data safety summary

Data types sent to GitHub at your request: your GitHub token (authentication), your issue text and labels, screenshots you choose to attach, and device details in the issue. Not shared with anyone else. Not sent to the developer. Sending is needed for the app to work, except screenshots and device details, which you can leave out. Encrypted in transit (HTTPS).

Sharing and export

Settings, Export issues as JSON opens the Android share sheet with your issues as text. Copy link puts an issue link on the clipboard. Other apps may read the clipboard. After you hand data to another app, its privacy policy applies.

Deleting your data

  • Settings, Disconnect removes the token from the phone.
  • Settings, Delete all data removes issues, repositories, settings, the token and scheduled notifications from the phone. Uninstalling the app also removes them.
  • Issues and screenshots already on GitHub stay there. Delete them on GitHub, and revoke the token at github.com/settings/tokens.
  • Demo mode can be switched off in Settings. It removes only the sample rows.

You can ask the developer to delete data at sonythm@gmail.com, but the developer holds none. Your data is on your phone and on GitHub.

Backups

The developer keeps no copy. Android's own device backup may include app data, depending on your phone's settings. The app's backup rules exclude secure-store data, so the token is not backed up. The developer does not control Android backup.

Children

The app is not directed at children. It needs a GitHub account, and GitHub's terms set their own minimum age.

Changes

If this policy changes, the new version will be published at the same address with a new effective date.

Contact

Sonith, sonythm@gmail.com

--- Owner notes, delete before publishing:

  • The About screen opens https://github.com/sonith/share-to-github-issue/blob/main/PRIVACY.md. Publish this policy at that address, or change the link in app/about.tsx and rebuild.
  • VERIFY ON DEVICE: the sentence "backup rules exclude secure-store data". The manifest sets fullBackupContent and dataExtractionRules to the expo-secure-store rules; confirm on an Android 12+ device that the token is not restored after a backup restore.
  • VERIFY ON DEVICE: merged permissions of the release build (see play-console-answers.md).