Privacy
Samepaste moves what you copy between your own devices. That content never comes to me or anyone else. This page lists everything that does leave your devices, and how to stop it.
What you copy
Copied text and pictures travel between your own devices and are never stored on a server I run. Copies an app marks as sensitive, such as a password manager’s, are not sent at all.
History on your devices
Each of your devices keeps its own history of what passed between them, so you can paste an older copy again: by default the last 7 days and at most 100 items (you can choose 1, 7 or 30 days and 50, 100 or 500 items). Older items are deleted on their own, and Settings › Clear now empties the history of that device. The history stays on your devices; it is never sent to me or stored on a server.
To make photos and screenshots searchable, each device reads the text in them itself (on the phone or tablet only while charging with the screen on; on the PC with Windows' own text recognition). That text stays on the device it was read on: it isn’t sent to your other devices or put into statistics or diagnostics. Copies marked as sensitive are not kept in the history.
App statistics, only if you say yes
The phone app and the PC program ask once whether to send usage statistics and crash reports, with two buttons of the same size and neither picked for you. Nothing is sent before you choose. You can change it in settings at any time; turning it off stops sending at once and drops anything not yet sent.
If you say yes, only the events below are sent. Every field is a fixed word or a range, never free text, and counts go once a day rather than per copy.
| Name | When | Fields |
|---|---|---|
onboarding_step | A first-run step starts | step: notifications, photos, overlay, battery, login, stats, done |
login_result | Sign-in finishes or is abandoned | result: ok, cancel, other_account, error |
devices | Once a day | total, phones, tablets, pcs: 0–9, 10+ |
daily_usage | Once a day, for the day before | text_sent, image_sent, photo_auto, received: 0, 1–5, 6–20, 21–50, 51–100, 100+; delay_p50, delay_p90: ~0.5s, ~1s, ~2s, ~5s, 5s+; relay_share: 0, ~25%, ~50%, ~75%, 100% |
problem | A problem is shown on screen | kind: other_account, battery_restricted, login_expired, blocked_by_rules, relay_only, offline_long |
plan_event | When it happens | kind: limit_reached, trial_started, device_resting, paywall_opened, purchase_done, restore_done; from: notification, tile, home, settings, pc_window |
feature_used | Once a day, only what was used | name: history, search, pin, send_now, send_mode_auto, send_mode_button, send_mode_off, receive_off, full_auto |
app_error | A caught error (Windows) | where: the module’s name; code: a fixed error name |
Never sent with statistics: what you copied, its exact length or size, text inside pictures, device names, your Google account or email address, phone numbers, precise location (GPS or street address), advertising ID, error message text. Crash reports carry only where the crash happened and its kind. Google estimates roughly the country and region from the connection’s IP address but does not store the IP; Google Analytics' granular location and device data collection is off in every region.
Recorded automatically by Firebase
Android only, and only after you chose to send statistics (before you are asked, or if you say no, Firebase collection is off). These records are added by the Firebase Analytics SDK itself, not chosen by our code, and never contain what you copied. Automatic screen-name logging (screen_view) is turned off.
| Name | When | What it holds |
|---|---|---|
first_open | The app is opened for the first time | Firebase’s standard fields (app version, time) |
session_start | You start using the app | a session number |
user_engagement | While you use the app | time on screen (ms) |
in_app_purchase | You buy Pro on Google Play | product ID, name, price and currency (no card details) |
This website’s statistics
When visit statistics are on (see below), this site counts the following with Google Analytics 4. Every value is a fixed word from the lists below, never anything you typed or copied. The home page shows its use scenes in a carousel; the scene it starts on is picked at random for each visit, and that scene’s id is added to these events as first_scene.
| Name | When | Fields |
|---|---|---|
page_view | A page opens | page address, language, the page you came from |
cta_click | You press a download or notify button | store: windows, apk, play, notify; place: hero, end, scene, install |
scene_view | A use scene sits mostly in the middle of the screen for over a second (once per scene); in the home page carousel, only the scene in front | scene: lecture, address, search, otp on the home page; otp, photo_ai, link, tablet_note on the use pages |
scene_leave | That scene then leaves the middle of the screen or the front of the carousel (once) | scene; dwell: <3s, 3–10s, 10–30s, 30s+ |
scene_pick | You pick a scene in the home page carousel yourself | scene; how: bar (the progress bars), arrow (a side card or the arrow keys), swipe |
download_click | You press a download or store button | store: windows, apk, play; last_scene: the scene seen last, or none |
lang_switch | You change the language | to |
scroll | You reach 90% of a page | percent_scrolled: 90 |
LCP, INP, CLS | When you leave a page | how fast the page loaded and responded, as numbers |
user_engagement | Sent by GA4 on its own when you have spent time on a page or leave it | time on the page (ms) |
first_visit, session_start | Sent by GA4 on its own: marks on the first page view of your first visit and of each visit, not separate requests | no fields of their own |
Google Analytics also records the browser, the type of device and an approximate country and city worked out from the connection; it does not keep IP addresses. Advertising features, Google signals and ad personalisation are off and ad data is redacted. The _ga cookie, holding a random ID, is set only while statistics are allowed. Where the site asks first, it loads nothing from Google until you allow it.
Who receives what
- Google (Firebase Analytics, Crashlytics, Google Analytics 4): the app’s, the PC program’s and this site’s statistics and crash reports above, in one place.
- Google Play: your purchase when you buy on a phone. Google handles the payment.
- Paddle: your purchase when you buy on a PC. Paddle is the seller of record and handles payment, tax and receipts.
- RevenueCat: a record of what you bought, filed under a value made from your Google account instead of the account itself, so Pro works on every device signed in with that account.
- Tailscale Inc., the connection service inside the app: when a device signs in, your Google account email, the device’s name and its IP address, so your devices can find each other. Never what you copy: devices connect directly and encrypted, and when a direct link isn’t possible the traffic passes through Tailscale relays still encrypted, so they cannot read it.
- GitHub: hosts this website and the downloads. Like any web server it receives your IP address and browser details when you open a page or download a file, under GitHub’s own privacy statement. The fonts on this site are served from it too, so no font service sees your visit.
How long it’s kept
Statistics are kept for 14 months, then deleted. Purchase records stay with Google Play, Paddle and RevenueCat for as long as the purchase and the law require.
If you emailed to be told when Samepaste is out, your address is used for that one reply only, and I delete those emails once I’ve replied.
How to turn it off
- App and PC program: the statistics switch in settings.
- This website: the button at the bottom of every page. The choice is kept in this browser, and after you turn statistics off no statistics requests are sent.
- In the EU and EEA, the UK and Switzerland, and whenever the browser doesn’t tell which region it is in, the site asks first and loads nothing from Google Analytics until you allow it.
Contact
Questions, or a request to delete data: philaxis.dev@gmail.com