Privacy Policy
Last updated: November 15, 2026
- Your files never go over the internet or through our servers: they travel directly from one device to the other, on your local network or over a direct Wi-Fi link between your devices. With Pro, only short messages between your own devices can go through our server (“Clipboard everywhere” text, or the invitation that gets one of your devices ready to receive), end-to-end encrypted: we cannot read them (section 2g).
- The app has no advertising identifiers. When it crashes, it sends a technical report to Sentry on its own, with no personal data: not your name, not your files, not your IP address (section 2i). It sends usage statistics, never your files: without an account, under a measurement identifier drawn at random on your device; with an account, linked to that account. On the store versions, it also contacts RevenueCat each time it opens, to count active users (section 5). You can turn both off in the settings (section 2h). On Android, with Pro, it uses Google’s notification service (Firebase Cloud Messaging) to wake one of your devices: the notification contains nothing of your texts or files (section 2g). A bug report only leaves your device if you send it yourself (section 2f). The website counts its visits anonymously, with no cookies (section 2b).
- The app collects one single piece of personal data: your email address, and only if you create an account (for your subscription, for the free days, or to link your devices together). The free tier asks for none. The only other exceptions: what beta testers gave us when signing up (section 2d), the address left on this website to be told when the app is out (section 2e), and what you put in a bug report (section 2f).
- EU users have full GDPR rights — contact us any time.
1. Who we are
GreySpace is developed and published by Fabien Chauveau, independent developer.
Contact: contact@getgreyspace.com
For any privacy-related inquiry, write to privacy@getgreyspace.com. We respond within 30 days.
2. Data we collect — and why
2a. Buying the subscription
When you purchase or subscribe to GreySpace Pro, your payment and email are processed by Stripe (our payment processor) — governed by their Privacy Policy. We do not store your card details or billing address.
Since September 2026, GreySpace no longer uses a license key: a subscription is tied to an account (section 2c). In practice:
- No license code is issued, entered or stored any more. The old alphanumeric code system has been removed from the product.
- To check that a subscription is active, the app sends over HTTPS to
api.getgreyspace.comyour session token and an installation identifier (a code created on your device, unrelated to your identity; on Android it is derived one-way from the identifier Android gives the app, and on iPhone it is kept in the keychain, so that reinstalling does not count as a new device), used to enforce the device limit. Nothing else. On iOS, macOS and Android, subscription status is additionally checked with the store through RevenueCat (section 5), which receives neither your email nor any payment details. - Logs of those checks are retained for 30 days (Cloudflare D1), then auto-deleted.
2c. GreySpace account (optional)
Since September 2026, GreySpace offers an account so your subscription follows you from one device to the next and, since version 3.0, so you can link your own devices together (“My devices”: they recognise each other with no code to copy). It is entirely optional. The free tier — including unlimited receiving, forever — works with no account, no email, and no personal data reaching us at all. An account is only created when you ask for one: when you subscribe, claim a subscription you already paid for or the free days, link your devices, or ask on this website to be told when the app is out (section 2e).
If you do create an account, here is exactly what is stored on our servers (Cloudflare D1, European Union), and nothing else:
- Your email address. It is the only personal data an account requires. It serves as your account identifier and lets us send your 6-digit sign-in code. It is never sold, never shared beyond the processors listed in section 5, and we only email you about your account — unless you asked to be told when the app is out (section 2e), which states exactly which emails you will get.
- Your device names and their platform (“Office PC”,
windows). You choose that name in the app — if it contains your first name, it is stored as-is. It exists only so you can recognise your own devices in the list and disconnect one. You can change it any time in settings. - An installation identifier per device (a code created on your device; on Android, derived one-way from the identifier Android gives the app, so your phone keeps its place after a reinstall), used to enforce the 5-device limit.
- Your subscription status: active or not, plan, end date, originating store. No payment details — we never see them.
- Last-activity timestamps (when each device last checked in: when the app opens and, if usage statistics are on, the first time you return to the app each day), to help you spot the one you no longer use and, as totals, to count returning accounts. Since version 3.0.4, turning usage statistics off also leaves this device out of this count: each check-in tells our server.
- Each device’s public key (the public half only: the private half never leaves the device’s secure vault). It lets your devices recognise one another. If you use “Clipboard everywhere” (section 2g), each device adds a second public key, used to encrypt the text meant for it.
- The notification token of an Android device, only with Pro and while its internet link is open (section 2g): it is used to wake the device when a message is waiting for it. It is deleted when the device signs out of the account or is removed from it, when the account is deleted, or as soon as Google reports it as expired.
- A QR-code linking request, when you link a computer by scanning the code it displays with your phone: hashes of the code, the computer’s name and platform. It is valid for 5 minutes and can be used once; it is deleted as soon as it has been used, otherwise by the next day at the latest.
- The free days, if you claim them: a hash of your email address (one-way: the address itself is not in it), the start and end dates, and the platform you claimed them from. This row is kept even after your account is deleted, so that the free days are only offered once per address (legitimate interest: preventing the same trial from being claimed again). During the free days only, this row also keeps a link to your account, so that we can email you the day before they end; the link is erased as soon as that email is sent, when the free days end, or when you delete your account.
- Usage statistics, unless you turned them off: the number, direction, size and outcome of your transfers, time spent in the app, the onboarding steps, your answer to “Where did you hear about us?”, signing in to the account, what happens on the subscription screen and the outcome of a purchase, along with the platform and app version (section 2h).
- Your answer to “Where did you hear about us?”, if you give one: the question is asked only once, right after the account is created (TikTok, Instagram, YouTube, Google, a friend, the app store or other), along with the date and the platform of the device that answered. It tells us which networks bring people to GreySpace, and is never used for advertising.
What is never stored: your password (there is none), your 6-digit code (only a hash is kept, for 10 minutes), and your session token (only a hash is kept server-side; the token itself lives solely in your device's secure vault — Keychain, Keystore or DPAPI).
Deleting your account is done from inside the app, in two taps: Settings → your address → “Delete my account”. Everything is erased from our servers immediately and irreversibly, except the hash of the free days described above. No email to write, no waiting period. An account created only for “Tell me when it’s out” is also erased by the unsubscribe link in every email. Note: this does not cancel your subscription, which is cancelled where you paid for it (Apple, Google or Stripe). See the dedicated account deletion page.
2b. Website (hosting and visitor statistics)
This website (getgreyspace.com) is hosted on Cloudflare Pages. Cloudflare may collect standard web server logs (IP address, browser type, referring URL) as part of their infrastructure security, subject to Cloudflare's Privacy Policy.
This website places no cookies and no identifier on your device, and uses no advertising pixels (no Google Analytics, no Mixpanel). To know how many people visit, where they come from and which download links get used, it relies on Umami Cloud (Umami Software, Inc.), a visitor statistics tool built for exactly that. That is why no cookie banner appears.
For each page view, Umami receives the page address (with its utm_ campaign tags, if any), the site you came from, your browser, operating system, device type, screen size and language. It derives your country, region and city from your IP address, without keeping that address. Page views are grouped per visitor through an anonymous hash, computed from the IP address and the browser and renewed every month: it is used to count visitors, not to know who you are. Clicks on download links, on the Discord link and on links to the pricing page are counted the same way, along with the page and the location of the button they came from (top or bottom of the page, for example), as well as the use of the “Send yourself the link” button, without the link sent or its recipient.
These statistics are used only to measure traffic on this website: they are never combined with your account, the app, or other websites. They are hosted in the European Union and kept for 6 months. To stop your visits from being counted at all, open getgreyspace.com/?notrack=1: your browser remembers that choice (repeat it on each browser and each device), and getgreyspace.com/?retrack=1 undoes it.
2d. Beta programme (only if you signed up)
Testers in the first phase signed up through a questionnaire (a Google Form). If you filled it in, here is what we keep (Cloudflare D1, European Union):
- Your email address, used to send you your beta access. That access code expired on July 31, 2026 and no longer grants anything.
- Your Discord username, if you gave it, to connect the GreySpace Discord server with the sign-ups.
- Your answers to the questionnaire: devices and software you use, how often and how large your transfers are, your current tools, your main pain point, and a link to your portfolio if you gave one. They are used to sort bug reports by platform.
Your answers also remain in the Google Form, on the developer's account, with the same retention period. None of it is sold or used for marketing.
This data is erased no later than 12 months after your last answer, or as soon as you ask at privacy@getgreyspace.com. It rests on your consent, which you can withdraw at any time the same way.
The Android closed test goes through a Google group (greyspace-testers): Google manages your membership, and your address appears in the member list, which is used only to give you access to the test on the Play Store. Leaving the group removes you from it.
2e. “Tell me when it’s out” (only if you signed up)
Until the app came out on Google Play (November 2026), the Download page let you leave your address to be told about that release (and, before the iPhone app came out, about the App Store one). You confirmed it with a 6-digit code, which created your GreySpace account (section 2c) — with no device, so nothing but your address. Here is what we keep (Cloudflare D1, European Union):
- Your email address, and the language to write to you in.
- The phones you ticked (Android, iPhone), and the dates of your sign-up and of the emails sent.
What you get, and nothing else: one email the day the app comes out in the store of each phone you ticked, then a single email introducing the Pro version, no sooner than a week later. Your address is never sold, never shared, never used for anything else.
Every email contains an unsubscribe link that erases your sign-up at once — and your account too, if that was all it was used for. Otherwise the sign-up is erased 12 months after the last email (or after signing up, if the app hasn’t come out yet), along with the account if it was never used in the app. It rests on your consent (GDPR art. 6(1)(a)), which you can withdraw at any time through that link or by writing to us.
2f. “Report a bug” (only if you send a report)
In the app, the “Report a bug” button (in Settings, and under every error message) opens a window to write to us. Nothing leaves your device until you tap “Send”, and you can read the full content first, with “See what is attached”. The report goes over HTTPS to api.getgreyspace.com, which stores it in the developer’s database (Cloudflare D1, European Union) and emails it to the developer. It contains:
- Your message and, if you give it, your email address so we can reply. If you are signed in, your account address is suggested: you can clear it.
- The place in the app you report from, and the text of the error shown at that moment.
- The GreySpace version, your device model and its operating system (for example “samsung SM-A375B, Android 16”), the language, and whether an account is signed in, with its tier (free or Pro). Never the name you gave your device.
- What the app did in the last few minutes (a technical log of 400 lines at most), unless you untick the box. It lives in memory only and is never written to your device. Before sending, the app masks your account name in folder paths, email addresses and sign-in tokens. File names stay: they often help understand the bug.
Without an internet connection, the report waits in the app (three at most) and goes out on the next launch. The server stores each report once (its random identifier prevents duplicates), so the developer can find it and track the fix, and deletes it automatically 12 months after receipt.
A report is used only to fix GreySpace and to reply to you. It is erased 12 months after it is received, or as soon as you ask at privacy@getgreyspace.com. It rests on your consent (GDPR art. 6(1)(a)): you choose whether to send, and what.
2g. “Clipboard everywhere” and the internet link between your devices (Pro, only if you use them)
With a paid or gifted Pro subscription (the free trial does not include it), your devices signed in to the same account can talk over the internet when they are not on the same network. This serves two purposes: carrying text copied on one of your devices to the others (“Clipboard everywhere”: the “Everywhere, even away from home” setting is on by default for a Pro account, and you can turn it off at any time in Settings); and, since version 3.0, letting one of your devices know that another wants to join it or send it files, so that it opens its direct Wi-Fi link (for example your PC getting your Android phone ready to receive). The files themselves never go that way: they then travel directly from one device to the other (section 4). To a device on the same network, the text still goes directly, with no server. The rest goes over the internet, through api.getgreyspace.com, at our host Cloudflare:
- End-to-end encrypted. Every message — a copied text, or an invitation carrying the name, password and hardware address of your PC’s direct network and the number and total size of the files to receive, but never their names — is encrypted on your device before it leaves, for the receiving device only (X25519 and AES-256-GCM), and signed by the sending device (Ed25519). Only the receiving device can open it: our server carries a box it cannot open, and we cannot read what is inside.
- What the server sees: the identifier of the sending device and of the receiving device (both on your account), the time and the size of the encrypted box. It uses them to hand the box to the right device, to check that your account is Pro and that the device has not been signed out, and to cap sending at 120 per hour per device (a count of the current hour’s sends, nothing more). Its technical log only records shortened identifiers, sizes and error codes, never the content.
- How long: the box is kept until the receiving device confirms it got it, and 10 minutes at most, then deleted automatically. The server only keeps the latest one per device: a new message replaces the previous one.
- Your devices’ public keys (section 2c): the sending device uses them to encrypt for the right recipient and to refuse a device that is not on your account. They stay with your account and are deleted with it.
- Waking by notification (Android): when a message is waiting for one of your Android devices that is not connected at that moment, our server has a notification sent to it through Firebase Cloud Messaging, Google’s notification service, at most once a minute. This notification contains nothing of your texts or files: only a signal asking the app to fetch the encrypted message. To receive it, the app asks Firebase for a notification token, which our server keeps with the device (section 2c). The app only contacts Firebase if your account is Pro and this internet link is open: on the free tier, no token is requested. In doing so, the Firebase SDK creates a Firebase-specific installation identifier and sends Google technical information (operating system version, device model, app version); Firebase’s audience measurement is turned off. Computers and iPhones do not use Firebase.
This link is only used to carry your messages from one of your devices to another. None of it is sold, analysed or shown to anyone. It rests on contract performance (GDPR art. 6(1)(b)): it is a feature of the Pro subscription you took out. On the free tier, the clipboard only travels between devices on the same network, with no server at all.
2h. Usage statistics
The app sends our server (Cloudflare D1, European Union) usage statistics: the number, direction and size of transfers, their outcome (completed, interrupted, declined…), time spent in the app, the onboarding steps, your answer to “Where did you hear about us?” (and whether a creator code was entered, without the code itself), signing in to an account (whether it was just created, and how: code sent by email, Google or Apple, or QR code), when the subscription screen and the offers that follow or precede it are opened (and from where), what is tapped on it (purchase, trial or free days requested, restore), the outcome of a purchase or of a free-days request (completed, cancelled or failed; monthly or yearly; with or without a trial; through the store, through Stripe or through our free days), when the free-days offer is shown, the store rating request and when a browser opens the receiving page (only that browser’s operating system), along with the platform and app version. Without an account, they are sent under a measurement identifier, drawn at random on your device at first launch and renewed at least every 13 months (a reinstall also draws a new one). It is distinct from the installation identifier of section 2a, is derived from no data about your device or you, it is never linked to your account or to a person, and it is used only to count installations and usage without an account. With an account, they are linked to that account, without this identifier; what the app noted before the account was created and had not yet sent goes with the account’s first batch. Never the names or contents of your files, your email address, your device names, your location or your contacts; your IP address is not stored with them.
We use them to improve GreySpace (spotting transfers that fail, or the step where people leave the onboarding or the subscription screen, for example), to help you if you write to us and, with an account, to contact you about your account. They are never sold or shared and are not used for any advertising. Legal basis: our legitimate interest in improving the service (section 6). You can turn them off at any time in Settings → Advanced → Usage statistics: the app stops sending anything and discards what was waiting to be sent. Those of an account are deleted with it; all of them are otherwise deleted after 13 months. Each night, our server derives daily totals from them (installations, active accounts, transfers, volume) that are not linked to any account or installation.
2i. Automatic crash reports (no personal data)
Since version 3.0.4, when an error makes the app crash or stops it from carrying on, it sends a technical report on its own to Sentry (Functional Software, Inc.), a service that specialises in tracking crashes. It is used only to see and fix the bugs nobody reports to us. The report contains:
- What happened: the type of error, its message and the list of GreySpace functions that were running, along with what the app was doing just before (going to the background, changing screens).
- The technical environment: the GreySpace version and its channel (store or website), the operating system and its version, the device model, its memory, its language and time zone, and other technical measurements (screen, battery, free space).
- Never: your email address, your account or a device identifier, your device’s name, the names or paths of your files, your IP or hardware addresses, your sign-in tokens, a screenshot, or the app’s log. Before sending, the app strips all of that from the report, error messages included: a file name becomes
<fichier>(“file”), a path<chemin>(“path”). A report is therefore tied neither to you, nor to your account, nor to your device, and is never used for advertising.
The report is sent over HTTPS. Like any server, Sentry sees the IP address of the connection, but does not store it with the report (a setting of our Sentry project). Reports are kept for 90 days at most, then deleted automatically. Sentry is a US company: processing may take place outside the European Union, under the European Commission’s standard contractual clauses and the EU–U.S. Data Privacy Framework, in which Sentry participates.
Legal basis: our legitimate interest (GDPR art. 6(1)(f)) in fixing GreySpace crashes. Test and development builds send nothing. Since a report contains nothing that could identify you, we cannot find the ones that came from your device; for any question, write to privacy@getgreyspace.com.
3. What we do NOT collect
- ❌ Your files — they travel directly from one device to the other, on your local network or over a direct Wi-Fi link, and never touch our servers
- ❌ Names, phone numbers, postal addresses.
The only exceptions, all explicit: your email address, if — and only if — you create an account (section 2c) or ask to be told when the app is out (section 2e), and what you gave us yourself if you signed up for the beta programme (section 2d), and what you put in a bug report (section 2f). Without an account and without a bug report, the app sends us literally no personal data about you. - ❌ Location data or GPS coordinates
- ❌ Contact lists or address books
- ❌ Advertising identifiers (IDFA, GAID)
- ❌ Session recordings (what you do on screen).
The app sends usage statistics, without any file name or content, which you can turn off (section 2h): under a measurement identifier drawn at random when you have no account, linked to your account when you have one. The website does count its visits, anonymously and with no cookies (section 2b). A bug report you send yourself attaches the log of the last few minutes, nothing more (section 2f). When the app crashes, it sends a technical report with no personal data (section 2i). - ❌ Hardware-bound device identifiers (IMEI, serial number, MAC address).
We do, however, generate an installation identifier: a code created on your device, unrelated to your identity. On Android it is not random: it is computed on your phone from the identifier Android gives the app, through a one-way fingerprint (the Android ID cannot be recovered from it and is never sent to us), so that your phone keeps its place among your devices when you reinstall the app. It is transmitted only if you use an account (subscription, free days, linking your devices), to recognise each of your devices and enforce the device limit. Usage statistics have their own identifier, the measurement identifier, drawn at random and distinct from this one (section 2h).
On Android, the weekly counter of the 2 GB of free sending is kept by our server, so that it does not reset when you reinstall the app. The server only receives an anonymous device fingerprint (computed on your phone from the Android ID, which is never sent to us), the month and the number of bytes sent. No account, no file name or content, no IP address. A row that has not changed for 100 days is deleted. Receiving is never counted. - ❌ Images from your camera.
Touch-free gesture: if you allow it, GreySpace uses your phone’s camera or your computer’s webcam to recognise your hand. Images are analysed on your device, one at a time, then discarded: they are never recorded or sent anywhere, neither to us nor to anyone. The camera only turns on when a gesture is possible, towards your own devices or your close contacts, and you can turn it off at any time in Settings.
4. Files: direct transfers only
File transfers in GreySpace are point-to-point, directly from one device to the other: on your local Wi-Fi or wired network, through a phone’s hotspot, or over a direct Wi-Fi link that one of your devices creates for the other (Wi-Fi Direct between Android phones; on a Windows PC, a network with a neutral name, DIRECT-Gs-…, and a password unique to that PC, given only to your devices). The two devices must therefore be within Wi-Fi range of each other. No file content is relayed through any external server, cloud service, or GreySpace infrastructure. You are in complete control of what gets transferred. The one exception, and it is never a file: with Pro, short end-to-end encrypted messages between your devices (“Clipboard everywhere” text, invitations) can go through our server (section 2g).
5. Data processors
| Processor | Purpose | Data shared | Policy |
|---|---|---|---|
| Stripe | Payment & subscription management | Email, payment info (at purchase only) | stripe.com/privacy ↗ |
| Resend | Sign-in and confirmation emails (6-digit codes), beta access emails, bug reports sent to the developer (section 2f), and “Tell me when it’s out” emails | Email address and, depending on the email: 6-digit code, beta access code, message text or the content of a bug report (section 2f) | resend.com/legal/privacy-policy ↗ |
| RevenueCat | Management of subscriptions bought on the App Store and Google Play, and number of active users of the apps downloaded from these stores (the app contacts it each time it opens, unless usage statistics are turned off) | Account identifier (UUID) or, without an account, a random identifier created by RevenueCat; subscription status; date of the last opening — never your email | revenuecat.com/privacy ↗ |
| Cloudflare | Website hosting, account API & account database, encrypted relay between your devices (“Clipboard everywhere”, invitations) | Server-level request logs, account data (section 2c), usage statistics, with or without an account (section 2h), beta-tester profiles (section 2d), bug reports (section 2f), “Tell me when it’s out” sign-ups (section 2e), anonymous counter of free sending on Android (section 3), encrypted messages between your devices, unreadable to us and kept 10 minutes at most (section 2g) | cloudflare.com/privacypolicy ↗ |
| Beta-tester questionnaire (Forms) and Android closed-test group (Groups) | Questionnaire answers, email address of group members (section 2d) | policies.google.com/privacy ↗ | |
| Google Firebase | Wake-up notifications for Android devices (Firebase Cloud Messaging), Pro only | The device’s notification token and Firebase installation identifier, technical information (operating system, model, app version). The notification contains nothing of your texts or files (section 2g). May be processed outside the European Union. | firebase.google.com/support/privacy ↗ |
| Umami | Website visitor statistics, no cookies | Page views, referring site, browser, OS, device, language, country and city (section 2b). IP address not kept | umami.is/privacy ↗ |
| Sentry | Automatic crash reports from the app (section 2i) | Cleaned error type and message, GreySpace functions that were running, app version, operating system, device model. No account, no device or file name, no stored IP address. May be processed outside the European Union. | sentry.io/privacy ↗ |
6. Your rights (GDPR — EU/EEA)
If you are located in the European Union or European Economic Area, you have the following rights under the General Data Protection Regulation (GDPR):
- Right of access — request a copy of data we hold about you
- Right to rectification — correct inaccurate data
- Right to erasure ("right to be forgotten")
- Right to restrict processing
- Right to data portability
- Right to object to processing
To exercise any of these rights, email privacy@getgreyspace.com. We will respond within 30 days.
You also have the right to lodge a complaint with your national data protection authority. In France: CNIL (cnil.fr).
Legal basis for processing: contract performance (GDPR art. 6(1)(b)) — subscription checks and account management exist to deliver the service you bought. The same goes for Clipboard everywhere (section 2g), a feature of the Pro subscription. The beta programme (section 2d) and “Tell me when it’s out” (section 2e) rest instead on your consent (art. 6(1)(a)), which you can withdraw at any time by writing to us — or, for the latter, through the link in every email. A bug report (section 2f) also rests on your consent: it only leaves if you send it. For free-tier users without an account, the app only sends usage statistics (section 2h), under a measurement identifier drawn at random that does not say who they are, the RevenueCat contact at opening on the store versions (section 5), both only if usage statistics are on, and crash reports with no personal data (section 2i), as long as they send no bug report. The right to erasure is exercised directly in the app (Settings → your address → “Delete my account”), with no need to write to us. Website visitor statistics (section 2b) rest on our legitimate interest (art. 6(1)(f)) in knowing how our own website is visited; you can object at any time through the link given in section 2b. Usage statistics (section 2h), with or without an account, also rest on our legitimate interest (art. 6(1)(f)) in improving the service; you can object at any time with the “Usage statistics” switch (Settings → Advanced). The same goes for the contact on the first return to the app each day, used to count returning accounts (section 2c), and for the RevenueCat contact at opening, used to count active users (section 5): legitimate interest (art. 6(1)(f)) in knowing how the app is used, and the same switch turns them off. Since version 3.0.4, it also leaves this device out of the count of returning accounts, including the contact at opening. Crash reports (section 2i) rest on our legitimate interest (art. 6(1)(f)) in fixing app crashes; they contain no data that could identify you.
7. Children's privacy
GreySpace is not directed at children under 13. We do not knowingly collect data from children. As we collect no personal data during normal use, this is already satisfied by design.
8. Data retention summary
- Subscription check logs: 30 days (Cloudflare D1, then auto-deleted)
- Purchase data: retained by Stripe per their policy (legal requirement)
- Account data (email, devices, their public keys and notification token, subscription status, answer to “Where did you hear about us?”): kept as long as the account exists, then erased immediately on deletion from the app; the notification token also goes as soon as the device signs out
- 6-digit sign-in codes: 10 minutes, stored as a hash, then deleted — a code that has been used is destroyed at once
- Sessions: a rolling 1 year, extended on each use; signing out deletes them on the spot
- Beta-tester profiles (beta programme questionnaire): erased no later than 12 months after the last answer, or as soon as you ask
- “Tell me when it’s out” sign-ups: erased on unsubscribing, otherwise 12 months after the last email sent; the account goes too if it was never used in the app
- Website visit statistics (Umami): 6 months, with no IP address
- Bug reports: 12 months after receipt, or as soon as you ask — on the server (automatic deletion) as well as in the developer’s mailbox
- Clipboard everywhere and invitations between your devices (Pro): an encrypted message, unreadable to us, waits 10 minutes at most on the server, then is deleted automatically
- QR-code linking requests: 5 minutes, single use; deleted as soon as they have been used, otherwise by the next day at the latest
- Hash of the free days (without the email address itself): kept after the account is deleted, with no time limit for now, so that the free days are only offered once per address. Its link to your account, kept for the email the day before they end, is erased as soon as that email is sent, when the free days end, or when the account is deleted
- Usage statistics: 13 months at most; those of an account are deleted with it; the measurement identifier is renewed at least every 13 months; the daily totals drawn from them are not linked to any account or installation
- Crash reports (Sentry): 90 days at most, then deleted automatically; no IP address, no account or device identifier
- Everything else: not collected, not retained
9. Changes to this policy
If we materially change our data practices, we will update this page and the "Last updated" date above. We will not add tracking or analytics without updating this policy first.
10. Contact
Questions or requests about your data:
privacy@getgreyspace.com