ATYPICOOL / TUBEQUEST
Privacy Policy
Last updated:
Atypicool is the project and brand behind TubeQuest, an app that helps parents combine video discovery with learning activities. Alejandro Galindo operates Atypicool and TubeQuest as an individual developer. This policy covers our website, parent portal, mobile apps, and APIs.
For privacy questions or requests about your family’s information, email support@atypicool.com.
1. Information we handle
- Parent accounts: email address, a protected password hash, account identifiers, sign-in sessions, account level, and settings. Passwords are not stored in readable form.
- Child profiles: the name or nickname a parent enters, grade, profile identifiers, question banks, and preferences such as video filters, voice search, and learning-break frequency. Children do not need their own email address or password.
- Learning and video activity: search terms, videos opened, recorded viewing events, video and channel information, questions presented, submitted answers, correctness, and timestamps. This information is associated with the child’s profile.
- Parent actions: profile and question changes, blocked videos, channels and keywords, report requests, and decisions about suggested learning-plan changes.
- Messages: support requests, suggestions, and bug reports sent from a parent or child profile, together with the sender’s account, message category, time, and any app version/build details supplied.
- Optional learning documents: IEP documents or learning-goal text a parent chooses to submit, and the proposals and questions generated from them. The processing steps are explained below.
- Atypicool Stories: the selected child profile, scenario and story descriptions, editable drafts, reference names and relationships, optional photos of children, other people and places, generated illustrations, and image revision requests and history.
- Technical information: network requests expose information such as IP addresses and browser or device details to our hosting provider and services loaded by the app. Operational logs may contain request or error information.
- Sign-in security: we record successful and unsuccessful sign-in attempts, including the attempted email address or username, time, outcome, IP address, browser or device information supplied with the request, and approximate city, region, and country when available. We estimate location using an IP-location database on our server, without requesting device GPS access or sending your IP address to a location lookup service. These records do not include passwords, session cookies, or access tokens.
- Sign-in protection: short-lived counters keyed by protected versions of email/username and IP identifiers help limit repeated password guesses. We record temporary cooldowns in the security log. These counters expire automatically; there is no permanent automatic account lockout.
2. How we use and share information
We use this information to provide accounts and child profiles, deliver questions and videos, apply parental settings, show learning history and reports, respond to messages, protect accounts, and understand which features families use.
Parents can access their own family’s information. Authorized TubeQuest team members can access account, activity, and message information to operate the service and provide support. Our hosting provider, Render, processes server data and stores the database and generated audio. Other providers used for specific features are described below. Information may be processed in the United States and other countries where those providers operate.
Community blocks display video/channel information and counts and percentages of parents blocking that content. The list does not display the parents’ names, children’s profiles, individual viewing histories, or private block reasons. Blocking choices contribute to these community counts.
If a parent gives an external tool a TubeQuest API key, that tool can access and modify the family information allowed by the parent API. Parents can revoke the key. The tool’s own handling of information is governed by its operator.
We do not sell family information or use it to target advertising. We may disclose information when required by law or when necessary to protect users or the service.
3. YouTube, Google, and Brave Search
TubeQuest uses YouTube API Services to find videos and retrieve video and channel information. Depending on the configured search provider and availability, search terms may be sent from our server to YouTube, Brave Search API, or both when a search provider fails. Brave searches are limited to finding YouTube videos. Videos are played through YouTube’s embedded player.
Brave search requests include the search text and filtering settings. We do not attach your child’s profile identifier, account details, device address, or learning activity. Brave’s handling of API queries is described in its Search API privacy notice. We still retrieve video information from YouTube and apply your family’s filters when Brave supplies search results.
When YouTube content loads, Google/YouTube may receive device and network information, use cookies or similar technologies, and serve content including advertisements. Their practices are described in the Google Privacy Policy. Use of YouTube features is also subject to the YouTube Terms of Service.
TubeQuest currently uses its own parent sign-in and does not request access to your Google account, YouTube subscriptions, or private YouTube account history. You can review permissions you have granted to Google-connected applications in your Google account connections settings. Deleting TubeQuest data does not delete information held independently by Google or YouTube.
4. Optional AI features and generated audio
Atypicool Stories (web only): creating a draft sends the selected child’s name, scenario, story description, and reference descriptions to OpenRouter and its selected text model provider. Draft creation does not send uploaded photos to these providers or generate illustrations. When you choose to create the illustrated story, we send the reviewed story, illustration descriptions, the child’s age and gender when provided, and any reference photos through OpenRouter to OpenAI. Age and gender are saved with that story to guide the illustrations. An image revision sends the current image, its saved generation description, your requested change, and reference photos through the same services. Photos can be used to carry a named person’s likeness or a place’s appearance into the illustrations. Only submit photos you have permission to use. Photos are optional; a story can be made without them.
Stories reuses your TubeQuest sign-in and child list. Story content, reference photos, generated images, and revision history are stored in a separate Stories database and are available through parent-authenticated requests. They are not published to a public gallery. A child photo can also be saved privately for reuse in future stories. You can reuse it, replace it, or use no child photo for an individual story. Each story keeps its own photo copy, so replacing the saved photo does not change earlier stories. You can delete a story, its photo copies, and its illustrations from the draft editor; the separately saved child photo remains available for future stories. Deletion from our service does not remove data independently retained by a processing provider.
Choosing Other lets you enter a name just for one story without saving a child profile. The name remains part of that saved story, and any photo uploaded for Other belongs only to that story; neither is added to reusable child profiles or photos. You can delete the story and its reference photos from the draft editor.
You can add children from Stories using the shared TubeQuest child list. Removing a child from Stories only hides them from new-story setup; their TubeQuest profile and data, saved photo, and existing stories are kept. You can restore them anytime. This preference is stored in the Stories database and does not delete the child's data.
Authorized team members can review Stories operational and billing records: account, child and story identifiers, action times and results, model and provider request identifiers, and reported AI costs. These records do not copy story text, prompts, or photos. Stories also stores credit balances, account page prices, story price quotes, and a credit history of opening grants, manual top-ups, completed-page charges and price changes, including amounts, timestamps, operator identifiers and optional notes. Creation counts, credit history and billing records may remain after a story is deleted so usage, balances and costs can be audited. The Stories app does not collect card details or process payments.
Learning reports: when a parent requests an AI report and the service is available, we send learning metrics, grade, relevant question text, answer examples, and possible learning-plan changes to OpenRouter and the model provider it routes the request to. Account names, email addresses, and account identifiers are omitted from that request. Personal information included in a custom question or answer can still appear in its text. Reports, suggestions, and parent decisions are saved in TubeQuest.
IEP practice: uploading a document sends it to our server for text extraction. The original file is processed in memory rather than saved as a document file. Before AI generation, the parent reviews and can edit the extracted text and confirms sending it for processing. The reviewed text and grade are sent to OpenRouter and its selected model provider. Remove names, dates of birth, diagnoses, contact details, and other unnecessary identifying information before confirming.
TubeQuest does not save the original IEP file or reviewed input text in its database. It saves a fingerprint of the input, generated proposals, and information about generation and adoption. Generated output can reflect sensitive details in the submitted text. Our AI requests ask for providers that do not retain prompts or use them for training; this request does not remove the need to minimize personal information in submissions.
Reading audio: we send the word to be spoken and voice settings to fal.ai to generate a recording. A word entered by a parent is included in that request. Generated recordings are saved, reused across profiles, and served through audio links that do not require sign-in. Avoid entering private information as a reading word. The standard success sounds are prerecorded phrases, not recordings of a child.
Password recovery: when email recovery is available and a reset is requested for an existing parent account, Resend processes the registered parent email address and a password-reset message containing a temporary link. The message does not include a password, child activity, or IEP content. We retain short-lived recovery records and hashed rate-limit identifiers to deliver the message and prevent abuse. Requesting a reset for an unregistered email does not create an account or send a message.
You can use ordinary question practice without requesting AI reports or uploading an IEP.
5. Voice search, cookies, and device storage
Voice search starts when the microphone control is used and requires device permission. Parents can turn it off per child. TubeQuest’s iOS voice search requires on-device speech recognition. Android requests offline recognition, but the device’s speech-recognition service may use remote processing according to that provider’s settings and policies. In the browser, speech recognition is available only where supported and may send audio to the browser provider’s recognition service under its policies. You can use typed search instead. TubeQuest does not save voice recordings or upload them to the TubeQuest server; recognized search text is submitted and recorded like a typed search.
The parent portal and browser child experience use an essential session cookie to keep you signed in. Opening a child profile replaces the parent’s browser session; returning to parent management requires signing in again. The browser stores each child’s learning-break counter, pending challenge state, retry timing, and encouragement rotation locally. A session-change signal keeps other open TubeQuest tabs in sync. Apps store credentials in platform-protected storage and keep preferences and playback/learning state on the device. Browser or embedded-player storage may also be used by Google/YouTube. You can clear browser data, revoke microphone permissions in device settings, or sign out. Clearing or uninstalling an app does not delete its server-side account history.
6. Children and parent choices
TubeQuest is designed for children using profiles created and managed by a parent or guardian. Parents choose the grade, question bank, video restrictions, voice-search setting, and optional learning features. A nickname can be used for the child’s profile.
Parents can review available activity and answers through the app or parent API, change profile information and questions, remove saved IEP proposals, and contact us to request access, correction, deletion, or an end to further collection for their child. To stop new activity immediately, stop using the child’s profile and sign out of devices where it is open.
If you believe information has been collected from a child without appropriate parental authorization, please contact us at support@atypicool.com so we can investigate and address the request.
7. Storage, security, and deletion
Stories: stories, their reference photos, and image revisions remain in the Stories database until the parent deletes the story or requests deletion. Open a story, choose Edit draft, then Delete story to remove its draft, uploaded references, and all saved illustrations from the active Stories database. Family generation counters cover a rolling 24-hour window; records older than two days are removed during that family’s next generation request. Saved child photos remain available across stories until replaced or deletion is requested. Choosing no photo for a story does not erase the saved photo. Child and account-wide deletion requests must include saved child photos in the separate Stories database.
Watch history: your family’s video history is available for the most recent 29 days, measured from when a video was opened. Older entries are excluded from watch-history views and APIs. Automatic cleanup runs when the server starts and daily while it is running, deleting expired watch records and any corresponding video-opened or video-completed activity copies from the active database. Deletion can occur after an entry stops appearing, at the next cleanup.
Learning and other records: this watch-history limit does not delete question banks, questions and answers, saved learning reports, account progress totals, blocked-content choices, separate search activity, or support records. We keep these to provide your family’s service, learning progress, and support; they do not currently have the same automatic 29-day expiry. You can request deletion at any time.
Sign-in security logs are accessible only to authorized TubeQuest team administrators for account protection and troubleshooting. They are normally retained for 90 days and then automatically removed from the active database. IP-based locations are approximate and may reflect a VPN, mobile carrier, or internet provider rather than your actual location. This product includes GeoLite2 data created by MaxMind.
Email support@atypicool.com from the parent account’s email address and tell us whether your request concerns one child or the whole family account. We verify that the request comes from the account holder before releasing or deleting information. Do not send your password or an IEP document with the request. Account deletion is handled by the team during the beta; there is no self-service account-deletion button.
Removing or resetting questions preserves previous answers and activity. Deleting an IEP proposal preserves questions already adopted into a child’s bank and the record of past actions. Request deletion of the related history explicitly if that is what you want removed.
Backups and recovery copies may retain information after it is removed from the active service and require separate handling. Some records may need to be retained for security or legal reasons. We will explain any remaining retention when responding to your request.
We use HTTPS on the public service, password hashing, protected session credentials, and account-based access controls. These measures reduce risk, but no storage or transmission system can be guaranteed completely secure.
8. Contact and policy changes
Contact the operator of Atypicool and TubeQuest for privacy questions, concerns, or requests:
Alejandro Galindo1761 Edgewood Dr
Palo Alto, CA 94303
United States
Email: support@atypicool.com
Phone: (202) 569-8386
We will update this page and its date when our practices change. A change requiring additional notice or permission will be handled before the new use begins.