Privacy Policy
This policy explains what data the Pasporo iPhone app ("the app") and its server process, why, who receives it, and how long it is kept. It applies to the app and to this website.
In short: we don't ask for your name, email address or phone number, and there is no sign-up form. The app identifies you with a random identifier it creates on your device. We store the SMS messages that arrive on the numbers you rent so we can show them to you, and we delete their content 30 days after the pass ends. We don't sell your data, we don't show ads, and we don't track you across other companies' apps or websites.
1. Who is responsible
The controller of your data is Naciye MEDENi, an individual developer. Contact: privacy@pasporo.com.
2. What we process
Identifiers
- App user ID. On first launch the app creates a random identifier and stores it in your iCloud Keychain, so your other Apple devices signed in to the same Apple ID can use the same account. It is not derived from your name, phone number or device hardware. We use it as your account ID on our server and as your customer ID at RevenueCat (purchases). We don't send it to Firebase Analytics or Crashlytics. It works like a key to your account, so the app never shows it and we never ask you for it.
- Support ID. A short ID derived from the app's random user ID by a one-way hash (computed the same way in the app and on our server) and shown in Settings → Support ID. It is not secret and can't be used to open your account; it only lets us find your passes and credits when you write to support.
- Firebase app instance ID. Created by Firebase Analytics for this installation of the app. We also pass it to RevenueCat so purchase events and app usage can be analysed together.
- Push tokens. If you allow notifications, Apple gives the app a push token, and for passes shown on the Lock Screen a Live Activity token. We store them to send you notifications about your passes.
- Session token. Our server gives the app a signed token so that its requests can be recognised. It is stored only on your device.
The app does not use the advertising identifier (IDFA) and does not ask for App Tracking Transparency permission.
Settings and device information
Your app language, time zone and app version, sent when the app starts. We use them to send notifications in your language and at the right time, and to keep the app compatible.
Purchases
Your purchases are processed by Apple. We receive transaction information from Apple and RevenueCat (product, transaction ID, date, price and storefront country, and refunds) but never your name, Apple ID or payment details. Our server keeps your credit balance and a ledger of credits added and spent.
Passes and the SMS messages you receive
- For each pass: the service you chose, the duration, the rented US phone number, when it started, was extended and ended, and the credits it used.
- The SMS messages that arrive on your rented number: the sender, the full message text, the code we detect in it, and when it arrived. This is the content of the service: we store it so the app can show it to you and notify you. The message is received first by our phone-number supplier, which holds the line, and passed to our server.
Messages sent to a rented number may contain personal data that you or the sending service put there. Please don't use a pass for anything you would not want stored as described here.
Usage data (Firebase Analytics)
Events about how the app is used, such as finishing the introduction, viewing the purchase screen, starting or completing a purchase, restoring purchases, receiving a code and being asked for a review, plus coarse device and app information (model, OS version, language, app version) and approximate country, which Google derives from your IP address. We use these to understand which parts of the app work and to improve it. Ad personalisation and Google signals are turned off.
Purchase screens and review prompts (our server)
Our server records, under your account, when a purchase screen or the first-purchase offer was shown and when the app asked you for a review. We use this only so the offer appears at most once a day and only before your first purchase, and so the app doesn't ask for a review too often. The purchase-screen records are deleted when you delete your account; see Delete your account.
Diagnostics (Firebase Crashlytics)
When the app crashes or hits a serious error: the stack trace, device model, OS version, app version, free memory and disk space, a Crashlytics installation ID and short notes about the steps before the crash (for example "purchase screen opened"). We use these only to find and fix bugs.
Previous version of the app
If you used an earlier version of this app and had unused credits, the app may send the Sign in with Apple identifier that version stored on your device, once, so we can carry the credits over. Our server never stores that identifier itself: it compares and keeps only a one-way hash (SHA-256) of it, linked to your app user ID, so the same credits cannot be claimed twice.
Support emails
If you email us, we receive your email address and whatever you write, and use them only to answer you.
Server logs
Like any web server, ours and its hosting provider see your IP address and basic request information (time, path, response status) when the app connects. We don't store your IP address in our database or link it to your account. Short-lived technical logs are used only for security and troubleshooting.
What we don't collect
Your name, email address (unless you email us), phone number, contacts, photos, precise location, advertising identifier, or the SMS messages on your own phone. The app never reads messages sent to your own number.
3. Why we process it (legal bases)
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Providing the app: your account, credits, passes, showing your codes, notifications | Identifiers, settings, purchases, passes and messages, push tokens | Performance of our contract with you (Art. 6(1)(b)) |
| Processing purchases and Apple refunds | Identifiers, purchases | Contract (Art. 6(1)(b)); keeping transaction records required by tax law (Art. 6(1)(c)) |
| Preventing fraud and abuse (for example claiming the same credits or first-purchase offer twice) | Identifiers, purchases, pass history, the hash described above | Our legitimate interest in protecting the service (Art. 6(1)(f)) |
| Fixing crashes and improving the app | Usage data, diagnostics | Our legitimate interest in a working, improving app (Art. 6(1)(f)) |
| Answering support requests | Email address and message | Contract (Art. 6(1)(b)) or legitimate interest (Art. 6(1)(f)) |
4. Who receives data
We use the following service providers. Each processes data only to provide its service to us.
| Recipient | What for | What it receives |
|---|---|---|
| Apple Inc. (USA) | In-app purchases, refunds, push notifications (APNs), iCloud Keychain sync of the app user ID | Purchase transactions (Apple already has them), push tokens and notification content, the app user ID in your Keychain |
| RevenueCat, Inc. (USA) | Purchase processing and validation | App user ID, Firebase app instance ID, language, time zone, app version, basic device and OS information, purchase transactions |
| Google LLC / Google Ireland Ltd. (Firebase Analytics, Firebase Crashlytics) | Usage analytics and crash reports | Firebase app instance ID, usage events, diagnostics, device information, IP address (used by Google for approximate country) |
| Hetzner Online GmbH (server in the European Union) | Hosting our server and its database | All server-side data described in section 2 |
| Our phone-number supplier(s) | Providing the US phone numbers used for passes and receiving the SMS sent to them | Which service and how long a number is needed, and the SMS sent to that number. We do not send them your app user ID or any other identifier of yours. The current supplier is named on request. |
We don't sell or rent personal data, and we don't share it for cross-context behavioural advertising. We disclose data to authorities only when the law requires it.
5. International transfers
Apple, RevenueCat and Google process data in the United States, and transfers to our phone-number supplier may also take place outside the EU, including the United States. Where data protection law requires it, these transfers rely on the EU–US Data Privacy Framework where the recipient is certified, or on the European Commission's Standard Contractual Clauses. Our own server is in the European Union.
6. How long we keep data
| Data | Kept for |
|---|---|
| SMS message content (text, sender, detected code) | Until 30 days after the pass ends, then deleted. Deleted immediately if you delete your account. |
| Rented phone number on a pass | Until 30 days after the pass ends, then removed from the pass record. Removed immediately if you delete your account. |
| Account data (language, time zone, app version, push tokens) | While your account exists. Removed when you delete your account. |
| Pass records without number or messages (service, duration, dates, credits used), credit balance and ledger, purchase and refund records | While your account exists and, after deletion, as long as tax and accounting law requires (up to 10 years) and to prevent fraud. They are linked only to the random app user ID. |
| Hash of the previous version's identifier | As long as the app is offered, to prevent double claims. |
| Firebase Analytics event data | No longer than 14 months. |
| Crashlytics crash reports | 90 days. |
| Support emails | Up to 2 years after the conversation ends. |
7. Deleting your account
You can delete your account at any time in the app: Settings → Delete account. What is deleted and what is kept is explained on Delete your account.
8. Your rights
Depending on where you live (for example under the GDPR, the UK GDPR, Türkiye's KVKK or US state privacy laws such as the CCPA), you may have the right to access your data, correct it, delete it, receive a copy, restrict or object to processing based on legitimate interests, and to complain to your data protection authority. To use these rights, email privacy@pasporo.com and include the Support ID shown in Settings, because we have no other way to find your data. We answer within one month. We will not treat you differently for using your rights.
9. Security
Connections between the app and our server are encrypted (HTTPS). The app user ID and session token are stored in the iOS Keychain. Access to the server and database is limited to the developer. No system is perfectly secure, but we work to protect your data and will tell affected users and authorities about a breach where the law requires.
10. Children
The app is not meant for children. It is not for anyone under 13 in the United States, or under 16 (or the higher age set by local law) where a higher age is required for consent to data processing. We don't knowingly collect data from children. If you believe a child has used the app, email us and we will delete the data.
11. Changes to this policy
If we change this policy, we will update the effective date above, and for important changes we will also tell you in the app.
12. Contact
Naciye MEDENi
Email: privacy@pasporo.com