Data Retention Policy
What data TurboSender stores, where it lives, how long it is kept, and how to permanently delete it.
Effective: March 1, 2026 · v1.0 · ViViD App Studio
1. Overview
TurboSender operates with a zero-server-storage policy. All user data is stored exclusively in chrome.storage.local â a sandboxed, local storage API specific to Chrome extensions. No user data is transmitted to or stored on ViViD App Studio's servers.
2. Data Categories and Retention
| Data Category | What's Stored | Location | Retention |
|---|---|---|---|
| Contact Lists | Phone numbers, names from CSV imports | chrome.storage.local | Until manually deleted or extension uninstalled |
| Message Templates | Saved message drafts and templates | chrome.storage.local | Until manually deleted |
| Campaign Settings | Delay, batch, country code preferences | chrome.storage.local | Until changed or extension uninstalled |
| Scheduler Entries | Scheduled campaign data and times | chrome.storage.local | Auto-deleted after campaign fires |
| Session Progress | Active campaign progress bar data | Browser memory only | Cleared when campaign ends or browser closes |
| Custom Variables | Variable names (custom1, custom2) | chrome.storage.local | Until changed in Settings |
3. Billing Data (Paid Plans)
If you subscribe to a paid plan, payment processing is handled by our payment provider. We retain only minimal billing confirmation data (transaction ID, amount, date) for subscription management, retained for 7 years as required by Indian tax law (GST records). No financial card data is stored by us.
4. How to Delete Your Data
- Within the Extension: Settings â Reset â Clear All Data
- Chrome Extensions Page: chrome://extensions â TurboSender â Storage section â Clear
- Uninstall: Removing the extension deletes all associated storage data automatically
5. Data Security
Data in chrome.storage.local is sandboxed (accessible only by TurboSender), protected by Chrome's extension isolation, and subject to your device's OS-level user account security. We recommend using device-level encryption (available in all modern operating systems) to protect extension storage data.