MobileApi Privacy Policy

Last updated: May 1, 2026. This policy explains how MobileApi accesses, uses, shares, protects, and deletes information when you use the Android app, backend API, WebSocket bridge, website, and related services.

1. Who We Are

MobileApi is a connected-device API solution for routing backend requests to an Android device. References to "MobileApi", "we", "us", and "our" mean the MobileApi project and its operator. For privacy questions, requests, or complaints, contact tilki00aydin@hotmail.com.

2. Information We Access or Collect

MobileApi handles personal and sensitive information only for the functionality described in this policy and in the app interface. The main categories are:

Device connection data

Device ID, connection status, WebSocket events, request IDs, timestamps, IP-derived server logs, and error diagnostics used to route requests and keep the bridge available.

Contacts data

Names and phone numbers read from the connected Android device only when contacts permission is granted and an authorized contacts request is sent to the device.

SMS data

Recipient phone number, message body, send request metadata, and delivery or failure status needed to process an SMS request through the connected device.

App preferences

Local settings such as light or dark theme preference, stored on the device to keep the app comfortable to use.

If you contact us by email, we may receive your email address and any information you choose to include in the message.

3. Android Permissions

The app may request permissions for contacts and SMS features. Permission prompts are controlled by Android. You can deny, revoke, or change these permissions in your device settings. Without the relevant permission, the related MobileApi feature may not work.

Contacts and SMS data should be used only with consent-based devices, lawful authorization, and test data where appropriate. MobileApi must not be used for spam, harassment, unauthorized surveillance, or unlawful messaging.

4. How We Use Information

Register a connected Android device with the backend.
Maintain a real-time WebSocket connection.
Route contacts and SMS requests to the correct device.
Return contact, SMS, status, error, and timeout responses.
Provide support, troubleshoot bugs, and improve reliability.
Protect the service from misuse, abuse, and security issues.
Comply with legal obligations and enforce service rules.

5. Legal Bases Where Required

Where laws such as the GDPR require a legal basis, MobileApi may process personal information based on consent, performance of a requested service, legitimate interests in operating and securing the service, and compliance with legal obligations. You may withdraw permission-based access through Android settings or by stopping use of the connected-device features.

6. Sharing and Disclosure

MobileApi may share or transmit information only as needed for the service:

With the backend and hosting providers that route device API requests and WebSocket messages.
With the API consumer or dashboard that initiated an authorized contacts or SMS request.
With Android, device services, and mobile network carriers as needed to send an SMS message.
With service providers that help operate, secure, debug, or host MobileApi.
When required by law, legal process, security investigation, or to prevent harm.

We do not sell personal information, and we do not share contacts or SMS content for targeted advertising.

7. Retention and Deletion

MobileApi is intended to keep contacts and SMS payloads only for the time needed to complete the requested device action, unless a temporary record is needed for debugging, security, abuse prevention, legal compliance, or service reliability. Local theme preferences remain on the device until changed, cleared, or the app is uninstalled.

You may request deletion by emailing tilki00aydin@hotmail.com. Some records may be retained where required for legal, security, or legitimate operational reasons.

8. Security

We use reasonable technical and organizational measures designed to protect information handled by MobileApi. Because contacts and SMS data can be sensitive, API consumers should use secure endpoints, protect device IDs, restrict access to trusted users, and avoid sending real contact data or SMS messages unless they have consent and a lawful reason.

9. API Consumer Responsibilities

If you build a dashboard, automation, webhook, or backend client that uses MobileApi, you are responsible for your own legal basis, user notices, consent flows, account security, message content, and compliance with communications, privacy, anti-spam, and data protection laws that apply to you.

10. Your Privacy Rights

Depending on where you live, you may have rights under privacy laws such as the GDPR, CCPA, CPRA, or similar laws. These rights may include:

Request access to personal information associated with your use of MobileApi.
Ask us to correct inaccurate information.
Ask us to delete information where deletion is legally and technically available.
Withdraw Android permission access by changing device settings or uninstalling the app.
Object to or restrict certain processing where local law gives you that right.
Request a portable copy of information where legally required and technically feasible.

We will not discriminate against you for exercising privacy rights that apply to you. To submit a request, email tilki00aydin@hotmail.com.

11. Children

MobileApi is not directed to children under 13, and it should not be used to collect personal information from children without the required consent of a parent or guardian.

12. International Transfers

MobileApi may be operated using cloud infrastructure that stores or processes information in countries other than where you live. Where required, we rely on appropriate legal safeguards for international transfers.

13. Changes to This Policy

We may update this Privacy Policy as MobileApi evolves, including before the Android release. The updated version will be posted on this page with a new "Last updated" date.