Privacy Policy | upplyst.ai

1. Who we are

upplyst.ai is a Swedish reading app for news and essays about AI and learning. You read a selection of articles, you can save the ones you want to come back to, and you can let the app notify you when something important is published. This policy describes what data we collect, how we use it, and what rights you have to that data. It covers the upplyst.ai app.

Developer: upplyst.ai
Contact: info@upplyst.ai

2. Delete your account

You can delete your account and all associated data directly in the upplyst.ai app:

Open the upplyst.ai app
Go to Settings
Tap Delete account
Confirm the deletion in the confirmation dialog

When you delete your account, the following data is removed permanently and immediately:

Your account and your profile settings
Your saved articles
Your reading history
Your device push tokens
The log of notifications sent to you

Deletion removes the account itself, and every record described above is tied to that account so that it is deleted with it. There is no retention period and the action cannot be undone. Deleting your account does not affect the articles themselves, which are editorial content and are not personal to you.

If you cannot access the app, you can request account deletion by emailing info@upplyst.ai from the email address linked to your account.

3. What data we collect

3.1 Account data

When you sign in with Google or Apple, we receive:

Data: Email address
Source: Google/Apple
Purpose: Account identification and sign in
Data: Name (optional)
Source: Apple (if provided)
Purpose: Display (if provided)
Data: Provider user ID
Source: Google/Apple
Purpose: Link the sign in to your account

We do not request access to your contacts, calendar, photos, or other services at Google or Apple.

3.2 Reading data

The app stores which articles you have saved and which ones you have opened, so that your saved list works and so that the app can separate what you have already read from what you have not:

Data: Saved articles (article reference and when you saved it)
Purpose: Show your saved list across sessions and devices
Data: Opened articles (article reference, first and most recent time opened)
Purpose: Mark what you have already read, and tell you when you have read everything in the selection

We record that an article was opened, and nothing about how you read it. There is no reading percentage, no time spent, no scroll depth, and no reading streak. We do not build an advertising or interest profile from what you read, and we do not share your reading data with anyone.

3.3 Settings

Data: Notifications on or off
Purpose: Your choice to receive notifications
Data: Time zone (read automatically from the device) and a delivery time
Purpose: Make sure a notification is only sent at a reasonable local hour
Data: Language preference
Purpose: Stored for future use. The app is currently Swedish only and offers no language choice
Data: Theme preference
Purpose: Light/dark/system (stored locally on your device only)

3.4 Device data (for notifications)

Data: Push token (Expo)
Purpose: Deliver push notifications
Data: Platform (iOS/Android)
Purpose: Platform specific notification handling
Data: When the device was last seen
Purpose: Send only to devices still in use

Push tokens are device identifiers used to route notifications. They are linked to your account only to deliver notifications. A push token identifies an app installation, so if another account signs in on the same device, the token moves to that account. Notifications are delivered through the Expo push service, which in turn routes them through Apple Push Notification service (APNs) on iOS and Google Firebase Cloud Messaging (FCM) on Android. These transports receive your push token and the notification title and body in order to deliver the message.

3.5 Notification history

When a notification is sent to you, we store a record of it: your account, the type of notification, which article it was about, when it was sent, and whether the delivery succeeded. We need this record for two reasons. It stops the same article from being sent to you twice, and it lets us detect a device token that no longer works so we can stop sending to it. The record includes the delivery ticket identifiers returned by the push services for the same purpose.

3.6 Diagnostic data

We use Sentry for crash and error reporting. Sentry receives error messages, stack traces, basic device information (device type, OS version, app version), and the sequence of screens you visited before the error, which helps reproduce it. Authentication headers, tokens, and request bodies are redacted before any data is sent, query strings are stripped from request URLs, and we do not attach any user identity to the reports. Sentry also counts app sessions so we can see how often a release crashes. Crash reports are processed in Sentry's EU region (Germany). Diagnostics are sent only from the production build of the app, not during development.

We use no analytics or advertising SDKs. If we add analytics in the future, we will update this policy and our App Store privacy details.

4. How we use your data

