Privacy Policy

Product

PhoneAid

Android package

com.phoneaid.guidedhelp

Developer / publisher

KegaSoft

Policy version

1.0

Effective date

13 August 2026

Support

info@kegasoft.com.tr

This policy URL

https://phoneaid.kegasoft.com.tr/privacy.html

How-to guide

phoneaid.kegasoft.com.tr/help.html

1. Who we are

PhoneAid is published by KegaSoft. For privacy questions, deletion help, or to exercise your rights, email info@kegasoft.com.tr.

This policy applies to:

• the PhoneAid mobile app for Android;
• this website at phoneaid.kegasoft.com.tr, which hosts product information, the how-to guide, and this policy.

This website is a static information site. It does not create user accounts and does not require you to submit personal data to read it. If you email us, we will process the content of that email in order to reply.

2. Summary in plain language

• PhoneAid helps a helper and an assisted user solve everyday Android problems with guides — not by taking over the phone.
• You do not create a named account. Each device uses an anonymous session so pairing and sync can work.
• Help content is shared only with the person you pair with, and only while that pairing is active, and only for topics you allow.
• Screenshots are never captured automatically. You must pick an image yourself.
• We do not sell your data. We do not use PhoneAid data for advertising.
• You can stop sharing, delete shared cloud data, and delete local history in the app.
• This release is a free product. There are no in-app purchases. Remote crash reporting is off.

3. Roles, pairing, and trust

Users choose a role: Helper or Assisted user.

1. The helper creates a short 6-digit pairing code.
2. The assisted user enters the code and reviews consent settings.
3. On accept, PhoneAid creates an active pairing and a consent record.

Codes are stored hashed (not in plaintext), expire in about 10 minutes, and are rate-limited against guessing. Helpers should only pair with people they trust. PhoneAid does not independently verify real-world identity beyond this pairing flow. A pairing code is a credential for that help relationship — treat it like a temporary key.

4. Authentication

PhoneAid uses anonymous authentication per device (Supabase Auth). The app does not collect a name, email address, or password for sign-in. An anonymous session (tokens stored in the device secure storage) identifies the device to PhoneAid’s backend so pairing and sync can work.

This anonymous identifier is required for cloud sync and pairing. It is not a social profile and is not shown to the other person as an email address.

5. Information we process

PhoneAid processes only what is needed to provide guided help. Categories:

5.1 On the device (local)

Stored in the app’s private database on the phone until you delete it or uninstall the app, for example:

• chosen role and language;
• Simple Assist Mode preference;
• pairing cache and consent toggles;
• help requests, messages, session progress;
• device snapshots you allowed;
• local copies of images you chose to attach.

Android backup of app data is disabled so this help content is not copied into cloud or adb backups.

5.2 In the cloud (when you pair or send help)

When cloud sync is used, PhoneAid stores pairing-bound records with our infrastructure provider, including:

• pairing and consent settings;
• help requests (problem type, optional description, status);
• messages between helper and assisted user (questions, replies, short instructions, screenshot or status requests);
• guide session progress;
• device snapshots, filtered by consent;
• screenshot files you manually selected, in a private storage location scoped to the pairing;
• optional helper notes on those screenshots;
• device registration rows needed for pairing;
• anonymous auth user identifiers.

These records are visible to the paired helper only while the pairing is active, and only for fields the assisted user allowed.

5.3 Device summaries (optional, consent-gated)

If the assisted user turns the relevant switches on, a snapshot may include high-level information such as:

• basic device info (for example model and Android version);
• battery summary (level / charging);
• storage summary (free vs used space — not file names);
• installed-apps summary (typically a count, not private app content);
• sensitive permission summary (permission types, not the private content those permissions protect).

Snapshot fields are allow-listed against consent before storage. Direct client inserts into snapshot tables are denied. Helpers see only consented fields while the pairing is active.

5.4 Screenshots (optional, manual)

• Never captured automatically.
• The assisted user must select an image with the system photo picker.
• The app warns users not to send passwords, bank information, private messages, or personal photos they do not wish to share.
• Files upload to a private storage bucket under a pairing-scoped path.
• PhoneAid does not use AccessibilityService, continuous screen capture, camera recording, or microphone recording for help.

