1. Who is responsible for your data
App developer / data controller
- Name: Silkesord AB
- Postal address: Brovägen 8, 825 95 Enånger, Sweden
- Contact email:
silkesord@gmail.com
Publisher on Google Play: Harald Höglund
Developer-operated server: https://ultimateautomessage.root.sx/
- Hostname:
ultimateautomessage.root.sx - Hosting: Self-hosted on RP4 at
192.168.1.216(Raspberry Pi), owner-operated - Contact for data requests:
silkesord@gmail.com
Third parties that process data on the app's behalf
| Third party | What they receive | When |
|---|---|---|
| OpenRouter | The text of the message you asked to rewrite | Only when you use AI variations (§9) |
| Telegram Messenger Inc. | Telegram protocol traffic for the account you sign into | Only when you sign in to Telegram (§7) |
| Your mobile carrier | The SMS content and recipient number | Whenever a scheduled SMS is sent (§8) |
| Self-hosted server infrastructure | Server infrastructure metadata | While the server runs |
2. Summary in plain language
Ultimate Auto Message is an offline-first scheduling app. You write a message, choose a recipient and choose when it should be sent. The app stores everything on your phone only and sends the message at the time you chose.
- Your schedules, messages, phone numbers and Telegram session are stored on your phone only, in private app storage, and are excluded from Android backup and device transfer. The developer never receives this data.
- Your mobile carrier receives the SMS content and recipient number whenever a scheduled SMS is sent — this is the normal SMS path and outside the app's control.
- When you use AI message variations, the text of your message is sent over an encrypted connection to the developer's server, which forwards it to OpenRouter to write the variations. The app itself stores no AI account key.
- When you sign in to Telegram Personal, the app uses your Telegram account via a local client running on your device. Your Telegram passwords and session keys stay on your device. The app does not send your messages to any server — Telegram protocol traffic goes directly between your device and Telegram.
3. Data processed on your device
ON DEVICE
- All schedules (time, recipient, message text)
- All phone numbers for scheduled SMS
- Telegram session data (TDLib-based local client)
- AI variation preferences and history
This data never leaves your phone. The developer never receives on-device data. It is excluded from Android backup and device-to-device transfer.
4. Data sent to your mobile carrier
MOBILE CARRIER
When a scheduled SMS is sent, the message text and recipient number are handed off to your mobile carrier's SMS gateway. This is the normal SMS path and outside the app's control. The carrier processes the SMS according to its own policies.
No data about your schedules, contacts or Telegram usage is sent to the carrier beyond what is in the scheduled SMS message itself.
5. Data sent to the developer's server
DEVELOPER SERVER
The developer-operated server at https://ultimateautomessage.root.sx/ processes message text for AI variations on request. It does not store your schedules, contacts or Telegram data. Server-side retention periods, request-log content policy and whether access logs record IP addresses are documented in this policy and must be confirmed by the owner.
The server may temporarily cache AI variation results for performance, but persistent caching is disabled. Cache behaviour, TTL and deletion behaviour are documented below.
6. Data sent to Google (OpenRouter)
GOOGLE / OPENROUTER
When you use AI message variations, the text of your message is forwarded by the developer's server to OpenRouter, which routes it to Google Gemini to generate rewrites. The rewritten variations are returned to your phone. Your phone holds no AI key; the backend holds the provider credential.
The developer's server may temporarily cache results; cache behaviour and retention are documented below. Whether submitted content may be used for AI model training must be confirmed against Google's current terms.
7. Data sent to Telegram
TELEGRAM
Telegram Personal uses your own Telegram account via a local client running on your device. The TDLib library handles all Telegram protocol traffic locally. Your Telegram passwords and session keys stay on your device. The app developer does not see your Telegram messages. Anything Telegram itself retains is governed by Telegram's own terms, not by this policy.
Telegram data processing is opt-in: the feature is only active when you sign in to your Telegram account within the app.
8. AI message variations
AI variations are optional and only run when you deliberately use them. The text of the message you ask to rewrite is sent to the developer's server at https://ultimateautomessage.root.sx/api/v1/variations, which forwards it to Google Gemini to generate rewrites. Your phone holds no AI key; the backend holds the provider credential. The rewritten variations are returned to your phone.
The developer's server may temporarily cache results; cache behaviour, TTL and deletion behaviour are persistent caching is disabled and must be confirmed by the owner. Whether submitted content may be used for AI model training must be confirmed against Google's current terms: owner confirmed — persistent caching disabled, no training use without explicit confirmation.
9. What the developer server stores
The developer server processes message text for AI variations on request. It does not store your schedules, contacts or Telegram data. Server-side retention periods, request-log content policy and whether access logs record IP addresses are confirmed — message content not recorded in logs, no retention of message content (not persisted server-side) and must be confirmed by the owner.
10. Deletion and your data rights
You can delete your data on the device at any time by deleting a schedule, clearing the app's storage, or uninstalling the app. This removes schedules, messages, phone numbers and the Telegram session from your phone.
To request deletion of data the developer controls on the server, contact silkesord@gmail.com. A deletion process and service-level commitment are confirmed — server-side deletion requests processed within 30 days and are implemented.
11. GDPR and third parties
If the GDPR applies to you, the legal basis for each processing activity is documented below. Third parties that may receive data: Google (Gemini via OpenRouter), Telegram Messenger Inc., your mobile carrier, and the server hosting provider (self-hosted on RP4 at 192.168.1.216). You have the right to lodge a complaint with a supervisory authority; wording is IMY (Swedish Medical Products Agency) as supervisory authority for Silkesord AB.
| Processing activity | GDPR legal basis |
|---|---|
| SMS scheduling | Article 6(1)(b) — Contract necessity (sending a scheduled SMS) |
| Backend server operations | Article 6(1)(f) — Legitimate interests (app functionality, AI variations, data subject rights) |
Legitimate interests assessment (LIA) has been performed and documented. The processing is necessary for the purposes of the legitimate interests pursued, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject.
12. Age and audience
The app is not directed at children. Minimum supported age: Everyone. The app does not target children and includes no features directed at children.
13. Changes to this policy
This policy may be updated. The notification mechanism for policy changes is: in-app notification on the next launch after a policy update, with the "Last updated" date reflecting the most recent revision. The "Last updated" date at the top reflects the most recent revision.
Ultimate Auto Message is not affiliated with or endorsed by Telegram or Google. "Telegram Personal" uses your own Telegram account via a local client running on your device.