Messaging status and scope
This is a release-pending review draft, not yet effective. It describes the revised app and backend, which await a coordinated release. The effective date will be assigned with that release. It does not confirm the behavior of an installed or production version. Publishing or opening this page does not record agreement or AI permission.
Tardy is operated by Michael Minh Nguyen and Aaron Nguyen for United States residents age 18 or older. Text Tardy and SMS digests are disabled in the revised app code. Production state has not yet been confirmed. This page explains historical messaging records and the separate permissions needed if messaging returns; it is not an enrollment form.
Separate connection and permission
Accepting the combined Terms/AI agreement does not connect a phone number, enable texting, grant calendar access, or enroll you in marketing messages. Text Tardy, event text reminders, SMS digests, and marketing must use the applicable separate connection and permission.
If texting becomes available, connect only a phone number or Messages address you control, and disconnect it before transferring it. Frequency varies, and carrier message or data rates may apply. A messaging connection or START message does not by itself establish the current Terms/AI permission. A return of the feature requires an accurate disclosure and an enforced permission flow.
Texting is not a reliable emergency channel. Delivery, timing, and availability depend on carriers, devices, providers, and connectivity. Message previews can expose coursework or calendar details on lock screens and linked devices.
Historical records and providers
Earlier linked accounts may retain encrypted sender bindings, planning snapshots, conversations, reminders, pending requests, delivery jobs, and operation receipts until cleared or deleted. Linq receives sender and recipient addresses, message content, and delivery information for Text Tardy. The disabled SMS digest feature used a separately supplied phone number and deadline summary with Twilio.
When separately connected and permitted, Text Tardy can send relevant message and Tardy context to the AI provider disclosed in the app. The revised release names DeepSeek’s direct API. Do not assume that accepting general Terms enables messaging or that a messaging connection alone grants AI permission.
Event text reminders, when separately enabled, use upcoming event titles and times through Linq without an AI call at delivery. Earlier requested reminders may retain titles, times, recipient bindings, and delivery state.
Messaging retention and calendar limits
An encrypted planning snapshot can let the server answer while the app is closed. Snapshots older than 24 hours are not used, but that freshness limit does not itself delete them. Conversation history is bounded to 24 messages and 32,000 UTF-16 units. Pending requests expire after 24 hours; results and operation receipts are bounded and may be cleaned during later activity. Delivery jobs have a 24-hour expiry. Expiry makes records eligible for cleanup, not guaranteed immediate deletion.
Changes that require the phone wait for the phone to execute them. Saved cloud events and their operation receipts are separate from messaging context and may remain until removed or the account is erased. Disconnecting texting does not necessarily delete those saved events.
Stopping messages, disconnecting, and deletion
For an existing linked connection, STOP pauses texts and clears waiting actions; it does not delete every shared snapshot, conversation, or saved cloud event. No HELP command or automated STOP confirmation is promised by this notice.
Disconnecting Text Tardy or deleting the account removes Tardy’s connection and shared messaging records. Signing out of the app does not disconnect a previously linked sender. Clearing local Ask history does not erase a separately retained server conversation.
Messages already delivered remain with recipients, in Messages, and with providers. A send already in progress may arrive. If the current app does not expose a legacy connection control, contact tardyadmin@tardyplanner.app or use account deletion. Deletion retries incomplete cleanup and does not promise immediate removal of provider or other-device copies.
If messaging returns, Tardy must confirm the production connection, permission, pause, and cleanup behavior before presenting these controls as available.
Questions or privacy requests?
Contact Michael Minh Nguyen and Aaron Nguyen at tardyadmin@tardyplanner.app.