sphinxsyLEARN · CREATE · PLAY · TOGETHER

Privacy policy

Draft for review. This describes how sphinxsy works as of October 8, 2026. It was prepared for Cyvexly LLC and has no effective date while contact and launch arrangements are being completed. It is not a legal opinion.

Who we are and what this covers

sphinxsy is operated by Cyvexly LLC at sphinxsy.com. It lets teachers, trainers and families turn their own material into quizzes, live games, study sets, forms and certificates. This policy covers the sphinxsy website and the people who use it: creators (who sign in and build activities), and participants (learners, players and respondents who open a shared link or join a game).

When a school, employer or other organization uses sphinxsy with its learners, that organization decides what to collect and why; sphinxsy processes participants' information on its behalf to run the service for it, subject to its instructions and applicable agreements. Each party remains responsible for its own legal obligations.

What we collect

  • Creator accounts: your name and email address from sign-up (email code, Google or Microsoft sign-in), your workspaces, role and settings. We don't receive your Google or Microsoft password, and sign-in asks only for basic profile and email access.
  • What creators make and upload: activities, questions, answer keys, pictures, and source material. Uploaded files (PDFs, documents, slides, spreadsheets, captions, photos and recordings) are kept as uploaded, together with the text read from them, so questions can cite where each fact came from.
  • Participants: what the activity asks for — a nickname in a live game, a name or learner code on class links, answers, scores, time taken, and files a form asks for. Anonymous identity settings omit requested names and learner codes from the response record, but free text and uploads may still identify someone. Many activities allow guest participation; restricted organization or LMS links may require the relevant account or launch. A workspace may also provide participant emails for invitations and reminders.
  • Reports to our reviewers: the reason and details you give, and, if you choose to give them, your name and email so we can reply. The workspace you report never sees your contact details.
  • Technical records: an audit log of changes inside each workspace, counts of link opens (not who opened them), and the server logs our hosting provider keeps for security and troubleshooting.

How we use it

  • To run the service: show activities, score answers, run live games, keep study progress, issue and verify certificates, and produce reports for the workspace that owns them.
  • To send notices a workspace's owners and admins choose to receive (safety alerts, renewal summaries, outcomes of content reports) and to reply to people who send a report.
  • To keep sphinxsy safe: rate limits, handling reports of harmful or infringing content, and reviewing safety alerts.

We don't sell personal information, show advertising, or use participants' information to build advertising profiles.

AI features

Some features use an AI model (Google's Gemini) when they are switched on: drafting questions from a creator's sources, reading photographed or scanned pages and recordings, web research with cited pages, and, for learners, “Explain this” and the study companion. What a feature needs is sent to the model — the creator's source text or file, or the published question, answer and cited passages. We do not intentionally add roster names or learner codes to AI requests, but source material and free text can themselves contain personal information. Remove unnecessary personal information before using an AI feature.

Learner-facing AI is currently not offered on sphinxsy.com; it will only be switched on after its policies are settled, and each workspace can keep it off. When it is on, a learner's message that sounds unsafe is not sent to the model: the learner sees help information instead, and a short excerpt goes to the workspace's staff for review.

Service providers

We use these providers to run sphinxsy. Each receives only what its part of the service needs:

  • Render — application hosting and the PostgreSQL database (United States).
  • Cloudflare R2 — private storage for uploaded files (automatic placement; no fixed country or jurisdiction guarantee).
  • Clerk — creator sign-in and sessions; Google and Microsoft when you choose to sign in with them.
  • Resend — sending email notices from notify.sphinxsy.com.
  • Google (Gemini API) — the AI features above, when switched on.

Cookies and storage in your browser

  • Sign-in cookies from Clerk keep creators signed in.
  • A cookie remembers which workspace a creator last opened (one year).
  • A live-game cookie lets a player rejoin the same game after a refresh (12 hours).
  • On anonymous links, a random cookie marks the browser so one person can't be counted many times (about 13 months); it contains a random identifier, not a name. Persistent identifiers can still be personal information.
  • A study cookie keeps a learner's study progress on a class link (180 days); answers in progress are also kept in the browser's own storage until they are sent.

We don't use advertising or third-party tracking cookies.

How long we keep it

  • Workspace content, responses and uploaded files currently remain until the workspace uses its deletion or erasure tools. Activity trash is retained for 30 days. Student-record expiry and school-specific retention arrangements must be established before the applicable child-data collection is offered.
  • Reviewed safety alerts are eligible for deletion 90 days after review; cleanup currently runs when the review queue is accessed. Finished webhook delivery records are eligible for cleanup after 30 days.
  • Database backups kept by our hosting provider may hold deleted information for a limited time after deletion.

Your choices and rights

  • Workspace owners can export everything in a workspace (Settings → Data & privacy), erase a learner's records from Reports, and delete the workspace.
  • Each person can turn email notices off in Settings → Email or from the link in any email.
  • Participants whose school or employer uses sphinxsy should contact that organization first; it controls their records. Anyone can contact us at a contact address that will be listed here before this policy takes effect to ask about, correct or delete their information.

Children

Children's participation requires an appropriate school or parent authorization arrangement. A school's authorization covers only the educational purposes it lawfully authorizes; Cyvexly LLC retains its own operator obligations. Teacher supervision or accepting these terms does not by itself establish every required authorization. Direct notice, review/deletion rights and a way to stop further collection must be in place before collecting personal information from children under 13.

Security

Traffic is encrypted (HTTPS). Uploaded files are stored privately and only reach people through sphinxsy after their access is checked. Each environment (production and testing) uses separate accounts, databases and storage.

Changes and contact

We'll update this page when how sphinxsy handles information changes, and note the date at the top. Questions: a contact address that will be listed here before this policy takes effect. You can also read our terms of service.