Privacy Policy

Last updated: June 2026

At AnTextShare, we believe in frictionless, anonymous sharing. This Privacy Policy outlines what minimal information we process, how long we keep it, and how we ensure your data remains yours. By accessing or using our Service, you agree to this Privacy Policy.

1. Information We Do Not Collect

We pride ourselves on offering a tool that does not require you to surrender personal details. Because AnTextShare is designed to be completely anonymous and frictionless, we explicitly do not collect, require, or process:

  • Personal Identity Data: Names, Usernames, or Passwords (there are no user accounts).
  • Contact Information: Email addresses, physical addresses, or phone numbers.
  • Financial Data: Payment information or credit card data.
  • Persistent Tracking: Persistent device identifiers used for targeted advertising profiling.

2. The Data You Share (Text and Files)

When you use our service to generate a secure code for text or files, that payload data is temporarily stored on our secure cloud databases (hosted via Google Firebase). Here is exactly how we handle that payload:

  • 24-Hour Auto-Deletion: Every single piece of text and every file uploaded to our database is strictly time-stamped. All shared data is permanently and irreversibly deleted from our active servers automatically 24 hours after it is created. No exceptions.
  • Encryption in Transit: All data sent between your browser and our servers is encrypted using industry-standard HTTPS/TLS protocols to prevent interception.
  • Access Restrictions: Your data can only be retrieved by someone holding the exact, randomly generated 4-character code provided at the time of creation. We do not index shared contents, nor are they searchable on public search engines.

3. Live Code (Peer-to-Peer Sessions)

Our Live Code feature operates fundamentally differently from our standard text sharing to provide maximum privacy for sensitive development workflows:

  • Zero Server Storage: Live Code uses WebRTC technology to establish a direct, peer-to-peer (P2P) connection directly between your browser and your collaborator's browser.
  • End-to-End Encryption: The keystrokes and code you share during a Live Code session are encrypted end-to-end. The data never passes through, nor is it stored on, AnTextShare central databases. Once the browser window is closed, the session is gone forever.

4. Log Data and Analytics

Like almost all websites, we collect information that your browser sends whenever you visit our Service ("Log Data"). This Log Data may include information such as your computer's Internet Protocol ("IP") address, browser type, browser version, the pages of our Service that you visit, the time and date of your visit, and the time spent on those pages.

To improve our service, ensure uptime, and understand aggregate usage trends, we utilize select third-party analytics services:

  • Google Analytics: We use Google Analytics to track basic metrics (like total site visitors and page views). This data is aggregated and anonymized to help us understand general traffic patterns.
  • Firebase: We utilize Google Firebase for our secure database hosting. Their infrastructure complies with strict international privacy and security standards.

5. Cookies and Local Storage

We believe in keeping a clean footprint on your device. We use minimal local storage purely for functionality, not for personal tracking:

  • Theme Preference: We save a simple flag (e.g., 'dark' or 'light') in your browser's Local Storage to remember your preferred visual theme on your next visit.
  • Analytics Cookies: Third-party tools like Google Analytics may place cookies on your browser to measure site interaction, as per standard web practices. You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent.

6. Security of Your Data

The security of your data is important to us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While we strive to use commercially acceptable means (like TLS encryption and Firebase infrastructure) to protect your temporary data, we cannot guarantee its absolute security.

7. Changes to this Policy

We may update this Privacy Policy from time to time as we add new features or as legal requirements change. Since we do not collect email addresses, we cannot notify users directly of these changes. We encourage you to review this page periodically. Changes to this Privacy Policy are effective when they are posted on this page. Continued use of the service implies acceptance of the current policy.

8. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or how your data is handled, please do not hesitate to contact us directly at: