Privacy Policy

1. Our approach to privacy

Our approach is straightforward:

• your datasets and workspaces remain yours or your organization’s
• we process information to operate, secure, support, and improve Telene
• we do not sell personal information or Customer Content
• we do not use customer datasets for advertising or AI-model training
• Workspace Shares are created only when an authorized user deliberately creates one
• we aim to be candid about the capabilities and limitations of a private-beta service

2. Who operates Telene

Telene is operated by:

TELENEER
A sole proprietorship owned and operated by G B SOUNDAR SRIRAM
Thanjavur, Tamil Nadu, India

Privacy questions, requests, and grievances: privacy@telene.app

General questions and support: hello@telene.app

Security reports: security@telene.app

In this Policy, “Telene,” “we,” “us,” and “our” refer to TELENEER. “You” refers to a visitor, invited beta user, or authorized user of an organization.

3. Scope of this Policy

This Policy applies to:

• the Telene website and Telene Grid private beta
• account registration and authentication
• the private-beta waitlist
• projects, datasets, workspaces, analyses, and reports
• Workspace Shares
• Google and Microsoft integrations
• product telemetry and error monitoring
• transactional and business email
• feedback and support communications
• other Telene services that link to this Policy

It does not govern services operated independently by third parties, even where Telene links to or integrates with them.

4. Private-beta limitations

Telene Grid is currently a free, invitation-only private beta for users aged 18 or older.

The beta may contain errors, incomplete features, changing limits, data-format changes, availability interruptions, and storage or recovery limitations. Telene does not currently provide an uptime, support-response, backup, or recovery service-level commitment.

Telene may maintain backup and recovery copies for disaster recovery and service restoration, but these do not replace your own source files and independent copies.

You must maintain independent copies of source files and other important information.

During private beta, Telene is not intended for children’s data, regulated health information, payment-card information, authentication credentials, government-classified information, high-risk government identifiers, or other highly sensitive or specially regulated information prohibited by the Terms of Service.

5. Information we process

Account and identity information

When you register, sign in, or use Telene, we may process:

• name or display name and email address
• authentication and application user identifiers
• authentication provider, email-verification, and account status
• organization memberships, roles, and permissions
• private-beta access and plan information
• login, token, session, and OAuth-flow information
• account creation and update times

Telene does not store your plaintext account password. Password authentication is handled through Supabase Auth.

Organization information

If you use Telene through an organization, we may process its name and identifier, creator, memberships, roles, permissions, plan status, projects, and other organization resources.

Organization datasets are organization resources. Creator information records attribution and assists with management rules; it does not make an organization dataset the personal property of the member who created it. Organization owners and administrators may have elevated abilities to manage members and organization resources.

Customer Content

“Customer Content” means content submitted to, imported into, stored in, created through, or shared from Telene. It may include:

• uploaded, imported, or manually created data
• dataset names, descriptions, cell values, and row identifiers
• column names, schema, data types, profiles, transformations, and derived columns
• source and import metadata
• projects, workspace titles, descriptions, blocks, layouts, and settings
• statistical analyses, results, diagnostics, interpretations, charts, and visual information
• reports and report settings
• Workspace Share snapshots
• selected content imported from connected Google or Microsoft services

You or your organization retain rights in Customer Content. Telene processes it to provide the functions you request and for the limited operational purposes described in this Policy and the Terms of Service.

Storage of datasets and workspaces

Small datasets may be stored directly in PostgreSQL. Larger datasets may be compressed and stored in Cloudflare R2, with related metadata and storage references maintained in PostgreSQL.

Large-dataset uploads and downloads may use limited-duration signed links. In some flows, the dataset object travels directly between your browser and Cloudflare R2 rather than passing through Telene’s API as a complete request body.

Saved workspaces may contain dataset references, analysis blocks, statistical results, visual settings, layouts, and report information. Workspaces can be creator-private or visible to authorized organization members. Organization owners and administrators may have elevated management access as permitted by the product.

Operational telemetry

Telene records controlled operational metadata to understand feature use, reliability, errors, and performance. This may include:

• identifiers for the user, organization, session, and affected product resources
• feature and operation identifiers
• analysis category or method
• controlled status and error information
• operation timings and measurements
• application and build information
• browser, operating-system, device, viewport, locale, and timezone information
• country and, when available, approximate region derived from infrastructure information

This telemetry is not anonymous. It may associate activity with a user, organization, dataset, workspace, or other resource.

Telene’s telemetry system is designed to accept controlled metadata and allowlisted values. It is not intended to contain dataset cell values, dataset or file names, column names, request bodies, report text, or arbitrary Customer Content.

Error and performance information

Telene currently uses Sentry for browser error and performance monitoring. Sentry may receive page or application route information, browser and device context, application version, stack traces, technical error messages, performance timing, and a Sentry event identifier.

The current configuration disables session replay and default PII collection. Telene also aims to prevent authorization credentials, cookies, request bodies, and Customer Content from being deliberately sent to monitoring services.

Error-monitoring systems can sometimes receive unexpected technical context. We therefore do not promise that incidental personal or customer-derived information can never appear in an error report.

Feedback and support

If you submit feedback or contact Telene, we may process the feedback category, message, email address, application route and version, page title, limited contextual and browser information, an optional screenshot or attachment, and internal resolution notes.

Screenshots and attachments may contain information visible on your screen. Review them before submission and remove anything unnecessary. Do not send passwords, access tokens, prohibited sensitive data, or unnecessary dataset contents by email or through feedback.

Waitlist information

If you join the private-beta waitlist, we may process your email address, product interest, optional use case, signup source, and signup date and time. We use this information to manage invitations, communicate about beta access, and understand potential uses of Telene.

Transactional and business email

ZeptoMail is used to deliver automated account, authentication, security, and service-related messages through Telene’s Supabase authentication configuration. It may process recipient information, message content, delivery status, bounce information, timestamps, and related delivery and security metadata.

Zoho Mail hosts Telene’s business email, including messages sent to or from hello@telene.app, privacy@telene.app, and security@telene.app. It may process email addresses, message content, attachments, timestamps, and delivery, spam, malware, and security metadata.

Payment information

The current private beta is free. Telene does not currently use a payment processor for the beta and does not collect payment-card information through Telene Grid. If paid services are introduced, we will provide the relevant billing and provider disclosures before collecting payment information.

6. Browser storage

Telene uses browser storage to preserve sessions, working data, drafts, and preferences.

Local storage

Local storage may contain authentication access and refresh tokens, token expiration information, account information, the selected organization, session timing, and application or appearance preferences.

IndexedDB

Telene’s browser database may contain dataset descriptors, complete dataset working copies, unsaved local datasets, dataset view state, workspace descriptors, workspace drafts, and project session information.

This browser-local information may include Customer Content and may remain on a device after the corresponding server-side information is deleted.

Cookies

Telene may use temporary cookies during OAuth flows to associate an authentication response with the browser that initiated it and to protect the authentication process. Our providers may use cookies or similar technologies as part of their services.

Shared devices

If you use a shared or public device, sign out when finished, do not allow the browser to save credentials, and clear Telene site data where appropriate. Signing out may not remove every locally stored dataset working copy or workspace draft.

Deleting information from Telene’s servers does not automatically clear every browser or device containing a local copy.

7. How we use information

We process information to:

• create, verify, and authenticate accounts
• provide and administer private-beta access
• maintain sessions and manage organizations, memberships, and permissions
• store, retrieve, edit, and delete datasets and workspaces
• perform user-requested statistical analysis and generate visualizations and reports
• create and manage Workspace Shares
• import selected information from connected services
• deliver transactional and support communications
• operate, monitor, secure, and improve Telene
• enforce product and rate limits
• investigate failures, abuse, and security incidents
• provide support and review feedback
• comply with legal obligations and protect legal rights

We may use operational telemetry, error information, and feedback to understand and improve Telene.

We do not ordinarily inspect uploaded dataset contents for general product research, and we do not use them for advertising or AI-model training. Limited access may occur for user-requested support, security, deletion, legal compliance, or investigation of a specific technical problem.

Where consent is legally required, we will request it through an appropriate notice and affirmative action. Withdrawing consent may prevent us from continuing to provide features that require the relevant information.

8. Statistical analysis and AI

Telene Grid currently performs statistical and analytical operations through application code.

Statistical tests, predictive methods, summaries, visualizations, and Grid Analyst functions are not, by themselves, third-party generative-AI processing.

The current implementation does not send uploaded datasets or workspace content to OpenAI, Anthropic, Google AI, Microsoft AI, or another third-party generative-AI model provider.

Telene does not use customer datasets to train AI models.

If Telene later introduces external AI functionality that processes Customer Content, we will update this Policy and provide appropriate notice before enabling that processing.

9. Workspace Shares

An authorized user may create a Workspace Share from a saved workspace. A Workspace Share is a separate, frozen snapshot. It is not direct access to the editable workspace or underlying dataset, and it may not reflect later changes to them.

Link access

A Workspace Share may use an unlisted bearer link. Anyone who obtains the link may be able to access the snapshot. The absence of public indexing does not make a bearer link confidential.

Password-protected access

A user may add password protection. This provides an additional access control, but it does not protect the snapshot if both the link and password are disclosed together.

Aggregate and row-level sharing

Aggregate sharing is the default. Aggregate snapshots use a sanitization process intended to limit content to supported results and visual information.

An authorized user may explicitly choose to include individual observations or row-level results. The user must review the snapshot, confirm that they are authorized to share it, and ensure that it contains no information prohibited during private beta.

