Data Retention
Keep data only while there is a clear business, contractual, security, or legal reason to retain it.
What we run by default
Website inquiries
Lead information submitted through Mopshy forms is stored in Supabase as a business inquiry and should be removed when it is no longer needed for that purpose.
Client data
Retention for client workflows is defined by the engagement and the client's own data obligations.
Provider backups
Backup and deletion behavior can depend on the infrastructure provider and must be considered in the architecture.
Logs
Logging should capture enough information to operate and troubleshoot a workflow without collecting unnecessary sensitive content.
Deletion requests
Requests concerning Mopshy-held data can be routed through the published contact or privacy channels for review.
End of engagement
Return, transfer, deletion, and credential-revocation expectations should be part of the project handoff.
Free workflow review
Find the workflow worth automating next
Bring one process that is slow, repetitive, expensive, or leaking opportunities. We will map the current workflow, identify the bottleneck, and tell you whether automation is worth pursuing.
No obligation. If automation is not the right answer, we will say so.