5.5 This website

The website itself does not require cookies for core reading. Your browser and our hosting provider may process standard technical logs (for example IP address, user agent, and requested URL) to deliver the page, maintain security, and diagnose faults. We do not use advertising cookies or sell website analytics profiles.

5.6 Support email

If you write to info@kegasoft.com.tr, we process your email address and the message so we can help you. Please do not send pairing codes, authentication tokens, passwords, or sensitive screenshots in support mail.

6. Information we do not collect

PhoneAid does not collect, read, or upload:

• SMS / MMS or call logs;
• contacts / address books;
• precise or approximate location for tracking;
• microphone or camera recordings (screenshots are gallery picker only);
• notification content from other apps;
• passwords or banking details inside other apps;
• accessibility, keystroke, or continuous screen data;
• remote-control commands;
• a traditional name/email/password account;
• purchase or payment card data (there are no paid purchases in this release).

PhoneAid does not use Device Admin, VPN service, notification listener, or AccessibilityService to operate or observe other apps.

7. Why we process information

We process the information above to:

• create and maintain a trusted pairing between two devices;
• deliver help requests, messages, guides, and optional screenshots;
• enforce consent and isolate one pairing from another;
• let you stop sharing and delete shared data;
• keep the service secure (for example hashed pairing codes and rate limits);
• answer support requests you send by email;
• publish this policy and product documentation.

We do not use PhoneAid help content for advertising, marketing profiles, or sale to data brokers.

8. Legal bases

Depending on where you live, we rely on one or more of the following:

• Performance of a contract / providing the service you asked for — pairing, sync, and delivering help you initiate.
• Consent — optional device summaries, screenshot sharing, and similar switches you can turn off.
• Legitimate interests — securing pairing codes, preventing abuse, keeping a minimal revoked-pairing audit row, and answering support mail, balanced against your rights.
• Legal obligation — if we must retain or disclose information to comply with applicable law.

If you are in Türkiye, we process personal data in line with Law No. 6698 on the Protection of Personal Data (KVKK) for the purposes described in this policy. If you are in the European Economic Area or the United Kingdom, we process personal data in line with applicable GDPR / UK GDPR principles of purpose limitation, data minimisation, and storage limitation.

9. Who can see information

9.1 The paired helper or assisted user

The other participant in an active pairing may see consented help content (requests, messages, allowed summaries, and screenshots you sent). After Stop sharing, remote access to that help thread is cut off.

9.2 Service providers (processors)

We use Supabase as a backend service provider / processor for anonymous authentication, database, edge functions, and private file storage. Data in transit uses HTTPS/TLS. The mobile app embeds only a public anonymous key — never a privileged service-role key. Row-level security is designed so one pairing cannot read another pairing’s content.

Our website hosting provider processes technical logs as needed to serve this site.

Email infrastructure used for info@kegasoft.com.tr processes messages you send to support.

9.3 What we do not do

• We do not sell personal data.
• We do not share PhoneAid help content with advertisers.
• We do not use it to build advertising audiences.

We may disclose information if required by law, a valid legal process, or to protect the rights, safety, or security of users or KegaSoft, and only to the extent reasonably necessary.

10. International processing

Backend infrastructure may process data on servers outside your country, including where our processor operates. Where required, we rely on appropriate safeguards offered by the provider (such as contractual clauses) together with encryption in transit and access controls described above. If you have questions about transfers, email info@kegasoft.com.tr.

11. Retention

• Active pairing data is kept while needed for the help relationship.
• After Stop sharing, the pairing is marked revoked. New help-thread access, uploads, and completions for that pairing are blocked. Existing cloud rows remain until you use Delete shared cloud data.
• After Delete shared cloud data, pairing-bound help requests, messages, sessions, snapshots, attachments, and storage screenshots for that pairing are removed. A minimal revoked pairing audit row (without message bodies or screenshots) may remain so the system can record that the relationship ended.
• Anonymous auth users and device registration rows are not always fully erased by pairing deletion alone, because they identify the device for security and future pairing. You may ask support to help with residual questions.
• Local data remains on the phone until you delete local help history, reset app data, or uninstall.
• Support emails are kept only as long as needed to resolve your request and meet record-keeping needs.
• Expired unused pairing invitations are designed to be purged.

