1. Who we are
HYSM (“Have You Seen Me,” “we,” “us”) is the studio behind the apps listed at hysm.org/devstudio and the optional services we operate under that name, including apps.hysm.org.
Privacy requests: privacy@hysm.org (or hello@hysm.org until that mailbox is live).
2. Studio rules (every HYSM app)
Unless an app note below says otherwise, every HYSM app follows these rules:
- Local first. The work you create in the app — notes, plans, files, recordings, settings — are all stored on the device in app-private storage.
- No account required to do the work. We do not make a HYSM login the price of the core feature.
- No advertising stack. We do not ship ad SDKs, tracking pixels, or third-party analytics in the apps or on these static pages.
- No sale of personal information. We do not sell your content. We do not share it for cross-context behavioral advertising. We do not rent your life to brokers.
- Network is a tap, not a background habit. If something leaves the phone, it is because you started a named action you can describe in one sentence.
- Minimum payload. When an action needs a network, we send the smallest artifact that makes the action work (text instead of a whole file when text is enough; a file only when the feature is “send this file”).
- You can delete the local store. Each app includes a Settings control that wipes that app’s on-device data. Uninstalling removes the app’s private files.
- These pages do not spy. hysm.org is static HTML. No cookies. No analytics script.
3. What stays on the device
Typical local store — exact items are in the app notes:
- Content you type, import, record, or generate.
- Files the app copies for your use (a syllabus PDF, an audio recording, an exported document you have not yet shared).
- Preferences and feature flags.
- Secrets you supply (API keys) in Android Keystore–backed storage, not in the APK.
- A device-generated identifier if that app talks to a HYSM service, used to enforce quotas or entitlements — not to stitch an advertising profile.
Where the OS allows it, we turn off automatic cloud backup of sensitive app data so a platform backup does not quietly copy your data into someone else’s cloud.
4. What may leave the device
Offline features keep working on whatever is already stored. If you never tap a network action, HYSM does not receive your content.
When you do tap, the destination is one of:
- A HYSM service we operate (today: apps.hysm.org), over HTTPS; That service does not invent the answer itself. It forwards the submitted text or audio to the model provider that performs the work — today that provider is xAI (api.x.ai) — then returns the result to the app. xAI’s terms and privacy policy apply to that processing step; or
- A provider you chose with a key you pasted (for example a speech or language API), over HTTPS, under that provider’s terms.
We use a HYSM service so vendor keys do not live in a public APK, so we can meter free use, and so we can keep the contract honest. We use a provider you chose when the family or early build is bring-your-own-key. An app note says which path that app takes today.
Ordinary hosting, DNS, and TLS vendors may see IP addresses and connection metadata, as any site host does. Language-model or speech providers process submitted text or audio only to complete the request you started. We do not grant them a right to use that material to advertise to you. We do not use your content to train a HYSM model.
5. Sale, ads, and profiles
We do not sell personal information. We do not share personal information for cross-context behavioral advertising. We do not build a marketing dossier across apps. A paid entitlement, if we add one, marks that a device or purchase may use a paid feature. It is not a license to profile you.
6. Permissions
Each app requests only what a feature needs (microphone to record, a document picker to read a file you choose, notifications if you opt into reminders). Refusing a permission turns that feature off. The rest of the app should still work on data already on the device.
7. Retention, deletion, and export
On the device. You hold the store. Use the in-app delete control, then uninstall if you want the app gone. Export or share only what you mean to let out — once you send a file to another app or person, that copy is outside HYSM.
On a HYSM server. We aim to keep request bodies only long enough to finish the job and debug a failure you report. Quota or entitlement rows (device id, timestamps, counts) may last longer so free tiers cannot be reset by reinstalling. Email privacy@hysm.org with the device id shown in that app’s Settings if you want server rows removed. Counsel should lock a numeric retention window before Play ships.
8. Children, classrooms, and schools
HYSM apps are aimed at college students, families helping them, and adults doing their own work. They are not directed at children under 13. We do not knowingly collect personal information from children under 13. If that happens through Extract, Ask, Transcribe, or a future action, tell us and we will delete server records we can find.
A document or recording can contain other people’s voices or names. You are responsible for having the right to process that material. Some places require all-party consent to record audio. Many schools restrict recording without instructor permission. HYSM is not your school’s FERPA official. Counsel should review COPPA, FERPA, and state student-privacy law against the store audience.
9. International users
HYSM services are operated from the United States. If you use a network action from another country, submitted material is processed in the U.S. and in regions our processors use. Add GDPR/UK GDPR language before targeting those stores.
10. Your rights
Where law gives you rights to know, access, correct, delete, or limit processing: most HYSM content never leaves the phone, so the practical delete is the in-app wipe plus uninstall. For server quota or logs, email privacy@hysm.org. We will not treat you worse for asking.
11. Security
HTTPS to HYSM services. Vendor keys for public builds belong on our side of the proxy, not in the APK. Bring-your-own-key builds keep those keys in the Keystore. No transmission is perfect. Do not paste secrets into a syllabus box or a lecture title.
12. Changes
When we add an app, an account, a payment rail, a processor, or a new kind of data that leaves the device, we update this page and the “Last updated” date. New apps inherit sections 1–12. Their differences appear as a new labeled note below — not as a silent change to the studio rules.
13. App notes
These paragraphs are the only place we list app-specific payloads. If a note conflicts with a studio rule, the note wins for that app and that version, and we will say so plainly.
DueNext · com.hysm.duenext
Syllabus planner
On the phone: terms, courses, tasks, study suggestions, pasted or extracted syllabus text, and any local copy of a syllabus PDF you import.
What leaves, only if you tap: Extract sends syllabus text (not the PDF file), a device id, and a year/term hint to apps.hysm.org (/v1/extract).
Ask sends your question plus a short excerpt to apps.hysm.org (/v1/ask).
Quota check sends the device id (/api/check).
Delete: Settings → Delete all local data removes the database and copied PDFs. Uninstall removes the rest of the app store.
ClassReplay · com.hysm.classreplay
Lecture recorder (family MVP)
On the phone: lecture audio, transcripts, summaries, titles, course labels, timestamps, and any API keys you paste (Keystore + encrypted preferences).
What leaves, only if you tap: Transcribe sends the audio file to the speech provider you configured (family MVP: OpenAI Whisper via the key on the device). Summarize sends transcript text to the language provider you configured (family MVP: xAI). Export PDF leaves the phone only if you share that file. Recording, playback, reading, and export of data already stored still work offline.
Delete: Settings → Delete all lectures removes database rows and audio files. Clearing keys is a separate action.
Classroom: other students and the instructor may be in the recording. Ask before you record. Do not treat a summary PDF as harmless if it quotes people who did not agree to be in the notes.
A later public build may route Transcribe/Summarize through a HYSM proxy the same way DueNext routes Extract/Ask, so vendor keys leave the client. If that happens, this note will say so before that build ships.
14. Apps we have not shipped yet
A future HYSM app is covered by sections 1–12 on the day it uses the HYSM name or the com.hysm package root.
We will add a short labeled note here that states: what lives on the device, which tap sends what, where it goes, and where Delete lives in Settings.
Until that note exists, assume the studio rules and assume nothing leaves the phone unless the in-app copy says it does.