Expiration and revocation

A Workspace Share may expire or be revoked. Deleting its source workspace also makes the Telene-hosted share unavailable.

Revocation prevents subsequent access through Telene. It cannot recall screenshots, downloads, exports, or other copies made outside the service.

10. When we disclose information

We may disclose information:

• to providers needed to operate Telene
• at your direction, including through Workspace Shares and connected services
• to authorized organization owners or administrators as permitted by the product
• when reasonably necessary to comply with law or valid legal process
• to investigate fraud, misuse, or security incidents
• to protect Telene, users, or others
• to establish, exercise, or defend legal rights
• in connection with a financing, incorporation, reorganization, merger, acquisition, or transfer of the Telene business, subject to appropriate safeguards and notice

We seek to limit disclosures to what is reasonably required for the relevant purpose.

11. What we do not do

Telene does not:

• sell personal information or Customer Content
• provide uploaded datasets to data brokers
• use Customer Content for third-party advertising
• use uploaded datasets to market unrelated third-party products
• use customer datasets to train AI models
• currently send uploaded datasets to third-party generative-AI providers
• intentionally place dataset cell values or arbitrary Customer Content in first-party telemetry
• collect payment-card information during the free private beta

12. Service providers

Cloudflare

Cloudflare provides website and application delivery, production API infrastructure, network and security services, rate limiting, application monitoring and operational logging, and R2 object storage. It may process requests, network information, operational metadata, Customer Content, large-dataset objects, and feedback screenshots as necessary to provide these services.

Supabase

Supabase provides authentication and PostgreSQL database infrastructure. Telene’s primary PostgreSQL database is currently configured in the AWS US West region in Oregon, United States. Supabase does not host the entire Telene application. Production API traffic is ordinarily served through Cloudflare Workers.

Sentry

Sentry provides browser error and performance monitoring and may process the technical information described in this Policy.

ZeptoMail

ZeptoMail delivers transactional account, authentication, security, and service-related email.

Zoho Mail

Zoho Mail hosts Telene’s business email and processes support, privacy, deletion, security, and other correspondence sent to or from Telene’s email addresses.

Google

Google provides supported authentication and optional Google Drive and Google Sheets connections. When you use these features, Google and Telene process the identity, authorization, selected-file, and import information needed to perform your request.

Microsoft

Microsoft provides optional OneDrive and SharePoint connectivity. When you use these features, Microsoft and Telene process the identity, authorization, selected-file, and import information needed to perform your request.

Railway

Telene currently retains a secondary Railway application deployment that may be used as a fallback for operational rollback or recovery. Production API traffic is ordinarily served through Cloudflare Workers.

We may update this list when a provider materially begins or stops processing information for Telene. We do not treat a provider as current merely because Telene is evaluating it or because legacy code mentions it.

13. International processing

TELENEER operates from India.

Telene’s primary PostgreSQL database is currently hosted through Supabase in Oregon, United States. Cloudflare, Sentry, ZeptoMail, Zoho Mail, Google, Microsoft, Railway where retained, and other providers may process information in different countries according to their infrastructure and the feature used.

Information may therefore be processed outside your country and may be subject to the laws of the place where it is processed. Where legally required, Telene will use appropriate contractual or other safeguards for international processing.

The private beta is currently intended for selected invited users, including users in India, the United States, and Australia. Availability to an invited tester does not mean Telene is generally offered or supported in every jurisdiction.

14. Access to Customer Content

Telene does not manually review uploaded datasets as part of ordinary product operation.

Authorized personnel or service providers may access information where reasonably necessary to:

• provide support you requested
• investigate a reported incorrect result
• diagnose a storage or application failure
• process an authorized deletion or recovery request
• maintain or secure the service
• investigate abuse or a security incident
• comply with law or protect legal rights

Where practical, we first rely on controlled metadata, reproduction steps, and information you choose to provide rather than accessing raw Customer Content.

15. Security

Telene uses technical and organizational measures intended to reduce unauthorized access, disclosure, alteration, and loss. These measures include authentication, organization-scoped access controls, role and permission checks, limited storage access, Workspace Share protections, rate limiting, monitoring, validation, and controlled handling of deployment secrets.

Additional information is available on our Security page.

No system can guarantee complete security. Telene Grid is a private beta and should not be used for prohibited sensitive information or as the only copy of important data.

Report suspected vulnerabilities to security@telene.app.

16. Retention

We retain information according to its purpose and the state of the relevant account or resource.

Account information and active Customer Content may be retained while needed to provide Telene.

Datasets and workspaces moved to Trash remain stored so they can be restored. Telene does not currently promise an automatic Trash-expiration period.

Workspace Share snapshots may remain until revoked, expired, removed through the source-workspace lifecycle, or otherwise deleted.

