Version: 1.0
Effective date: August 25, 2026
Telene distinguishes between moving an item to Trash, restoring it, permanently deleting it, revoking a Workspace Share, deleting an account, and clearing information stored locally in a browser. These actions have different effects.
Telene Grid is a free, invitation-only beta. Some deletion processes, particularly complete account deletion, currently require manual verification and assistance.
1. Our approach to deletion
We believe deletion controls should be understandable and should not report success when required deletion has failed.
This page explains what currently happens when information is moved to Trash, restored, permanently deleted, revoked, or removed during the Telene Grid private beta.
2. Before deleting information
Before deleting important information:
- retain your original source files
- export or copy anything you may need later
- check whether other Organization members rely on the resource
- review active Workspace Shares
- consider whether local working copies remain on another browser or device
Permanent deletion is intended to be irreversible through the ordinary product controls. Telene does not promise recovery after permanent deletion.
Telene may maintain backup and recovery copies for disaster recovery and service restoration. These copies are not a user-accessible backup service, and Telene does not promise recovery of a permanently deleted dataset, workspace, account, or individual version.
You should retain independent copies of important information.
3. Dataset deletion
Moving a dataset to Trash
Deleting a dataset through the ordinary deletion control moves it to Trash.
While a dataset is in Trash:
- it is removed from normal active listings
- its database record remains
- inline dataset content remains in PostgreSQL
- associated active Cloudflare R2 objects remain, where applicable
- related storage references and metadata remain
- an authorized user may be able to restore it
- it continues to use storage until permanently deleted
Moving a dataset to Trash is not permanent deletion. Telene does not currently promise that items in Trash will be automatically deleted after a fixed period.
Restoring a dataset
A user with the required Organization permission may restore a dataset from Trash, subject to applicable product limits.
For a dataset stored in Cloudflare R2, Telene verifies that the required active-storage information is valid and that the associated active objects remain available before restoring it.
If required active storage is missing, invalid, or cannot be verified, Telene does not restore the dataset as though its contents were available.
Restoring a dataset does not necessarily reverse changes that occurred elsewhere while it was in Trash.
Permanently deleting a dataset
Permanent dataset deletion is restricted to Organization owners or administrators who also have the required dataset-deletion permission.
For an inline dataset, permanent deletion removes its record and inline content from the active PostgreSQL database.
For a dataset stored in active Cloudflare R2 storage, Telene requires deletion of the associated active R2 objects before completing deletion of the active database record.
If required active R2 deletion fails:
- Telene does not report the dataset as permanently deleted
- the active database deletion is not completed
- the dataset remains in Trash
- the user can retry or contact Telene for assistance
This ordering is intended to prevent Telene from reporting permanent deletion while required dataset objects remain in active storage.
Permanent deletion may also remove dependent application records associated with the dataset through database relationships.
Permanent deletion from active systems does not necessarily remove the same information immediately from retained backup or recovery copies. Residual backup copies are handled as described in Section 10 and are not ordinarily available through the product.
Telene does not promise recovery after permanent deletion.
Temporary and superseded objects
Some upload and update operations may temporarily create storage objects that are not part of the current active dataset.
Telene attempts to remove failed, abandoned, or superseded objects through operational cleanup processes. During private beta, Telene has not published a fixed retention schedule for every such object.
4. Workspace deletion
Moving a workspace to Trash
Deleting a workspace through the ordinary deletion control moves it to Trash.
While a workspace is in Trash:
- it is removed from normal workspace listings
- its saved workspace content remains in PostgreSQL
- an authorized user may be able to restore it
- its active Workspace Shares are revoked
Moving a workspace to Trash is not permanent deletion.
Workspace deletion, restoration, and permanent deletion are restricted to the workspace creator or an Organization owner or administrator and also require the applicable workspace-deletion permission.
Restoring a workspace
Restoring a workspace does not automatically reactivate Workspace Shares that were revoked when the workspace was moved to Trash.
If the user wants to share the restored workspace again, a new share or another deliberate sharing action may be required.
A restored workspace may refer to datasets that have changed, been moved to Trash, or been permanently deleted. Restoring the workspace does not recreate a missing underlying dataset through the ordinary product controls.
Permanently deleting a workspace
Permanent workspace deletion removes its record and saved content from the active PostgreSQL database.
Associated Telene-hosted Workspace Share records and snapshots are removed from active product systems through their database relationship with the workspace.
Residual copies of the workspace or related records may remain temporarily in retained backup or recovery copies as described in Section 10.
Permanent deletion cannot remove copies previously downloaded, exported, copied, photographed, screenshotted, printed, or otherwise saved outside Telene.
Telene does not promise recovery after permanent deletion.
6. Account deletion during private beta
Self-service account deletion is not currently available.
To request account deletion, email:
Please send the request from the email address associated with your Telene account. Do not send your password, access token, dataset contents, or prohibited sensitive information.
Verification
Before acting on a request, Telene may need to verify:
- your identity and control of the account email address
- the account affected by the request
- your authority to act for an organization
- whether other organization members depend on affected resources
- whether organization ownership must be transferred
- whether content belongs to you personally or to an organization
This verification helps protect users and organizations against malicious or unauthorized deletion requests. Telene will not ask you to provide your password or access token to verify a deletion request.
Organization resources
Deleting an individual account does not necessarily mean that every resource the person created should also be deleted.
Organization datasets, projects, organization-visible workspaces, and related resources may belong to or be controlled by the organization. Depending on the circumstances, Telene may:
- transfer organization ownership or administration
- remove the person’s membership
- retain organization resources for remaining authorized members
- remove or anonymize creator attribution where appropriate
- seek instructions from an authorized organization owner
Telene will not knowingly delete an organization’s shared resources solely because one member requests account deletion unless that person has the required authority.
Scope of an account-deletion request
Depending on the account and verified authority, the process may involve:
- the Telene application user and Supabase Auth identity
- organization memberships, ownership, or administration
- eligible projects and organization resources
- active PostgreSQL datasets and related records
- active Cloudflare R2 objects
- active workspaces, Workspace Shares, and snapshots
- Google or Microsoft connector credentials
- operational telemetry
- feedback and screenshots
- waitlist records
- support and privacy correspondence
- other records associated with the account
The exact outcome depends on organization ownership, other users’ rights, legal requirements, security needs, and the verified scope of the request.
Timing and confirmation
Telene will respond and act within a reasonable period after identity, authority, and scope are verified, or within a shorter period where applicable law requires it.
We may contact you if additional information or an organization decision is required.
Where practical, Telene will explain what the request covers, any Organization resources that must be transferred or retained, any information that cannot immediately be removed, when deletion from active Telene systems has been completed, and how retained backup or recovery copies are handled where relevant.
Information that may be retained
Even after an account-deletion request, Telene may retain limited information where reasonably necessary to:
- comply with legal, regulatory, accounting, or recordkeeping obligations that apply to the relevant information
- document Terms acceptance
- prevent fraud or abuse
- investigate security incidents
- resolve disputes or protect legal rights
- preserve a record that a privacy or deletion request was completed
Residual copies of account information or Customer Content may also remain temporarily in backup or recovery systems according to Section 10. These copies are retained for disaster recovery and service restoration, not for ordinary product access or unrelated use.
Retained information will not be used to restore ordinary product access or for unrelated advertising. Telene will seek to limit retained information to what is reasonably required for the relevant purpose.
7. Connected Google and Microsoft accounts
Disconnecting Google Drive, Google Sheets, Microsoft OneDrive, or SharePoint prevents future access through the disconnected Telene connection. Telene may revoke the applicable connector credential where supported.
Disconnecting a provider does not automatically delete Customer Content already imported into Telene. Imported datasets must be deleted separately through the relevant dataset or account-deletion process.
Disconnecting Telene does not delete the original file from Google or Microsoft. You may separately review and revoke Telene’s access through the connected provider’s account settings.
8. Browser-local information
Telene stores some information in the browser.
Local storage may contain authentication access and refresh tokens, token expiration information, account information, the selected organization, session information, and application preferences.
IndexedDB may contain dataset descriptors, complete dataset working copies, unsaved local datasets, dataset view state, workspace descriptors, workspace drafts, and project session information.
Deleting information from Telene’s servers does not automatically clear browser-local information from every device.
To remove local copies, you may need to:
- sign out of Telene
- close open Telene tabs
- clear site data for
telene.appthrough your browser - repeat these steps on every browser profile and device used with Telene
Clearing browser site data may remove unsaved working copies and drafts. Export anything you need first.
9. Other records
Feedback, screenshots, and correspondence
Feedback may include message content, an optional email address, application and browser information, an optional screenshot, and internal resolution notes.
You may request deletion of eligible feedback by contacting privacy@telene.app. Telene may need the feedback identifier, approximate submission date, email address used, or other information to locate the record.
Privacy, deletion, support, and security correspondence is processed through Zoho Mail. Transactional account email is delivered through ZeptoMail.
Some correspondence may be retained where reasonably necessary to complete or document a request, maintain an appropriate audit trail, investigate security or abuse, resolve a dispute, or comply with law.
Telemetry, error, security, and acceptance records
Deleting an account does not necessarily require the immediate removal of every operational or security record.
Telene may retain limited telemetry, error, security, and Terms-acceptance records where reasonably necessary to investigate incidents, detect or prevent abuse, understand service failures, protect users or Telene, document accepted Terms, comply with law, or protect legal rights.
Telene has not adopted a fixed public retention period for every operational or security category. More specific retention schedules may be introduced as the beta develops.
10. Providers and recovery copies
Telene uses infrastructure and service providers including Cloudflare, Supabase, Sentry, ZeptoMail, Zoho Mail, Google, and Microsoft.
These providers may temporarily retain operational logs, delivery records, caches, security records, error reports, temporary operational or recovery copies, correspondence, and information they must retain under their own legal obligations.
Telene does not control every provider’s internal deletion schedule.
Where Telene controls the relevant account or record, we will use available provider controls as appropriate to process a verified deletion request.
Deleting information from Telene does not delete information held independently in your own Google, Microsoft, email, browser, or device accounts.
Backups and recovery
Telene may maintain periodic backup and recovery copies for disaster recovery, business continuity, and service restoration. Coverage, frequency, retention, and restoration capabilities may vary as the private beta develops.
When information is permanently deleted, it is removed from Telene’s active product systems. Residual copies may remain for a limited period in backup or recovery systems and are removed or overwritten according to the applicable backup-retention process, unless longer retention is required by law.
Backup copies are not ordinarily available through Telene and are not intended to restore an individually deleted dataset, workspace, share, account, or version. Telene does not promise that a particular item or version can be recovered.
Restoration from a backup may require additional reconciliation before ordinary service resumes, including identifying information that was previously deleted from active systems.
Infrastructure providers may separately retain temporary operational or recovery copies according to their own systems and schedules. Telene does not control every provider’s internal deletion schedule.
Users must retain independent source files, exports, and copies of important information.
11. What Telene cannot delete or recall
Telene cannot delete information that it does not control, including:
- source files retained by a user
- copies stored on another person’s device
- downloads or exports made by a Workspace Share recipient
- screenshots, photographs, or printed copies
- information copied into another application
- files remaining in a connected Google or Microsoft account
- messages stored in a recipient’s email account
- browser-local copies on devices Telene cannot access
- information independently retained by a third party under its own authority or legal obligations
Revocation and deletion can terminate Telene-controlled access where supported. They cannot make every external copy cease to exist.
12. Unauthorized, malicious, or unclear requests
Telene may decline, delay, or seek additional verification for a deletion request where we reasonably believe that:
- the requester cannot verify control of the account
- the requester lacks authority over an organization or resource
- the request may be fraudulent or malicious
- acting immediately could harm another authorized user
- the request conflicts with a legal preservation obligation
- the requested scope is unclear
- additional information is reasonably necessary to identify the affected records
These safeguards are intended to protect users and organizations against unauthorized or accidental deletion. Where possible, Telene will explain what additional verification or clarification is needed.
13. Changes to deletion practices
Deletion processes may change as Telene Grid develops.
If a change materially affects how personal information or Customer Content is deleted, retained, or restored, Telene will update this page and, where appropriate, the Privacy Policy and Terms of Service.
We will not describe a planned deletion, backup, or recovery capability as currently available before it is implemented.
14. Contact us
For account deletion, privacy requests, or questions about this page:
TELENEER
Owned and operated by G B SOUNDAR SRIRAM
Thanjavur, Tamil Nadu, India
General questions and support: hello@telene.app
Security reports: security@telene.app
Please include enough information for us to identify and understand your request. Do not send passwords, access tokens, prohibited sensitive information, or unnecessary dataset contents by email.