Privacy Policy
The short version: Rize uses account details to provide your account, Apple and RevenueCat to manage subscriptions, and optional Apple Health data for sleep insights on your iPhone. Where AI bed verification is available, a photo is sent through Supabase to DeepSeek only after your permission. Tips and offers are optional and are not a condition of using Rize.
This policy covers the website and the app, including account and AI features when available in a test or updated version. Older versions may not include those features. Reading this policy does not turn them on or give permission to upload photos.
1. Who is responsible
Rize is developed by Efe Aksoy, who is responsible for the processing described here. For privacy questions, requests, or newsletter withdrawal, contact efeaksoy9445@gmail.com.
2. Accounts and onboarding
Depending on your app version, you can use Apple, Google, or email and password to create or access an account. The sign-in provider supplies an account identifier and available name and email information; Apple may supply a private relay address. Supabase provides authentication and the account database. It processes your account ID, name, email, authentication information, registration date, and account updates. Email/password credentials are handled by Supabase Auth, not stored as a readable password in your Rize profile. Session credentials are kept securely on the device.
The backend profile can also contain your language and onboarding answers: gender if provided, how you heard about Rize, morning preferences, use of a sleep tracker, alarm frequency, difficulty getting up, usual and target wake-up times, and chosen challenge, difficulty, and repeat days. These support your profile and personalized setup. We do not use your Health data or challenge photos for marketing.
Account records are restricted to the relevant signed-in user in the app. The developer and authorized service providers may access backend records as necessary to operate, secure, and support the service. Do not include sensitive information in your name or support messages unnecessarily.
3. Alarms and information on your device
- Alarms, streaks, and preferences: stored on the device. Existing Apple/iCloud accounts can continue using private iCloud synchronization. New Google and email accounts initially keep this information on the device; backend profile synchronization is not an alarm backup.
- Profile photo: a photo you select for your Rize profile is stored on your device, not uploaded by Rize or synchronized through the profile backend.
- Private iCloud: the developer does not have access to your private CloudKit records. Apple operates iCloud under its own terms.
4. Camera challenges and AI bed verification
Camera access is optional and controlled by iOS permission. Touch Grass, Picture of Sky, Scan an Object, and push-up detection analyze photos or live frames on the device. Rize does not upload or record these challenge images. In versions without external bed verification, bed recognition also runs on the device.
When AI bed verification is available: the app explains the transfer and asks for your agreement before opening the camera. After you take and confirm a photo, a reduced-size, re-encoded image with location and other image metadata removed is sent to Rize’s Supabase function and then to DeepSeek to check whether a bed is reasonably made. The image itself can still reveal people, possessions, or details of your home; frame only the bed and avoid people, documents, and other private details.
DeepSeek receives the image and a bed-check instruction, not your Rize name, email, account ID, sign-in token, or Apple Health data in the request content. Rize does not save the photo in its backend database or log its content. Rize processes the result to accept the challenge or ask you to try again. Account-linked attempt counts and timestamps are retained for rate limiting; infrastructure providers may also process request and security logs.
This is not a promise of immediate deletion or zero retention by DeepSeek. Provider-side processing and retention may apply. DeepSeek’s consumer privacy policy does not itself govern downstream app users’ API data; its API terms are linked below. Photos may be processed in China. Do not use AI verification if you do not agree to this transfer. You can choose another challenge or decline before taking a photo; cancelling cannot recall an image already transmitted.
5. Apple Health and sleep coaching
If you enable Sleep Analytics, Rize requests read-only access to sleep data through Apple Health. It uses recent nights to calculate sleep duration, timing, stages where available, trends, scores, and personalized wellness suggestions on your iPhone. Derived sleep information is processed in memory, not uploaded to Rize’s backend, iCloud, RevenueCat, or DeepSeek.
On supported devices, coaching may use Apple’s on-device language model; otherwise it uses local rules. Health data is not used for advertising or newsletters. You can revoke access in Apple Health or iOS settings. Sleep scores and suggestions are wellness information, not diagnosis or medical advice.
6. Subscriptions and purchases
Apple handles App Store payments. RevenueCat processes a pseudonymous customer identifier, purchase and subscription records, entitlement status, and related technical information to verify and manage Rize Pro access and restore purchases. Rize does not receive your payment-card details and does not send your name, email, Health data, or camera images to RevenueCat as customer attributes.
Deleting a Rize account does not cancel an App Store subscription. Manage or cancel it in your device’s Apple subscription settings. Apple and RevenueCat may retain transaction information for their billing, security, and legal purposes.
7. Account emails and optional tips and offers
Supabase Auth and the configured email-delivery service, Resend, process your email address, account-message content, and delivery information for confirmation emails, password resets, and other necessary account messages. These are separate from marketing.
Newsletter signup is optional: the tips-and-offers checkbox starts unchecked. Creating an account, signing in, or purchasing a subscription does not automatically subscribe you. If you opt in, we record your account ID, email at consent, language, consent wording version, source, time, and any later withdrawal. Only opted-in, verified addresses are eligible; existing accounts are not automatically enrolled.
To withdraw, email efeaksoy9445@gmail.com from the subscribed address and ask to unsubscribe. Any marketing campaign we enable must also provide an unsubscribe option. Withdrawal does not affect your account, subscription, or the lawfulness of earlier processing. We do not sell newsletter addresses or use Health data or challenge photos to target offers.
8. Website, support, and security
This website remembers your chosen language and appearance in browser local storage. You can clear those preferences in your browser. The site does not currently include advertising trackers or an analytics SDK. Hosting and other infrastructure services can process IP addresses, browser or device information, requested URLs, timestamps, and error/security logs to deliver and protect the service.
If you contact support, we receive the contact details, message, and any attachments you send. Send only what is needed, and never send passwords, authentication tokens, or private keys. We use access controls and encrypted connections to help protect data, but no service can guarantee absolute security.
9. Providers and international processing
Service providers include Apple (sign-in, iCloud, Health access, and payments), Google (sign-in), Supabase (authentication, profiles, consent records, and server functions), Resend (account-email delivery), RevenueCat (subscriptions), DeepSeek (optional bed-image analysis), and our website hosting infrastructure. They process only the data relevant to their service; this is not a statement that every provider receives every category above.
Processing is not guaranteed to remain in your country. Depending on the provider, it may take place in the United States, China for DeepSeek, and other countries. Applicable transfer protections and API-specific terms must be assessed for the feature concerned; publication of this notice is not a certification of those arrangements. Contact us for information about the providers and transfer arrangements relevant to your use.
Provider information: Apple · Google · Supabase · Resend · RevenueCat · DeepSeek API terms.
10. Purposes and legal bases
Where these concepts apply under data-protection law, we process necessary account, service, and subscription data to perform our contract with you; optional Health access, external photo checks, and marketing rely on your choices and consent where required. Limited security, fraud prevention, and support processing may rely on legitimate interests, balanced against your rights. We may also retain information to meet legal obligations. Rize does not sell personal data or show third-party ads. Bed verification and sleep suggestions are not decisions with legal or similarly significant effects.
11. Retention and deletion
We keep backend profile and onboarding records while your account is active. Consent records are kept to manage your preference; withdrawing stops marketing eligibility without necessarily erasing the consent history. Use Settings → Delete Account in the app to request removal of your authentication account and linked profile, onboarding, consent, and photo-quota records. The app also clears the account’s local data and, where applicable, its private iCloud data; cloud changes require synchronization. Apple accounts may require Apple authorization to revoke sign-in access.
Rize does not keep an archive of challenge images in its backend. On-device images are discarded after processing or leaving the challenge. Quota counters are refreshed as later requests are made and are removed with the account. Service-provider logs, backups, transaction records, or information needed for security, legal obligations, or disputes can have separate retention periods; account deletion does not promise immediate erasure from every provider system. Contact us for a specific deletion or retention request.
Deleting Rize data does not delete the original records in Apple Health or cancel subscriptions. Signing out or uninstalling the app alone does not delete your backend account.
12. Your choices and rights
You can control camera and Health permissions in iOS, decline external photo checks, leave newsletter consent unchecked or withdraw it, and request account deletion. Depending on your location, you may also have rights of access, correction, erasure, portability, restriction, objection, and withdrawal of consent, and the right to complain to your local data-protection authority. Contact us using the email above; we may need reasonable information to verify that the request concerns your account.
13. Children and changes
Rize is not directed at children under 13. If you believe a child has provided personal data without required permission, contact us so we can investigate and address it. We will post policy changes here with a new effective date and seek new permission where a change requires it.