This Privacy Policy explains how TweetSMS (“we”, “us”, or “our”) collects, uses, stores, and protects information when you use our website and SMS messaging services at www.tweetsms.ps and related applications or APIs.
TweetSMS provides business and personal SMS sending tools, including account dashboards, contact groups, scheduled and variable messages, Excel/file uploads, sender IDs, billing/credits, support tickets, and API access. By using our services, you agree to the practices described in this policy.
Depending on how you use TweetSMS, we may collect:
We collect information when you:
We use the information we collect to:
When you send SMS through TweetSMS, you are responsible for the content of messages and for having a lawful basis to contact recipients (including consent where required). Message content and recipient numbers are processed to deliver the service you request and to generate delivery reports and usage history in your account.
We may process messaging metadata with telecommunications / SMS gateway partners as needed to route and deliver messages. Those partners may process data only to provide network delivery and related carrier services.
If you use the TweetSMS mobile application, we process additional data needed to run the app and deliver notifications:
Push notifications are delivered through Google’s Firebase Cloud Messaging service. To deliver a notification, your device token and the notification payload (title, body, and related fields such as notification type and sender name) are transmitted to Google, which routes the message to your device. Notification payloads may reference account activity — for example, that a send failed — so please bear in mind that previews can appear on a locked screen. We do not provide Firebase with your contact lists, and we do not use push data for advertising.
You can turn off push notifications at any time in your device settings or by signing out of the app. If you want the stored token deleted from our servers, contact us and we will remove it. Disabling notifications does not affect SMS sending or the rest of your account.
The TweetSMS mobile application uses Firebase Crashlytics, a Google service, to report crashes and stability problems so that we can diagnose and fix them. When the app crashes or hits a serious error, Crashlytics collects a diagnostic report that typically includes:
Crash reports are used only to investigate and fix stability problems. We do not deliberately include SMS message content, contact lists, passwords, or API keys in crash reports. Because a crash report captures the state of the app at the moment of failure, we cannot completely rule out that a diagnostic value contains data you had entered; any such data is used solely for debugging and for no other purpose.
Crash and diagnostic data is processed by Google acting as our service provider, and is retained for a limited period in line with Firebase’s retention practices. See Firebase’s privacy information for details of how Google handles this data.
We use cookies and similar technologies that are necessary for the service to work, including:
We do not use advertising cookies for third-party ad tracking on the TweetSMS site at this time. You can control cookies through your browser settings. If you disable cookies, some features (including staying logged in) may not work properly.
We do not sell your personal information. We may share information only in these cases:
We do not offer unrelated third-party products on our website for the purpose of transferring your personal information to marketers.
We retain account, messaging, billing, and support records for as long as needed to provide the service, maintain your history and reports, meet legal/accounting requirements, resolve disputes, and enforce our agreements. When data is no longer needed, we delete or anonymize it according to our operational practices, unless a longer retention period is required by law.
Push notification tokens are kept only while they are current: registering a new token replaces the previous one for your account, and we delete a token when you ask us to or when the provider reports it as no longer valid. Crash and diagnostic reports are retained by Firebase for a limited period as described in section 7.
We use administrative, technical, and organizational measures designed to protect personal information against unauthorized access, loss, misuse, or alteration. No method of transmission or storage is completely secure; please use a strong unique password and keep your login credentials and API keys confidential.
Subject to applicable law, you may:
To make a privacy request, email info@Tweetsms.ps. We may need to verify your identity before fulfilling the request.
TweetSMS is intended for business and adult users. We do not knowingly market to or collect personal information from children under 13. If you believe a child has provided us personal information, contact us and we will take appropriate steps to delete it.
If a personal data breach occurs that is likely to result in a risk to individuals, we will take reasonable steps to investigate, contain, and remediate the incident, and to notify affected users and/or relevant authorities as required by applicable law. Where feasible, we aim to provide notice within one business day of confirming a material breach affecting user personal data.
We may use your email address to:
We will not use false or misleading subjects or email addresses. To unsubscribe from non-essential emails, contact info@Tweetsms.ps and we will remove you from marketing correspondence.
We may update this Privacy Policy from time to time. The “Last updated” date at the top of this page will change when we do. Continued use of TweetSMS after an update means you accept the revised policy.
If you have questions about this Privacy Policy or our privacy practices, contact us:
Last updated: 15 August 2026