We use your data to:

Provide the app's features (reading, saving articles, seeing what is new)
Store and sync your saved articles and reading history across sessions and devices
Send notifications about new articles (only if you enable notifications)
Maintain account security and prevent abuse
Find and fix crashes

We do not use your data to:

Target ads or marketing
Build an interest or advertising profile
Sell data to third parties
Train AI models

Which articles appear in the app is an editorial selection, the same for every reader. It is not personalized from your reading data.

5. Third party services

We use the following services to run the app:

5.1 Supabase (database and authentication)

Purpose: Authentication and storage of your app data
Data processed: Account data, settings, saved articles, reading history, device tokens, notification history
Provider policy: https://supabase.com/privacy
Hosting region: Europe (Stockholm)

5.2 Expo Push Notifications (with APNs and FCM)

Purpose: Deliver push notifications
Data processed: Push token, platform, and the notification content (title and body)
Transport: Expo forwards the notification through Apple Push Notification service (APNs) on iOS and Google Firebase Cloud Messaging (FCM) on Android. FCM is used solely as a transport for notifications, not for analytics.
Provider policies: https://expo.dev/privacy, Apple, Google Firebase

5.3 Google (sign in)

Purpose: Authentication only
Data received: Email and basic profile information
We do not access: Gmail, Drive, Calendar, Contacts
Provider policy: https://policies.google.com/privacy

5.4 Apple (sign in)

Purpose: Authentication only
Data received: Email (may be a private relay address) and name (if provided)
Provider policy: https://www.apple.com/legal/privacy/

5.5 Sentry (crash reporting)

Purpose: Crash and error reporting to improve app stability
Data processed: Error messages, stack traces, screens visited before the error, device type, OS version, app version, and app session counts. Authentication headers, tokens, and request bodies are redacted before they are sent. No user identity is included.
Processing region: EU (Germany)
Provider policy: https://sentry.io/privacy/

6. Data retention

We keep data for as long as needed to provide the service:

Data type: Account data and settings
Retention: Until you delete your account
Data type: Saved articles
Retention: Until you remove them, or until you delete your account
Data type: Reading history
Retention: Until you delete your account
Data type: Notification history
Retention: Until you delete your account
Data type: Push tokens
Retention: Until the token is replaced or moves to another account, or until you delete your account
Data type: Crash reports
Retention: Per Sentry’s retention period, with no user identity attached

When you delete your account, the associated app data is deleted with it, as described in section 2.

7. Data security

We use established security practices, including:

Encryption in transit (HTTPS/TLS)
Row level security in the database, so a signed in reader can only read and write their own saved articles, reading history, settings, and devices
OAuth based authentication (Google/Apple)

Session tokens may be stored locally on your device. If your device is compromised (for example jailbroken or rooted), an attacker could access locally stored session data.

8. Your rights

8.1 Access and control

You can see your saved articles in the app, and the app shows you which articles you have already read. You can remove a saved article at any time.

8.2 Delete your account

You can delete your account in the app via Settings > Delete account. This removes your account and the associated data from our systems.

8.3 Manage your settings

You can update your settings and notification choices at any time.

8.4 Data portability

If you would like a copy of your data, you can contact us at info@upplyst.ai and we will help you.

8.5 Withdraw notification consent

You can turn off notifications at any time in the app settings or in your device settings.

9. Children's privacy

upplyst.ai is not directed to children under 13. We do not knowingly collect personal data from children under 13. If you believe a child has provided data, contact us for removal.

10. International data transfers

Our service providers may process data in different countries depending on their infrastructure and how our project is configured. Supabase for this project is hosted in Europe (Stockholm) and Sentry processes diagnostic data in Europe (Germany). Push notifications are routed through Apple (APNs) and Google (FCM), which may process your push token outside the EU. If you have questions about where your data is processed, contact us at info@upplyst.ai.

11. Changes to this policy

We may update this policy from time to time. We will update the "Last updated" date above. Continued use of the app after changes means you accept the updated policy.

12. Contact

For privacy questions or requests:
Email: info@upplyst.ai