Operational telemetry, security information, errors, feedback, and correspondence may be retained while reasonably needed to operate and secure Telene, investigate issues, provide support, document actions, resolve disputes, or comply with law.

Connector credentials may remain while a connection is active and may be removed or revoked when the connection or account is deleted.

Terms-acceptance records and limited legal or security records may be retained where necessary to document agreements, prevent abuse, resolve disputes, or comply with law.

When information is permanently deleted from active product systems, residual copies may remain for a limited period in backup or recovery systems. These copies are removed or overwritten according to the applicable backup-retention process, unless longer retention is required by law.

Telene has not adopted a fixed public retention period for every category. We will update this Policy as more specific retention schedules are established.

17. Backups and recovery

Telene may maintain periodic backup and recovery copies for disaster recovery, business continuity, and service restoration. Backup coverage, frequency, retention, and restoration capabilities may vary as the private beta develops.

Backup and recovery copies are separate from active product systems and are not intended as a user-accessible backup, archive, or version-history service. Telene does not guarantee that a particular dataset, workspace, account, version, or individually deleted item can be restored.

Information deleted from active product systems may remain for a limited period in backup or recovery copies and is removed or overwritten according to the applicable backup-retention process, unless longer retention is required by law.

Infrastructure providers may also retain temporary operational copies, caches, logs, or recovery data according to their systems. Telene does not control every provider’s internal deletion schedule.

Users must retain independent source files, exports, and copies of important information.

18. Deletion

Datasets and workspaces can be moved to Trash and, subject to authorization, permanently deleted.

Permanently deleting an R2-backed dataset removes its active database record and associated objects from active Cloudflare R2 storage. If required active-storage deletion fails, Telene does not report the dataset as permanently deleted.

Deleting a workspace revokes its active Workspace Shares. Permanently deleting it removes the workspace and associated Telene-hosted share records and snapshots from active product systems.

These permanent-deletion actions remove the relevant information from Telene’s active product systems. Residual copies may remain temporarily in backup or recovery systems as described in Section 17.

Deleting server-side information does not automatically remove browser-local working copies, drafts, downloads, exports, screenshots, or copies retained by Workspace Share recipients.

Self-service account deletion is not currently available during private beta. To request account deletion, email privacy@telene.app from the address associated with your account.

Before acting, Telene may verify your identity, control of the account, authority over an Organization, and whether Organization ownership or administration must be transferred.

Deleting an individual account does not necessarily delete Customer Content controlled by an Organization or needed by other authorized members.

We will respond and act within a reasonable period after verification, or within a shorter period where applicable law requires it.

Additional details are provided on the Data Deletion page.

19. Your choices and rights

Depending on where you live, you may have rights concerning your personal information. You may ask Telene to:

• confirm whether we process your personal information
• provide access to appropriate information
• correct inaccurate account information
• delete eligible information
• explain relevant processing
• provide a portable copy where required and reasonably available
• restrict or object to certain processing where applicable
• address a privacy grievance

Where applicable law provides, you may nominate another person to exercise relevant rights on your behalf.

You may also update available profile information, delete eligible datasets and workspaces, revoke Workspace Shares, disconnect Google or Microsoft, decline optional screenshots, stop using Telene, or request account deletion.

Send requests to privacy@telene.app. We may ask for information reasonably necessary to verify your identity and authority. We will not disclose another user’s or organization’s information in response to your request.

You may also have the right to contact the relevant privacy or data-protection authority in your jurisdiction.

20. Communications

We may send service-related messages concerning authentication and email verification, account security, private-beta invitations, important service incidents, requested support, organization administration, and material changes to the Terms or this Policy.

These are operational communications, not third-party advertising. If Telene later sends optional promotional messages, we will provide an appropriate way to opt out.

21. Users must be 18 or older

Telene Grid is limited to users aged 18 or older during private beta.

Telene does not knowingly permit children to create accounts. Customer Content containing children’s personal information is prohibited during private beta.

If you believe a child has provided information to Telene, contact privacy@telene.app.

22. Changes to this Policy

We may update this Policy as Telene, its providers, applicable law, or our data practices change.

We will update the effective date, make the current version available on the Telene website, provide appropriate notice of material changes, and request a new acknowledgment or acceptance where legally or contractually appropriate.

We will update this Policy before introducing a materially new use of Customer Content, such as sending customer datasets to an external generative-AI provider.

23. Contact and grievances

For privacy questions, rights requests, deletion requests, or grievances:

TELENEER
Owned and operated by G B SOUNDAR SRIRAM
Thanjavur, Tamil Nadu, India
privacy@telene.app

For general questions and support: hello@telene.app

For security reports: security@telene.app

Please include enough information for us to understand your request. Do not send passwords, access tokens, prohibited sensitive information, or unnecessary dataset contents by email.