Jaivik Kotadiya

Privacy Policy — ClipCode

Effective date: May 12, 2026 Last updated: May 12, 2026

This Privacy Policy describes how ClipCode (“we”, “our”, or “us”), developed by Oopsable, collects, uses, and protects information when you use the ClipCode mobile app and browser extension (collectively, the “Service”).

By using the Service, you agree to the collection and use of information as described in this policy.

1. Information We Collect

1.1 Information you provide directly

Data	When collected
Email address	When you create an account
Display name	When you create an account or sign in with Google
Profile photo URL	When you sign in with Google (if available)
Clipboard content (text, links)	When you send text or links through the app or extension
Files	When you upload files to share between devices

1.2 Information collected automatically

Data	Purpose
Pairing code	Assigned on first launch to identify your session; persisted per account
Device FCM token	Required to send push notifications to your device
Transfer metadata (timestamps, file type, file size, direction)	To display your transfer history
Daily upload usage (bytes uploaded)	To enforce plan limits
App lifecycle events	To update session activity (`lastActiveAt`)
Crash reports and diagnostics	To identify and fix bugs (via Firebase Crashlytics)
Screen navigation events	To understand feature usage and improve the app (via Firebase Analytics)

1.3 Guest mode

You can use ClipCode without creating an account (“Guest mode”). In guest mode, we assign an anonymous pairing code and store transfer data linked to that code only. Guest data is automatically deleted after 48 hours of inactivity.

1.4 Information we do NOT collect

We do not read your device clipboard without your explicit action (you must tap Send)
We do not track your location
We do not access your contacts, camera, or microphone
We do not serve advertisements or share data with ad networks

2. How We Use Your Information

To provide the Service — storing and syncing your transfers between your phone and browser extension in real time
To enforce plan limits — checking file size and daily upload quotas against your subscription tier
To send push notifications — notifying your phone when the browser extension sends a transfer
To maintain your account — linking your pairing code to your user account on sign-in
To improve the Service — using anonymised crash reports and navigation analytics to fix bugs and prioritise features
To process payments — your subscription is handled by Google Play Billing via RevenueCat; we do not store payment card details

3. Data Storage and Retention

Data type	Storage	Retention
Account info (email, name)	Firebase Firestore	Until you delete your account
Transfer text and links	Firebase Firestore	24 hours (Free) · 7 days (Pro) · 30 days (Premium)
Transfer files	Firebase Storage	Same as transfer retention above; deleted when the transfer doc is deleted
Guest session data	Firebase Firestore	48 hours after last activity
Crash and analytics data	Firebase (Google servers)	Per Google’s retention policy (up to 90 days for Crashlytics)
Payment events audit trail	Firebase Firestore	Retained for accounting and dispute resolution

All data is stored on Google Firebase infrastructure (servers in the United States and other regions per Google’s data centre locations).

4. Third-Party Services

ClipCode uses the following third-party services that may process your data:

Service	Purpose	Privacy Policy
Firebase (Google)	Authentication, database, file storage, push notifications, crash reporting, analytics	firebase.google.com/support/privacy
Google Sign-In	Optional social login	policies.google.com/privacy
RevenueCat	Subscription management and receipt validation	revenuecat.com/privacy
Google Play Billing	In-app subscription payments (Android)	policies.google.com/privacy

We do not sell your personal data to any third party.

5. Browser Extension

The ClipCode browser extension (Chrome / Firefox) connects to the same Firebase backend as the mobile app. When connected:

It reads transfers from Firestore in real time to display them in the popup
It writes transfers you send (text, links, files) to Firestore
It stores your pairing code and connection state locally in your browser (chrome.storage.local / browser extension storage)
It sends desktop notifications for incoming transfers

The extension does not access web page content unless you explicitly send text or a file using the send bar in the popup.

6. Data Security

We implement the following security measures:

All data in transit is encrypted via HTTPS/TLS
Firebase Security Rules restrict Firestore and Storage access — users can only read and write their own data
Subscription tier and billing fields can only be updated server-side via Cloud Functions; clients cannot modify them directly
Firebase App Check (Play Integrity API on Android) is enforced to prevent unauthorised API access
Release builds use code minification and obfuscation (ProGuard)

Despite these measures, no method of electronic storage or transmission over the internet is 100% secure. We cannot guarantee absolute security.

7. Children’s Privacy

ClipCode is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with personal information, please contact us and we will delete it promptly.

8. Your Rights

Depending on your location, you may have the right to:

Access the personal data we hold about you
Delete your account and associated data
Export your data
Withdraw consent at any time by stopping use of the Service

To exercise any of these rights, contact us at the email below. We will respond within 30 days.

To delete your account: Go to Settings → tap your account → Sign Out, then contact us to request full data deletion from our servers. We will delete all Firestore and Storage data linked to your UID within 7 days of your request.

9. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will update the “Last updated” date at the top of this document. Continued use of the Service after changes constitutes acceptance of the updated policy. We encourage you to review this policy periodically.

10. Contact Us

If you have any questions, concerns, or data deletion requests regarding this Privacy Policy, please contact us:

Email: jaivikkotadiya22@gmail.com Developer: Oopsable App: ClipCode (com.oopsable.clipcode.app)