Android · nexus.skandax.sms · v1.0 (Build 1)

Your messages belong on your phone. Nowhere else.

Skandax Messages Shield (SMS) is a default SMS app for Android built around one rule: your messages stay on your device. No accounts, no cloud sync, no analytics and no internet permission. Incoming messages are written to a private SQLCipher-encrypted database whose key is protected by the Android Keystore.

Get it on Google Play How protection works

Free · Android 7.0 and later · Read the Privacy Policy

  • No data collected
  • No analytics
  • No cloud sync
  • No internet permission
0personal data collected
0cookies on this website
0cloud copies of messages
AES-256encryption at rest

The product

A complete SMS app that assumes nobody else should see your messages

Skandax Messages Shield replaces your default SMS handler without moving your message history off the device. Receiving, sending, threads, contacts and deletion all run locally on Android.

Default SMS handler

Android delivers SMS only to the app that holds the default-SMS role. Shield asks for that role and handles receiving, sending, threads and composition once the role is granted.

Encrypted private vault

Message data lives in a private SQLCipher (AES-256) database inside the app's own storage. Its database key is protected by a key held in the Android Keystore.

Conversations, on-device

Inbox with contact-name resolution, newest-first conversations, unread state, and compose with contact search or a direct number — all computed locally.

Deletion on your terms

Move threads to Trash, delete individual messages, or permanently erase conversations. Permanent deletion uses SQLite secure-delete and VACUUM to reduce recoverable remnants.

Refuses untrusted devices

A device-integrity gate checks for root and USB or wireless debugging at launch and on resume. If the Android sandbox can be bypassed, the app locks itself instead of exposing the vault.

Offline by architecture

The Android manifest removes INTERNET and ACCESS_NETWORK_STATE. There is no analytics SDK, no advertising SDK and no server component for the app.

By design

What the app never does

Privacy here is an architecture decision, not a settings page. These are properties of the app, not optional toggles.

  • Collect, transmit or sell your personal data.
  • Send crash reports, usage events or telemetry of any kind.
  • Create an account, profile or advertising identifier.
  • Sync your messages to a cloud service.
  • Share message content or contacts with third parties.
  • Keep the shared SMS-provider copy after an encrypted write succeeds.

What is processed, and where

The app processes SMS content and metadata, locally resolved contact names, your consent flag, and device-integrity signals. All of it stays on the device. We never receive a copy — there is no server to receive one.

Read the full Privacy Policy or see what deletion actually removes.

Message flow

What happens to a message, step by step

The path is deliberately short, and every step stays inside the phone.

  1. Receive

    When Shield holds the default-SMS role, Android delivers incoming SMS to the app's SMS receiver.

  2. Encrypt and store

    The message is written to the private SQLCipher database. Its encryption key is protected by a key held by the Android Keystore.

  3. Remove the shared copy

    After the encrypted write succeeds, the app removes the corresponding row from Android's shared SMS provider, so the message is not left in plaintext there for other apps to read.

  4. Erase on uninstall

    Uninstalling the app removes its private database, encryption key material and consent flag. App backup and device transfer are disabled, so the vault is not copied into Google backups. Because Android provides no uninstall callback, messages cannot be restored to the provider at uninstall.

The shared-copy removal depends on Shield being the default SMS app on a non-rooted device with debugging disabled. Read the Security & Permissions page for the exact boundaries of these guarantees.

Straight answers

What this protection does — and does not — do

We would rather be precise than impressive. These limits are part of the product, and the in-app consent screen depends on the same facts.

At-rest encryption, not end-to-end

SMS has no end-to-end encryption. Your carrier and the SMS network can see message content in transit, and messages are readable in memory and on screen while the app displays them. Shield protects data at rest on the device, not the SMS channel itself.

The device gate is best-effort

Root-hiding tools, custom kernels and spoofed system settings can defeat any userspace integrity check. The gate raises the cost of a compromised device; it cannot prove that a device is clean.

Deletion is not forensic erasure

Flash storage and filesystem behaviour can retain old blocks. SQLite secure-delete and VACUUM reduce recoverable remnants but do not guarantee physical erasure, and the app cannot reach backups or snapshots it does not create.

No backup, no recovery

v1 has no export workflow and no restore. Uninstalling permanently removes the vault, and permanent deletion cannot be undone. Copy anything you need to keep before you delete it or uninstall.

Before you install

Read the policy that applies to you

The in-app consent screen asks you to accept a Privacy Policy with the same four commitments shown here. The website policy below is the public version of that document, versioned and dated.

Legal · Privacy

Privacy Policy

How Skandax Nexus Pvt. Ltd. handles information in the Skandax Messages Shield (SMS) Android app and on this website.

  • Policy version 1.0
  • Last updated: 7 November 2026
  • Applies to app and website

This Privacy Policy explains what the Skandax Messages Shield (SMS) Android application (package nexus.skandax.sms) and the website at https://sms.skandax.nexus/ do with information. It is written to match the actual behaviour of the app, including the permissions removed from its Android manifest and the way its private message database is encrypted.

The short version

We do not collect, receive, store, sell or share your personal data. The app has no internet permission, no accounts, no analytics and no cloud sync. Your SMS is stored only on your device in an encrypted private database. Uninstalling the app permanently removes that private data. This website sets no cookies and loads nothing from third parties.

1. Who we are

The app and this website are provided by Skandax Nexus Pvt. Ltd., a company incorporated in India, with its registered office at No. 3-1 / 7-33, Thiru VK Nagar, Chinnalapatti, Dindigul, Tamilnadu, India – PIN 624301.

Under the Digital Personal Data Protection Act, 2023 (the DPDP Act), Skandax Nexus Pvt. Ltd. is the Data Fiduciary for personal data that it processes. As explained in this policy, the app is designed so that we do not process personal data from it at all: message content and contacts remain on your device and are never transmitted to us. Our website is a static information site with no backend, accounts or contact forms.

You can reach us through the contact details in section 18.

2. Scope

This policy applies to:

  • the Skandax Messages Shield (SMS) Android application, version 1.0 (Build 1), package nexus.skandax.sms, including the in-app Privacy Policy consent screen;
  • the website at https://sms.skandax.nexus/ and every page hosted on it.

It does not cover third-party services that you choose to use independently — for example, Google Play (which processes installation and account data under Google's own privacy policy), your mobile carrier, or another messaging app. We do not control those services.

3. Summary of commitments

The app's first-run consent screen states four commitments. This policy explains each of them in full:

  1. No data collected. There are no analytics, trackers, advertisements or user accounts, and the app has no internet permission, so message data cannot be transmitted.
  2. Encrypted and private. SMS is stored in a private SQLCipher (AES-256) database inside the app's own storage, and the database key is protected by the Android Keystore.
  3. Not readable through the shared provider. Messages received by Shield are written to the encrypted database and the corresponding shared SMS-provider copy is removed after the encrypted write succeeds.
  4. Uninstall erases the vault. Uninstalling the app removes its private message database, encryption key material and consent flag. There is no backup and no restore.

These commitments are properties of the app. They are not optional settings, and the app does not include a switch to turn collection on. Where a guarantee depends on the device or the Android platform, this policy and the Security & Permissions page say so explicitly.

4. Data the app processes on your device

The app handles the following categories of information locally. None of it is transmitted to Skandax Nexus Pvt. Ltd. or to any third party by the app.

Categories of data processed locally by the app and their purpose
InformationWhere it livesWhy the app uses it
SMS content, sender and recipient addresses, timestamps, read state, thread groupingSQLCipher-encrypted private database on the deviceTo receive, display, organise and send messages, and to show conversations
Contact names for phone numbersRead from the Android contacts provider when needed; not stored by usTo label conversations and help you pick a recipient when composing
Privacy consent flag and acceptance timePrivate app preferences on the deviceTo show the consent screen only once per install
Database encryption key materialPrivate app storage on the device, protected by the Android KeystoreTo decrypt the message database when the app opens it
Device-integrity signals (root indicators, debugger and developer-option state)Checked in memory on launch and resume; a verdict may be written to the device log with signal names onlyTo block use on devices where the Android sandbox could be bypassed. The log entry never includes message content.

MMS. Android requires a default messaging app to handle MMS delivery notifications. The MMS receiver records a fallback notice rather than storing the MMS payload, and MMS content is not imported into the encrypted database. This policy describes the payload data the app actually stores, which is SMS.

Legal basis. Where the DPDP Act applies, the app's local handling is carried out on your device under your direction and with your consent, which you give on the in-app consent screen before the default-SMS role is requested. You may withdraw consent by declining the policy or by uninstalling the app; because we hold no copy of your data, there is nothing for us to delete on our side.

5. Data we do not collect

The app and this website do not collect, and we do not receive, any of the following:

  • your name, email address, phone number or postal address;
  • your contact list, call log, location, photos, files or calendar;
  • advertising identifiers, device identifiers or installation identifiers;
  • usage events, session recordings, crash reports or diagnostic telemetry;
  • message content, message metadata or backups of your messages;
  • payment information (the app does not process payments or in-app purchases);
  • cookies, browser storage or fingerprinting data on this website.

We do not use analytics providers, crash-reporting SDKs, advertising networks, social plug-ins, session-replay tools or any other data-broker service. We do not sell or rent personal data.

6. Network access and transmission

The Android manifest explicitly removes the android.permission.INTERNET and android.permission.ACCESS_NETWORK_STATE permissions using manifest merger removal. Without the internet permission, the app has no ability to open network connections, so message data cannot be transmitted by the app even if the device is online.

There is no cloud sync, no server-side inbox and no remote backup. The app contains no analytics, advertising or crash-reporting components. Google Play may process information about app installs and updates as part of its own platform under Google's privacy policy; we do not receive your message content or contacts from Google Play.

This website is delivered as static files. It does not call any API, and it loads no script, font, image or stylesheet from a third-party domain.

7. Permissions the app requests, and why

Android requires certain permissions for a default SMS app. Each permission is used only for the purpose listed, and the app does not request network permissions at all.

Android permissions requested by the app
PermissionPurpose
READ_SMSRead messages from Android's SMS provider during the one-time encrypted import and for thread display.
RECEIVE_SMSReceive incoming SMS while Shield is the default SMS app.
SEND_SMSSend SMS that you compose in the app.
RECEIVE_MMSHandle MMS delivery notifications as a default messaging app.
RECEIVE_WAP_PUSHReceive MMS WAP push messages as required by the default messaging role.
READ_CONTACTSResolve contact names for conversations and help you pick recipients when composing.
POST_NOTIFICATIONSShow new-message notifications on Android 13 and later.
INTERNET — removedExplicitly removed from the manifest; the app cannot access the network.
ACCESS_NETWORK_STATE — removedExplicitly removed from the manifest; the app cannot inspect network state.

The default-SMS role is granted through Android's own role-selection dialog. You can revoke it at any time in Android settings, at which point Shield stops receiving SMS. More detail is on the Security & Permissions page.

8. This website

This website is a static information site. It has no backend, no database, no user accounts, no contact forms and no payment flow. The only way to send us information through the site is to write to the email address published on the Contact page; that message is handled by your own email provider and by ours.

Like any website, the site is delivered by a hosting provider. Our hosting provider (Cloudflare Pages) may process standard technical request data — such as IP address, user agent, requested path and timestamp — to deliver the site, keep it available and protect it against abuse. We do not use that data to identify, profile or track individual visitors, we do not combine it with other data, and we do not use analytics on this site. The provider's handling is governed by its own terms and privacy policy as our data processor. The Tracking & Cookies Statement sets out exactly what the site does and does not load.

9. Cookies, trackers and third parties

This website sets no cookies — neither first-party nor third-party. It does not use localStorage, sessionStorage, IndexedDB, fingerprinting, web beacons, pixels, session replay, heatmaps, A/B testing or advertising tags. It does not embed YouTube, maps, social widgets or any other third-party content. All styles, scripts and graphics are served from this domain, and fonts are the fonts already installed on your device.

The app contains no third-party analytics, advertising or tracking components. We do not share data with third parties because we do not collect it. The only third parties involved in delivering the app and website are the Google Play store (which distributes the app) and our static hosting provider (which serves this website), each acting under its own terms.

Full detail is in the Tracking & Cookies Statement.

10. Sharing and disclosure

We do not sell, rent, trade or otherwise disclose personal data, because the app does not provide us with any. Specifically:

  • we do not share message content, contacts or metadata with advertisers, data brokers, affiliates or business partners;
  • we do not share data with third-party SDK providers, because the app includes none;
  • we do not transfer data as part of a merger, acquisition or asset sale, because there is no app data to transfer.

We may disclose business correspondence that you send to us if we are required to do so by law, a court order or a lawful request from a competent authority, and we may keep records of such correspondence as required. We cannot disclose message content because it never reaches us.

11. Retention and deletion

We retain no personal data from the app or the website. All app data remains on your device under your control:

  • Messages remain in the encrypted database until you delete them or uninstall the app.
  • Trash holds soft-deleted threads until you permanently delete them, empty Trash, or uninstall the app. There is no restore action.
  • Consent flag and encryption key material remain in private app storage until you uninstall the app.
  • Uninstalling removes the app's private database and preferences. Android provides no uninstall callback, so no server-side copy exists and none needs to be deleted.

Deletion is effectively immediate on the device, but two limits apply. First, flash storage and filesystem behaviour can retain old blocks, so deletion is not a guarantee of forensic erasure. Second, copies held by your carrier, the recipient's phone, screenshots or clipboard, or any other app or backup you created are outside our control. Android app backup and device transfer are disabled for Shield, so its private data is not included in Google backups. See the Data Deletion & Uninstall page for step-by-step instructions.

12. Security measures

We designed the app around the sensitivity of SMS. The app uses:

  • SQLCipher with AES-256 for the private message database, so database pages are encrypted at rest.
  • Android Keystore custody for the key that protects the app's randomly generated database encryption key. The protected key material is kept in private app storage.
  • No network permission, which removes the app's ability to transmit data at all.
  • Backup and device-transfer disabled for app data.
  • Device-integrity gate that refuses to run when root or USB/wireless debugging is detected, with fail-closed behaviour when the native check cannot run. This gate is best-effort and cannot prove a device is clean.
  • Secure deletion using SQLite secure-delete and VACUUM for permanent deletion, subject to the flash-storage limits above.

No security measure is perfect. The app's encryption protects data at rest on a non-rooted device with debugging disabled and Shield set as the default SMS app. It does not encrypt SMS end-to-end in transit, does not protect against a compromised operating system, and cannot guarantee forensic erasure. The Security & Permissions page explains each limit in detail.

13. Children's privacy

The app is intended for adults and is not directed to children. Under the DPDP Act, a child is an individual below the age of eighteen years. We do not knowingly process personal data of children, and because the app does not transmit data to us, no children's data reaches Skandax Nexus Pvt. Ltd. The app has no advertising, no behavioural tracking and no profiling of any user, which is consistent with the additional protections the DPDP Act gives to children's data.

If you are a parent or guardian and believe that a child has used the app in a way that raises a concern, you can contact our Grievance Officer using the details in section 18. Because all message data is local, you can also remove it directly by deleting messages in the app or by uninstalling it.

14. Your rights

Under the DPDP Act, as a Data Principal you have rights including:

  • Right to access information about the personal data processed about you (section 11);
  • Right to correction and erasure of your personal data (section 12);
  • Right to grievance redressal (section 13);
  • Right to nominate another individual to exercise your rights in the event of death or incapacity (section 14);
  • Right to withdraw consent at any time, with the consequences of withdrawal explained to you (section 6).

Because we do not receive or retain your app data, these rights are principally exercised directly on your device: you can view, correct and delete messages in the app, withdraw consent by declining the policy, and remove all app data by uninstalling. There is no server-side account or dataset that requires a deletion request. If you believe we hold personal data about you, or you want to exercise a right in relation to our business correspondence, write to the Grievance Officer in section 18. We will respond within the timelines stated there.

If you are not satisfied with our response, you may escalate the matter to the Data Protection Board of India in accordance with the DPDP Act, or pursue any other remedy available to you under applicable law.

15. IT Act 2000 obligations

Skandax Nexus Pvt. Ltd. is an Indian company and operates this app and website in a manner it believes is consistent with the Information Technology Act, 2000 (as amended) and the rules made under it. In particular:

  • We aim to observe reasonable security practices and procedures of the kind contemplated by section 43A of the IT Act and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, through encryption at rest, key custody in the Android Keystore, removal of network permissions and disabled backups.
  • We do not disclose personal information in breach of a lawful contract or without consent. Section 72A of the IT Act provides for punishment for such disclosure; our design ensures that message data is not available to us to disclose.
  • We maintain a Grievance Officer and a grievance-redressal process as part of our obligations under Indian information-technology and data-protection law, including the DPDP Act.

Nothing in this section is a claim of independent audit, certification or legal endorsement. It describes the standards we design to and the law we understand to apply.

16. International transfers

We do not transfer app data internationally, because app data never leaves your device. This website is served through a global content-delivery network operated by our hosting provider, so a request may be served from a location outside India and standard technical request logs may be processed in other jurisdictions by that provider. We do not send personal data of app users to any country, because we do not hold any.

17. Changes to this policy

We may update this policy as the app evolves or as the law changes. Each version is dated and numbered. Material changes will be published on this page with a new last-updated date and effective date, and will be presented in the app where the law or platform requires it. The current in-app consent screen displays Policy version 1.0, which corresponds to this version of the website policy.

If we ever introduce a feature that changes these commitments — for example, any network feature — we will update this policy first and will not enable the feature for existing users without the consents the law requires. The app's no-network design is a deliberate product decision, not a temporary state. You should check this page for the version that applies to you. Continued use of the app after the effective date of an updated policy means you accept the updated policy to the extent permitted by law.

18. Contact and grievance officer

For privacy questions, data-principal requests, complaints or any concern about this policy, contact our Grievance Officer:

Grievance Officer
Skandax Nexus Pvt. Ltd.
Name: [Grievance Officer name]
Email: [Grievance Officer email]
Postal address: No. 3-1 / 7-33, Thiru VK Nagar, Chinnalapatti, Dindigul, Tamilnadu, India – PIN 624301

We aim to acknowledge grievances within 7 business days and to resolve them within 30 days of receipt. Please include enough detail for us to identify your request; never send us your message content, passwords or database keys.

If you are not satisfied with our resolution, you may approach the Data Protection Board of India under the DPDP Act or the appropriate forum under the IT Act, 2000. The full contact page is at Contact & Grievance.

Policy version 1.0 · Last updated 7 November 2026 · Effective 7 November 2026 · Skandax Nexus Pvt. Ltd., India

Transparency · Security

Security & Permissions

What the app protects, how it protects it, which permissions it needs, and exactly where those guarantees stop.

  • App v1.0 (Build 1)
  • Android
  • Last reviewed: 7 November 2026

Design principle

Reduce what can leak. The app keeps message data local, removes network permissions, encrypts the database at rest, disables backup and device transfer, and refuses to run on devices where the Android security model can be bypassed. Each of those measures has limits, listed honestly below.

Encryption at rest

Messages are stored in a private SQLCipher database inside the app's own storage. The app works as follows:

  1. A random database encryption key is generated for the install.
  2. A separate key-encryption key is held by the Android Keystore. It encrypts the database key before that key is stored.
  3. The encrypted database key is kept in private app storage. When the database is opened, the app retrieves the key through the Keystore.
  4. SQLCipher decrypts database pages as the app reads them. Message data is therefore available in process memory while the app is running and is displayed in the app's user interface.

On upgrade from an earlier version, existing messages are migrated into the encrypted database and the old plaintext database is removed after the migration succeeds. Removing the old file does not establish forensic erasure because flash storage can retain old blocks.

No network access

The Android manifest removes android.permission.INTERNET and android.permission.ACCESS_NETWORK_STATE from its Android manifest. The resulting app has no network permission, no analytics SDK, no advertising SDK and no server component. It cannot sync, upload, phone home or fetch remote content. You can verify this yourself in Android settings (App info → Permissions) and in the app's manifest.

Backup and device transfer disabled

The app disables Android backup and device-to-device transfer for its data. Shield's private message database and key material are therefore not copied into Google's backup systems by Android. This also means an uninstall cannot be undone through a backup restore.

Device-integrity gate

On every launch and every return to the foreground, the app checks whether the device's Android protections are still in place. It looks for signs that the device's security model may have been bypassed — such as root access, a debuggable build, or enabled USB or wireless debugging and developer options. If a check fails, the app shows a DEVICE NOT TRUSTED screen with general fix instructions. There is no override. If the check cannot complete, the gate fails closed.

This is a best-effort control. Root-hiding tools, custom kernels and spoofed settings can defeat any userspace check. The gate raises the cost of attacking a device; it does not prove that the device is clean, and it is not a substitute for keeping your operating system updated and your device locked.

Deletion

Moving a thread to Trash is a soft delete; there is no restore action. Permanently deleting messages or emptying Trash uses SQLite secure-delete and VACUUM. This reduces recoverable remnants but does not guarantee physical erasure from flash storage, and it cannot reach backups, snapshots or copies outside the app.

Permissions requested

Permissions requested by Skandax Messages Shield and their purpose
PermissionWhy the app needs it
READ_SMSRead system SMS rows during the one-time encrypted import and to display threads.
RECEIVE_SMSDeliver incoming SMS to the app as the default SMS handler.
SEND_SMSSend messages you compose.
RECEIVE_MMSHandle MMS delivery as a default messaging app.
RECEIVE_WAP_PUSHReceive MMS WAP push notifications.
READ_CONTACTSShow contact names and help you choose recipients.
POST_NOTIFICATIONSNotify you of new messages on Android 13 and later.
INTERNETRemoved — the app cannot access the network.
ACCESS_NETWORK_STATERemoved — the app cannot inspect network state.

The app does not request location, camera, microphone, storage or media-library, phone-state, accounts, calendar, body sensors or accessibility permissions.

The default-SMS role

Android delivers SMS only to the app holding the default-SMS role. Shield asks Android to show its role-selection dialog; you choose the app there. Until the role is granted, the app does not receive SMS. You can revoke the role at any time in Android settings, after which Shield stops receiving messages. When the app is the default handler, the Android system and apps holding SMS permissions may still interact with the shared SMS provider; Shield removes the provider copy after a successful encrypted write, but apps with privileged access, accessibility services or root can still reach the device in ways the app cannot prevent.

What this does not protect against

  • Interception in transit. SMS is not end-to-end encrypted. Your carrier and the SMS network can see message content.
  • A compromised operating system. Root-level malware, a modified kernel or a hostile system service can access app-private data. This is why the device gate exists, and why it is not a proof of safety.
  • Physical flash remnants. Deletion reduces but does not guarantee forensic erasure.
  • Your own copies. Screenshots, clipboard contents, notifications and copies you make outside the app are outside its control.
  • Recipients and carriers. Messages you send are stored and processed by the recipient's device and by the network.
  • User-granted access. If you grant SMS access to another app, that app's handling of the shared provider is outside Shield's control.

Reporting a security issue

If you believe you have found a security vulnerability, please contact us using the details on the Contact & Grievance page. We aim to acknowledge security reports within 5 business days. Please do not include real message content, passwords or database keys in your report; a clear description and reproduction steps are enough.

Security & Permissions · Last reviewed 7 November 2026 · App version 1.0 (Build 1)

Legal · Terms

Terms of Service

The agreement between you and Skandax Nexus Pvt. Ltd. for use of the Skandax Messages Shield (SMS) app and this website.

  • Version 1.0
  • Last updated: 7 November 2026
  • Governing law: India

These Terms of Service ("Terms") govern your access to and use of the Skandax Messages Shield (SMS) Android application (package nexus.skandax.sms) and the website at https://sms.skandax.nexus/ (together, the "Service"). The Service is provided by Skandax Nexus Pvt. Ltd., a company incorporated in India ("we", "us", "our").

Please read before you agree

By installing or using the app, or by using this website, you agree to these Terms and to the Privacy Policy. If you do not agree, do not install or use the app and stop using the website. The app stores messages only on your device and permanently deletes them when you uninstall it — that behaviour is a core part of this agreement.

1. The Service

Skandax Messages Shield (SMS) is an Android SMS application that can hold the default-SMS role and handle receiving, sending, conversations, contacts, deletion and local encrypted storage of SMS. The app is described on this website and in its in-app screens. It is a client for ordinary SMS and MMS delivered through your mobile carrier; it is not a messaging network, a cloud service or an end-to-end encrypted messenger.

We may provide updates through Google Play from time to time. This website is a static information site and provides no user accounts, subscriptions, payments or hosted messaging.

2. Eligibility

You must be at least 18 years old, or the age of majority in your jurisdiction, to accept these Terms and use the app. If you are below that age, you may use the app only with the involvement and consent of a parent or legal guardian who agrees to these Terms on your behalf. The app is not directed at children. You must not use the app if you are barred from doing so under applicable law.

3. Licence

Subject to these Terms, we grant you a limited, personal, non-exclusive, non-transferable, revocable licence to install and use the app on devices you own or control, for your personal, lawful use. This licence does not include the right to sublicense, distribute, rent, lease or commercially exploit the app. You may not copy, modify or reverse engineer the app except to the extent that applicable law expressly permits it, and you may not remove proprietary notices.

The app may include third-party components governed by their own licences. To the extent those licences conflict with these Terms, those licences prevail for the components they cover.

4. Your responsibilities

You agree to:

  • set Shield as the default SMS app if you want it to receive SMS, and understand that Android will not deliver SMS to it otherwise;
  • keep your device secure: use a screen lock, install operating-system updates, avoid root access and turn off USB and wireless debugging. The app refuses to run on devices where these controls are compromised;
  • copy or otherwise preserve any message you need before uninstalling the app or permanently deleting it, because uninstall and permanent deletion cannot be undone;
  • comply with all applicable laws, including the Information Technology Act, 2000, telecom and spam-prevention rules, and any rules applicable to the content you send;
  • not use the app to send unlawful, fraudulent, abusive, harassing or unsolicited bulk messages, or to interfere with the rights of any person;
  • not attempt to bypass, disable or interfere with the device-integrity gate or other security controls;
  • bear all carrier charges for SMS and MMS, and any device costs, associated with your use.

5. Privacy

Your privacy is governed by the Privacy Policy, which forms part of these Terms. In summary, the app does not collect or transmit your personal data; SMS is stored only on your device in an encrypted private database; the app has no internet permission; and uninstalling the app permanently removes its private data. This website sets no cookies and uses no trackers.

6. SMS, carriers and availability

SMS and MMS delivery depends on your carrier, network coverage, the recipient's device and other factors outside our control. We do not guarantee delivery, timeliness or receipt of any message. The app is not a substitute for emergency services: for emergencies, use your device's emergency calling features. Message content is not encrypted end-to-end in transit and may be accessible to carriers and the SMS network.

7. Uninstall and permanent data loss

The app is designed to keep messages private to the installation. Android does not provide an uninstall callback that would allow Shield to export its private data, so uninstalling the app permanently deletes the private message database, the encryption key material and the consent flag. There is no backup and no restore, and the app provides no bulk export. Likewise, permanently deleting messages or emptying Trash cannot be undone. You are solely responsible for copying anything you need before those actions. To the extent permitted by law, we are not liable for messages lost through uninstall, permanent deletion, device loss, device failure or failure to keep a copy.

8. Device-integrity gate

For your protection and ours, the app may refuse to run on devices on which root access, USB or wireless debugging, developer options or other sandbox-bypass signals are detected. This gate is a best-effort control. It does not guarantee that a device is secure, and it may produce false positives or false negatives. If the app does not run on your device, the remedy is to restore the device to a trusted state; there is no override.

9. Intellectual property

The app, this website, its text, graphics, layout and inline SVG artwork, and the names and marks "Skandax", "Skandax Nexus", "Skandax Messages Shield" and associated logos are owned by Skandax Nexus Pvt. Ltd. or its licensors and are protected by intellectual-property laws. Except for the limited licence in section 3, no rights are granted to you. You may not use our marks without prior written permission, except for accurate, non-misleading references to the app.

10. Updates and changes to these Terms

We may update the app and these Terms from time to time. Updated Terms will be published on this page with a new last-updated date and effective date. Where a change materially affects your rights or obligations, we will take reasonable steps to bring it to your attention, including through the app where appropriate. Continued use of the Service after the effective date of updated Terms means you accept them to the extent permitted by law. If you do not agree, you should stop using the app and website, and you may uninstall the app.

11. Disclaimer of warranties

To the maximum extent permitted by applicable law, the Service is provided "as is" and "as available", without warranties of any kind, whether express, implied or statutory, including implied warranties of merchantability, fitness for a particular purpose, accuracy and non-infringement. We do not warrant that the app will be uninterrupted, timely, error-free or free of harmful components, that it will protect data on a compromised or unsupported device, that encryption will prevent every form of access, or that deletion will achieve forensic erasure. We do not warrant any third-party service, including Google Play or your carrier. Nothing in these Terms excludes or limits any warranty or right that cannot be excluded or limited under applicable law, including consumer-protection law.

12. Limitation of liability

To the maximum extent permitted by applicable law, Skandax Nexus Pvt. Ltd. and its directors, officers, employees and agents will not be liable for any indirect, incidental, special, consequential, exemplary or punitive damages, or for loss of messages, data, profits, revenue, goodwill or business opportunity, arising out of or relating to the Service or these Terms, even if advised of the possibility of such damages. To the maximum extent permitted by law, our total aggregate liability arising out of or relating to the Service or these Terms will not exceed INR 1,000.

Nothing in these Terms excludes or limits liability that cannot be excluded or limited by law, including liability for fraud, wilful misconduct, or death or personal injury caused by negligence. If you are a consumer, you retain all mandatory rights available to you under Indian consumer-protection law and other applicable law.

13. Indemnity

To the extent permitted by applicable law, you agree to indemnify and hold harmless Skandax Nexus Pvt. Ltd. and its directors, officers, employees and agents from and against any claims, liabilities, damages, losses and expenses (including reasonable legal fees) arising out of your misuse of the Service, your breach of these Terms, or your violation of any law or the rights of any third party. This indemnity does not apply to the extent the claim arises from our own negligence or wilful misconduct.

14. Governing law and jurisdiction

These Terms and any dispute or claim arising out of or in connection with them or the Service are governed by the laws of India, including the Information Technology Act, 2000 (as amended) and the Digital Personal Data Protection Act, 2023, without regard to conflict-of-law principles. Subject to any mandatory consumer-protection rights, the courts at Dindigul, Tamilnadu, India, have exclusive jurisdiction over any dispute arising out of or relating to these Terms or the Service.

15. Grievances

If you have a complaint about the Service or these Terms, contact our Grievance Officer using the details on the Contact & Grievance page. We aim to acknowledge grievances within 7 business days and to resolve them within 30 days. You may also have the right to escalate a data-protection grievance to the Data Protection Board of India under the DPDP Act.

16. General

  • Entire agreement. These Terms and the Privacy Policy are the entire agreement between you and us regarding the Service and supersede any prior understanding on that subject.
  • Severability. If any provision of these Terms is held invalid or unenforceable, the remaining provisions remain in full force, and the invalid provision will be modified to the minimum extent necessary to make it effective.
  • No waiver. Our failure to enforce any provision is not a waiver of our right to do so later.
  • Assignment. You may not assign these Terms. We may assign them in connection with a merger, acquisition or sale of assets, subject to applicable law.
  • Force majeure. We are not liable for delay or failure caused by events beyond our reasonable control.
  • Termination. You may stop using the Service at any time by uninstalling the app. We may suspend distribution of the app or access to the website, in whole or part, where necessary for legal, security or operational reasons. Sections that by their nature should survive termination will survive.

Terms of Service version 1.0 · Last updated 7 November 2026 · Effective 7 November 2026 · Skandax Nexus Pvt. Ltd., India

Privacy · Control

Data Deletion & Uninstall

How to delete your messages, what happens when you uninstall, and why there is no account deletion request to make.

  • App v1.0 (Build 1)
  • No server-side data
  • Last updated: 7 November 2026

There is no account to delete

Skandax Messages Shield has no accounts, no cloud database and no server-side copy of your messages. We do not hold personal data about you, so there is no deletion request to submit and no retention period to wait for. You delete data directly on your device, and uninstalling the app removes the rest.

What is stored, and where

Everything the app stores is in its own private storage on your Android device:

  • the SQLCipher-encrypted message database;
  • the protected database key material in private app storage;
  • the privacy-consent flag and its acceptance time;
  • ordinary app preferences needed for the app to run.

Contact names are read from your Android contacts provider when needed; they are not copied to a server. Device-integrity checks run in memory and may record a verdict in the device log without message content.

Delete individual messages or conversations

  1. Delete one message. Open the conversation, long-press the message, and choose Delete.
  2. Move a conversation to Trash. On the conversation list, long-press the thread to enter selection mode, select one or more threads, and tap the Trash action. Confirm when prompted.
  3. Delete permanently. Open Trash from the conversation list, then use the delete action on a thread, or choose Empty Trash to remove every trashed thread. Confirm when prompted.

Moving to Trash is a soft delete and there is no restore action. Permanent deletion uses SQLite secure-delete and VACUUM to reduce recoverable remnants, but it does not guarantee forensic erasure from flash storage. Copies you have made outside the app, and copies held by recipients or your carrier, are outside the app's control.

Uninstall the app

To remove all app data:

  1. Open Android Settings → Apps (or Apps & notifications).
  2. Select Skandax Messages Shield (SMS). The package name is nexus.skandax.sms.
  3. Tap Uninstall and confirm. Alternatively, long-press the app icon and choose App info → Uninstall.
  4. If Shield is your default SMS app, Android will ask you to choose a new default SMS app. Messages that Shield had already moved out of the shared provider are not restored to another app.

What uninstall removes

  • The encrypted message database and all messages stored in it.
  • The database key material and consent flag in private app storage.
  • All other app preferences and local app data.

What uninstall does not remove

  • Messages or copies held by recipients, your carrier, or the SMS network.
  • Screenshots, clipboard contents or copies you made in other apps.
  • Any backup or snapshot you created outside the app. Shield disables Android app backup and device transfer, but it cannot control other backup tools you use.
  • Residual blocks on flash storage that may not be physically overwritten.

Before you uninstall

Uninstalling is permanent. There is no backup, no restore and no bulk export in the app. If you need to keep a message, copy it somewhere safe before you uninstall — for example, by long-pressing the message and copying it to another app or note. Also confirm that another SMS app is available if you still need to receive SMS, and re-grant any permissions that app needs.

Website and correspondence data

This website stores no cookies and no browser storage. Our static hosting provider may process standard request logs to deliver and secure the site, as described in the Privacy Policy. If you email us, your message and our reply are retained in our email systems for as long as needed to handle the enquiry and meet legal obligations. You can ask us to delete that correspondence at any time by writing to the Grievance Officer.

Deletion requests and timelines

Because we hold no app data, a deletion request is only meaningful for correspondence you have sent us. To make such a request, email the Grievance Officer at the address on the Contact & Grievance page. We will acknowledge within 7 business days and complete the request within 30 days, unless we are required by law to retain the correspondence. On-device deletion and uninstall take effect immediately and require no request to us.

Your rights

Under the DPDP Act, 2023 you have rights to access, correction, erasure, grievance redressal and nomination, and to withdraw consent. Since the app does not transmit data to us, you exercise these rights directly on your device, and the Grievance Officer is available if you need help. You can also escalate to the Data Protection Board of India. More detail is in the Privacy Policy.

Data Deletion & Uninstall · Last updated 7 November 2026 · App version 1.0 (Build 1)

Transparency · Website

Tracking & Cookies Statement

This website sets no cookies, uses no analytics and makes no third-party requests. Here is exactly what that means.

  • No cookies
  • No trackers
  • Last updated: 7 November 2026

The statement

This website does not set or read cookies. It does not use analytics, advertising, pixels, beacons, session replay, fingerprinting or any other tracking technology. It does not load fonts, scripts, images, styles or content from any third-party domain. There is no consent banner because there is nothing to consent to.

What this website does not use

  • First-party or third-party cookies of any kind.
  • localStorage, sessionStorage, IndexedDB or other browser storage.
  • Analytics platforms (including Google Analytics or privacy-focused alternatives).
  • Advertising networks, conversion pixels or retargeting tags.
  • Social-media plug-ins, embedded posts or share buttons.
  • Session-replay, heatmap or A/B-testing tools.
  • External fonts, icon fonts or CDN-hosted scripts and styles.
  • Embedded maps, video players or third-party forms.
  • Device fingerprinting, cross-site identifiers or advertising identifiers.
  • Contact forms or any mechanism that sends your input to a third party.

What happens technically when you visit

This is a static site. Your browser requests HTML, CSS, JavaScript and SVG files from sms.skandax.nexus, and those files are served by our hosting provider, Cloudflare Pages. Fonts are not downloaded at all: the site uses font families already installed on your device.

Our hosting provider may process standard technical request data — such as IP address, user agent, requested path and timestamp — to deliver the site, keep it available and defend it against abuse. We do not use that data to identify, profile or track visitors, and we do not have an analytics product layered on top of it. This processing is governed by the provider's terms and privacy policy as our data processor. See section 8 of the Privacy Policy.

Browser storage

The site writes nothing to your browser. There is no cookie, no local or session storage entry, no cache-based identifier and no service worker. Navigating between pages uses JavaScript's history API only, in memory, and leaves no trace after you close the tab. If you clear your browser data, nothing about this site will be lost, because nothing was stored.

No third-party requests

Every resource the site loads is served from this domain: /assets/styles.css, /assets/app.js, /assets/favicon.svg and inline SVG graphics. There are no external stylesheets, no external scripts, no analytics snippets, no embedded fonts and no third-party images. Links to other websites are not present in the page content; the only outbound links are the Google Play listing for the app and an email address, and each opens only when you choose it. Neither loads content on this page.

Email links

Contacting us uses an email address, not a web form. Using it opens your email application with a draft; nothing is transmitted until you choose to send it, and no tracking pixel is included in our replies.

Do Not Track and Global Privacy Control

Because this website does not track you, there is nothing to opt out of. The site behaves identically whether or not your browser sends a Do Not Track or Global Privacy Control signal. We do not sell or share personal information as those terms are used in applicable privacy laws.

The app itself

The Android app has no internet permission, no analytics and no crash-reporting component. It makes no network requests at all. Its tracking posture is therefore stricter than this website's, which still has to be served over HTTP by a hosting provider. Details are in the Privacy Policy and on the Security & Permissions page.

How to verify this yourself

  1. Open your browser's developer tools and go to the Network tab, then reload the page. Every request should be to sms.skandax.nexus.
  2. In the Application (or Storage) tab, check Cookies, Local Storage and Session Storage. They will be empty for this site.
  3. View the page source and search for "http". You will find only this site's own domain, the schema.org vocabulary identifiers used in structured data (which are strings, not requests), and the email address.
  4. Disable JavaScript and reload: all policy text is still present as plain HTML, and no tracking appears because there is none.

Changes to this statement

If the site's technical behaviour ever changes, this statement will be updated first, with a new last-updated date. We do not intend to add analytics or third-party resources, and we would not do so without prominently updating this page and the Privacy Policy.

Tracking & Cookies Statement · Last updated 7 November 2026 · sms.skandax.nexus

Transparency · Releases

Changelog

Public release history for the Skandax Messages Shield (SMS) app and this website. The version labels shown across the site are generated from this changelog.

  • Website v1.0
  • App v1.0 (Build 1)
  • Policy version 1.0

Every public release of the app and website is listed below, newest first. The current versions come from the same entry set that drives the version labels in the footer and in each page header.

The changelog is maintained in the project's CHANGELOG.md; the site's version and date labels are generated from it, so there is one place to update at release time.

Changelog · Last updated 7 November 2026 · sms.skandax.nexus

Company · Contact

Contact & Grievance

How to reach Skandax Nexus Pvt. Ltd., including our Grievance Officer for privacy, data-protection and security matters.

  • Skandax Nexus Pvt. Ltd.
  • India
  • DPDP Act 2023 · IT Act 2000

We do not operate a contact form, helpdesk or chat widget on this website, and the app has no support channel built into it. Please use email for all enquiries. Our static site sends nothing to us until you choose to send an email yourself.

Grievance Officer

For grievances under the DPDP Act, 2023 and the IT Act, 2000, including privacy concerns, data-principal requests and complaints about the app or this website.

Name
[Grievance Officer name]
Email
[Grievance Officer email]
Postal address
No. 3-1 / 7-33, Thiru VK Nagar, Chinnalapatti, Dindigul, Tamilnadu, India – PIN 624301
Response time
Acknowledgement within 7 business days; resolution within 30 days

Security reports

If you believe you have found a vulnerability in the app or this website, write to the Grievance Officer and mark your email Security report. We aim to acknowledge security reports within 5 business days.

Please do not include real message content, passwords or database keys. A description of the issue, affected version and reproduction steps is enough. Do not test against devices or accounts you do not own or have permission to use.

Data-principal requests

You can request access, correction, erasure or grievance redressal under the DPDP Act, and you may nominate a person to exercise your rights. Because the app does not send data to us, requests about message data are addressed directly on your device: delete in the app or uninstall it.

Email the Grievance Officer for any request concerning correspondence you have sent us.

Company details

Legal name
Skandax Nexus Pvt. Ltd.
Registered office
No. 3-1 / 7-33, Thiru VK Nagar, Chinnalapatti, Dindigul, Tamilnadu, India – PIN 624301
Jurisdiction
Dindigul, Tamilnadu, India
App
Skandax Messages Shield (SMS) · nexus.skandax.sms · v1.0 (Build 1)

Incubated at MaDeIT Foundation (Chennai), IIITDM Kancheepuram and TNAU Coimbatore, Tamilnadu, India.

What to include in your email

  • Your name and a reliable reply address.
  • The subject of your request: privacy, data-principal right, security, or general.
  • The app version (v1.0, Build 1), Android version and device model, where relevant.
  • A clear description of the issue or request, and any steps to reproduce it.

Never send us your actual message content, SMS database files, database keys, passwords or one-time codes. We do not need them to help you, and we do not want them.

Escalation

If you are not satisfied with our response to a privacy or data-protection grievance, you may escalate the matter to the Data Protection Board of India under the DPDP Act, 2023. Nothing in this page limits your right to approach a court, consumer forum or other competent authority under applicable law.

Response hours

We aim to respond to emails during Indian business hours (Monday to Friday, excluding public holidays) in English. Our acknowledgement and resolution targets are stated above and are goals rather than a guarantee of outcome.

Contact & Grievance · Last updated 7 November 2026 · Skandax Nexus Pvt. Ltd., India