wakeframePlease read these documents before using Wakeframe. Mandatory rights under the laws that apply to you are not limited by these documents.
1. Who is responsible
Wakeframe is operated by Quadvale Studio (Yosuke Fujita), Japan. The operator is responsible for personal information processed to provide Wakeframe. Use the support contact on this website for privacy requests, questions, or complaints.
2. Account and age information
We process the email address, telephone number or sign-in provider identifiers used for authentication; your user ID, username, display name and chosen profile photo; your date of birth, language and time zone; and account and consent settings. Date of birth is used for age eligibility and is not displayed to other users or sent to advertising SDKs. Authentication credentials are handled by Firebase Authentication; each account has one password. For accounts that can also sign in by email, phone-number sign-in checks that password with Firebase Authentication; phone-only accounts use a server-side salted password hash. We do not store readable passwords. Adding a date of birth is optional; without one, we record only your confirmation that you are 13 or older.
3. Content and relationships
We store the photos, videos, audio in videos, captions, comments, reactions and messages you choose to send, together with recipients, visibility, timestamps, friend requests, accepted friends, group names, memberships, invitations and blocked accounts. Photos and videos sent in Chats (DMs or groups) are not published to the timeline. We process reports, moderation decisions and appeals to protect users. Authorized service providers and the operator may process relevant content for delivery, safety checks, incident investigation and responding to reports. Messages in Chats (DMs and groups) are not end-to-end encrypted.
4. Alarms, device information and permissions
Alarm settings, stop times and your device time zone are processed to determine the morning posting window. Notification tokens are used to deliver notifications. Chat notifications include the sender or group name and the beginning of text messages, and are delivered through the Apple Push Notification service and Firebase Cloud Messaging. Photos, videos and morning photos are never included in notifications. The morning timeline notification only tells you how many friends shared a morning photo that day. Each notification type can be turned off in the app settings. Local alarm sound files stay on your device. Camera and microphone access are used when you record; the system photo picker provides only the media you choose. Contacts are used only for a device-side invitation workflow, not uploaded as an address book. Wakeframe does not request GPS location. Network and advertising providers can receive your IP address and derive an approximate location. Permissions can be changed in system settings; optional permissions control only the features that need them. Other features remain available.
5. Purposes and legal bases
We use information to authenticate accounts, provide alarms and social features, enforce posting windows and visibility, deliver messages and notifications, respond to support, prevent abuse, and comply with legal obligations. Where GDPR or similar law applies, processing relies on performance of the service contract, legitimate interests in security and operation where those interests are not overridden by your rights, legal obligations, or consent where required. Optional tracking and any processing legally requiring consent depend on that consent; it may be withdrawn without affecting the lawfulness of earlier processing.
6. Advertising and service providers
Firebase and Google Cloud provide authentication, databases, private media storage, server functions, notifications, hosting and abuse protection. Google Cloud Vision checks uploaded media for safety. The app includes Google AdMob and mediation SDKs from Unity Ads, Liftoff Monetize, Chartboost and Meta Audience Network. Which network serves an ad depends on the active configuration and availability. Advertising providers may process IP-derived approximate location, device or advertising identifiers where permitted, ad impressions and interactions, usage and diagnostic information. On iPhone, the app requests personalized ads only for users aged 18 or over who allow tracking. On Android, it requests personalized ads for users whose registered date of birth shows they are 18 or over; this can be turned off by deleting the advertising ID in the device settings. For everyone else, it requests non-personalized ads and applies Google's teen ad treatment, since everyone confirms at sign-up that they are 13 or over. All ads are limited to general-audience content. These settings do not mean no data is processed. We do not send your messages, photographs, full date of birth or address book to advertising networks as targeting data. See the linked providers’ privacy policies for their processing. Firebase Crashlytics receives reports of app crashes and freezes (technical error details, device model, OS and app version, and a pseudonymous installation ID) so that we can find and fix problems; your posts, messages and contacts are not sent. Google Analytics for Firebase receives app usage events (such as app opens, screens viewed and use of features like posting or inviting friends, and whether a feed ad was shown and, if not, the type of error), device, OS and app version, an app instance ID and approximate region, so that we can understand how the app is used and measure installs that come from our own ads. On iPhone it uses the advertising identifier only if you allow tracking, and ad personalization signals are turned off. Your posts, messages, contacts and date of birth are not sent. When you buy Wakeframe+ or a pass, Apple or Google processes the payment. We receive and keep the transaction information needed to provide what you bought (product, transaction and order IDs, purchase and expiry dates, and refund status), never your card details. When you earn a pass with a rewarded ad, your Wakeframe user ID is passed to Google AdMob so it can confirm the reward to our server. Separately, for users in regions where ad choices are legally required, such as the EEA, the UK, Switzerland, and certain US states, and whenever the region cannot be determined, we signal to Chartboost, Liftoff Monetize and Unity Ads that the user has not consented to the sale or sharing of data for advertising. In other regions, such as Japan, these networks may treat the user as not subject to that opt-out. This is separate from whether an ad itself is personalized, which depends on age as described above.
7. Visibility and sharing
Your username, display name and profile photo can be shown in profile search and social features. Posts are shared with the audience you select: accepted friends, or eligible friends of friends. Viewing friends’ posts also requires completing that day’s morning posting condition. Direct messages are displayed to the conversation participants. Recipients may copy or screenshot content; we cannot undo copies outside Wakeframe. We may disclose limited information to service providers, when lawfully required, or when necessary and proportionate to address serious harm or protect legal rights. We do not sell personal information for money. Advertising-related sharing can have a broader legal meaning in some jurisdictions; you can contact us about applicable opt-out rights.
8. Storage, security and international processing
We use encrypted network connections, private storage, authentication, server-side authorization, rate limits and app-integrity checks. Uploaded images are resized and re-encoded, and location metadata is removed; videos are processed for size and duration. No system can guarantee complete security. Cloud providers may process information in Japan, the United States and other countries. Where legally required, international transfers use an applicable adequacy decision, contractual safeguards or another lawful transfer mechanism. Contact us for information relevant to your request.
9. Retention and account deletion
Account information and content are retained while needed to provide the service or until you delete them. Account deletion is available in Settings and may require recent sign-in. It starts a server-side deletion process for the profile, posts and media, friend relationships and conversations involving that account. A scheduled worker continues processing if the app disconnects; deletion is not necessarily instantaneous. Limited security, abuse-report, moderation, appeal and legal records may be retained when necessary to resolve incidents, prevent repeated abuse or meet legal obligations. Provider backup and security-log retention follows the applicable service configuration. Information retained for these purposes is restricted and is not restored as a public profile. Copies previously saved by other users are outside our control.
10. Your rights and children
Depending on applicable law, you may request access, correction, deletion, restriction, portability, or objection to certain processing, withdraw consent, and complain to a relevant data-protection authority. Contact support with your username and request; do not send passwords or identity documents unless a secure and proportionate verification process is separately agreed. Wakeframe is not for children under 13, and local rules may require a higher age or guardian consent. We use the declared date of birth for eligibility, not government identity verification. If you believe an ineligible child has registered, report it to support.
11. This website and support
This website does not load advertising or analytics trackers. Hosting providers process network and request information to deliver and secure the site. Your chosen language may be stored locally in your browser. Information you send to support, including your reply address, message and correspondence, is used to address the request and related safety or legal issues. Avoid including unrelated personal information or illegal media. Changes to this policy will be published here with an updated effective date; material changes will be communicated as required by law. Contact form submissions are stored in Firebase and forwarded to our Google Gmail support inbox so we can respond.