PhoneAid does not automatically delete other apps, files, or system settings on the phone.

12. Your controls and rights

12.1 In the app

If a server disconnect or cloud deletion fails, the app offers retry. Local stop-sharing still takes effect on the phone.

12.2 By email

You may also email info@kegasoft.com.tr to ask us to help with deletion, to ask what categories we process, or to object or restrict processing where the law gives you that right. We may need enough information to locate the relevant pairing or device without asking you to send secrets (do not send pairing codes or tokens).

12.3 Additional rights

Depending on your location, you may have the right to access, correct, delete, or port personal data, to withdraw consent, to object to certain processing, and to lodge a complaint with a supervisory authority. In Türkiye, you may contact the Personal Data Protection Authority (KVKK). In the EEA, you may contact your local data protection authority.

13. Security

We take measures appropriate to a consent-first help app, including:

• HTTPS/TLS in transit;
• anonymous tokens in platform secure storage, not plaintext preferences;
• hashed pairing codes, expiry, and brute-force rate limits;
• row-level isolation so pairings cannot read each other’s content;
• private screenshot storage with paths bound to the pairing;
• server-side consent filtering for snapshots;
• Android allowBackup=false so local help data is not swept into device backups;
• no privileged backend key shipped inside the mobile app.

No method of transmission or storage is perfectly secure. Please pair only with people you trust, and avoid sending images that contain secrets.

14. Children

PhoneAid is designed for family help, including situations where an adult helps a parent. It is not directed at children under 13, and we do not knowingly collect personal data from children under 13 to create profiles. Do not pair a child’s device with a stranger. If you believe we have information from a child that should not have been provided, email info@kegasoft.com.tr and we will take appropriate steps.

15. Crash reporting and diagnostics

For the current free release, remote crash reporting is off. Crashes and handled errors may be logged locally on the device. Logs are scrubbed so tokens, pairing codes, message bodies, and screenshot paths are not left in clear text. Those local logs are not uploaded to KegaSoft automatically. Testers and users should use info@kegasoft.com.tr for manual feedback.

If we enable remote crash reporting in a future version, we will update this policy and Google Play Data Safety before that change ships.

16. Purchases

There are no paid purchases in this release. Google Play Billing is not implemented. In-app Premium or Family screens are informational previews only. We do not collect payment card or purchase history through PhoneAid.

17. No remote control

PhoneAid cannot and will not operate the assisted user’s phone remotely, change system permissions without the user acting in Android Settings, install or uninstall apps without user action, or view the screen continuously in the background. All help is guidance only. The assisted user performs every step on their own device.

18. Google Play Data Safety (summary)

The following matches how we complete Play Console Data Safety for this release:

• Data encrypted in transit (HTTPS).
• Users can stop sharing and delete shared cloud data in-app, and can email support.
• Data is not sold and is not used for advertising.
• Account: anonymous per-device session (no traditional email account).
• Photos: only user-selected screenshots when sharing is used.
• App activity: help requests, messages, and session progress for the paired helper while active.
• Device identifiers: anonymous auth and device registration needed for pairing.
• Crash logs: local only; not shared remotely while remote crash reporting remains off.
• Approximate device diagnostic summaries: only if consent allows.

19. This website

The pages at phoneaid.kegasoft.com.tr describe the product, provide a how-to guide, and publish this policy so the in-app Privacy Policy link and Google Play listing can point to a stable HTTPS address. Using the site is optional. The app remains usable for paired help without browsing this site, except that the policy itself is hosted here for transparency.

20. Changes to this policy

We may update this policy when the product, our processors, or the law changes. The effective date at the top will change. Material changes that affect how we handle personal data will be reflected here before (or at the same time as) they apply to the app. Please review this page when you update PhoneAid.

21. Contact

KegaSoft
PhoneAid privacy and support
info@kegasoft.com.tr

How to request deletion or help:

1. Use in-app Stop sharing and Delete shared cloud data where available.
2. Use Delete local help history on the device if needed.
3. Email info@kegasoft.com.tr if retry fails or you have a privacy question.

This policy is provided in English as the authoritative public text for PhoneAid.