Known Limitations and Caveats
This article documents the current known limitations of the MessageFuture platform – things that are intentionally constrained, not yet implemented, or have edge-case behaviour worth being aware of.
1. Alive Check-ins – Scheduling Not Yet Live
The Alive Check-ins page is visible in the dashboard and surfaces UI elements for monitoring check-in status. However, the automated scheduling and triggering system behind it is not yet fully connected.
What this means: No check-in reminders are currently being sent, and no automated Guardian alerts are being triggered by missed check-ins. The feature operates with illustrative data for preview purposes only.
When this changes: MessageFuture will notify all users by email and in-app notification when Alive Check-ins go live. In the meantime, use the Guardian system to manage Timeless message delivery manually.
See What Are Alive Check-ins? →
2. Recipients Without an Email Address Cannot Receive Date-Scheduled Messages
Email delivery is the primary mechanism for date-scheduled messages. If a recipient contact has no email address on their record, the MessageFuture composer will automatically switch the delivery mode to Timeless and display an explanatory banner.
What this means: You cannot send a date-scheduled message to a contact who has no email address. The workaround is to add their email address to their contact record before composing the message.
Not affected: Timeless messages do not rely on email for delivery – they can be addressed to email-less contacts, because a Guardian triggers delivery manually.
See Choosing Your Recipients →
3. Email Address Is Immutable After Signup
The email address used when creating your MessageFuture account cannot be changed through the Settings page or any self-service flow. It is permanently tied to your Supabase authentication record.
What this means: If you signed up with an incorrect or outdated email address, you cannot update it yourself. Contact MessageFuture support for assistance.
Visible reminder: The email field in Settings → Profile is shown in read-only mode to make this clear.
4. Data Export and Account Deletion Are Web-Only
The Data Export and Account Deletion workflows are not available in the mobile app. They are exclusively accessible through the web dashboard at app.messagefuture.com.
What this means: Mobile app users who need to export their data or close their account must sign in via a web browser to do so.
See Data Export → | Account Deletion →
5. Cancelling a Delivery Does Not Refund Credits
Credits are deducted when a message is finalised (moved from draft to scheduled or timeless). If you subsequently cancel delivery – returning the message to draft status – the credits spent to finalise it are not refunded.
What this means: Think of credits as covering the cost of the storage and processing commitment, not just the act of sending. Draft as long as you like before committing.
See Editing and Cancelling a Scheduled Message →
6. The 4-Hour Delivery Cancellation Cutoff
Once a scheduled message is within 4 hours of its delivery time, editing or cancelling it may not prevent delivery. The scheduler processes messages on a tight cycle, and messages close to their window may already be queued for sending.
What this means: For the safest outcome, make any changes to a scheduled message well in advance – ideally more than 4 hours before the delivery time.
See Editing and Cancelling a Scheduled Message →
7. Push Notifications Are Mobile-Only
MessageFuture does not currently support browser-based push notifications on the web dashboard. All web alerts are delivered exclusively through the in-app notification bell (🔔).
What this means: Web-only users will not receive device-level alerts when a message is delivered or a Guardian takes an action. Check the notification bell regularly, or use the mobile app for push alerts.
See Notification Preferences →
8. Deleted Twins Cannot Be Recovered
Permanently deleting an AI Twin removes all of its data – including its personality settings, conversation history, and all access grants – with no recovery path.
What this means: If you are unsure whether you want to permanently remove a Twin, deactivate it instead. A deactivated Twin can be reactivated at any time without any data loss.
9. Timeless Message Storage Is Capped at 20 Years
Timeless messages are stored for a guaranteed maximum of 20 years from the date they are finalised. The expiry date (storage_expires_at) is set automatically at creation and is visible on the message detail screen.
What this means: A Timeless message created today will be stored until approximately 20 years from now. If a Guardian has not triggered delivery before that date, the message may become inaccessible. Plan accordingly – ensure your Guardians are actively engaged well before any long-term horizon.