Start here
Wise Sparks keeps each learner’s space separate. The hosted platform saves account and learning information so invited families can continue on different devices. The earlier offline edition keeps its work on the local device.
This draft describes the implemented pilot features. The operator’s supplied business contacts are listed below. Legal review and an approved, tested retention and deletion process remain unfinished. This page is not a statement that all privacy or consent requirements have been satisfied.
Information used by the platform
Account & access
Username, password verification data, account role and status, sign-in sessions, security and account-change records.
Provide sign-in, protect accounts and record important changes.
Learning profile
Student name, selected grade, school, courses, schedule, theme and membership or testing group. A hosted learner profile holds no caregiver phone number; for kindergarten to grade 2 it records only that a caregiver completed setup. An adult’s own contact details, given when they ask for an account, belong to that adult’s account and are described below.
Set up an appropriate learning space and support the invited pilot.
Practice & saved work
Answers, attempts, saved activities, writing, helper chat, points and purchases, visits, pets, calendar tasks, organizer directions and optional photos.
Save work, run activities, show progress and restore your space.
Parent account requests
When account requests are open, a parent can ask for an account on the public site with their first and last name, an email address, a username the site suggests, a password and, if they have one, an invite code. A phone number and a ZIP or postcode are offered and never required: nothing in Wise Sparks reads them, and they are held only so the care team can reach a family another way. The request cannot sign in until a Wise Sparks administrator approves it, or a valid invitation code approves it at once, and we record which code did. A request nobody decides in 30 days expires: it stops waiting, and what it holds is kept until a person decides it. A declined request keeps its name, password and contact details for 30 days, then all three are cleared and only the username stays reserved, with a short record of the request and its decision.
Let a parent ask for an account, let a person or a valid invitation code decide it, and tell the family what was decided.
A learner who signs up themselves
When registration is open, a learner from grade 3 to grade 12 can start their own account, and only with a parent or guardian email address and their agreement. We write to that address with a six-character code, and the learner’s space opens only when the code is typed in, so nothing is practiced or saved until the grown-up agrees by passing it on. A code works for seven days and can be sent again. If nobody opens the account within 30 days, we clear the learner’s name, school and the grown-up’s address from it and switch it off. A reply to the letter closes the account at any time. The address is held for that and nothing else: it is never shown on any page about the learner, never used for advertising, and never shared outside Wise Sparks. Kindergarten to grade 2 is not open to new accounts yet, from this form, from a parent’s account or from a school’s class list.
Let a learner start, with a grown-up told and able to end it.
How we reach a parent
An approved parent account keeps the email address, and any phone number or postcode, given when the account was asked for. We write to that address about that account and nothing else, starting with one letter saying it was approved or declined. There is no marketing, no newsletter and no sharing with anyone outside Wise Sparks. A parent changes or clears these details in their own profile at any time, and an account with no address on it simply receives nothing. Only that parent, and the Wise Sparks team, can read them: they are never shown to a teacher, to another family, or on any page about a learner.
Tell a family what was decided about their account, and give the care team a way to reach them.
Children a parent adds
When account requests are open, an approved parent can add their own child, from grade 3 to grade 12, with the child’s full name, grade, a username the site suggests and a first password the parent chooses. The parent confirms they are the child’s parent or legal guardian, and is connected to the child with learning and school access. The child picks a new password at their first sign-in. A Wise Sparks administrator sees every child added this way and can pause the account.
Let a family start without waiting for us, while a person can still step in.
Family a parent invites
When family invitations are open, a parent can invite another adult in the family, such as the other parent or a grandparent, by name and email address. We write to that address once, with a code that works once for seven days, and the letter names the parent who sent it and never a child. The invited person opens their own account with the code, choosing their own username and password, and is connected only to the children the parent chose, with no more access than that parent has. We keep the address until they join or the invitation is canceled, and at most 30 days after it ends. The invited person can leave at any time, and a Wise Sparks administrator can end the connection.
Let a family share a child’s learning with the adults they choose.
Teachers a parent approves
When teacher connections are open, a teacher can ask to connect with a learner by username. The teacher is told the same thing whether or not the username belongs to anyone. A parent or legal guardian of the learner approves or declines, and any of them can remove the connection at any time. A connected teacher sees only the learner’s name and grade, on their teaching page. A request ends after 14 days, and a teacher a family declined cannot ask that family again for 90 days. A family can also choose to share a weekly practice summary with a connected teacher: what the learner practiced, how much, and whether it looks steady or worth revisiting. It never carries their writing, helper chat, messages, school results or uploaded reports, and the family can stop sharing at any time. A connected teacher can also suggest one activity that Wise Sparks already offers at that learner’s grade. The suggestion carries nothing the teacher wrote, and only the family can make it their child’s focus.
Let a family decide which teachers see their child, how little, whether practice is shared, and what is suggested.
Schools and what they see
When a school runs its own space on Wise Sparks, it sees a child only after the child’s parent or guardian connects them with that school, by accepting the school’s invitation or by asking with the school’s family code. The school then sees the child’s name, grade and class, and whether they have started. It sees the child’s own practice, what they practiced and how it went, only if the family chooses to share it, and the family can stop sharing at any time. Counts a school sees about a group include a child only when the group holds five or more learners, and accuracy is rounded so a small group’s results cannot be read back to a child. A teacher at the school sees a child’s practice only after the parent approves that teacher. Before a family connects, a school can see how many learners named it when they signed up, by grade and spelling, and never who they are. A school never sees writing, helper chat, messages or uploaded reports.
Let a school a family chose support its learners, and let the family decide what it sees.
People who work at a school
A school invites the people who work in it by name and email address. We write to that address once, with a code that works once for fourteen days, and the person chooses their own username and password. A teacher who names their school in their teaching profile can be found by that school and invited to join it. When a school asks to join Wise Sparks, we keep the contact’s name, role and email address until the application is decided, and then the address is erased from it.
Open a school’s space, and let the right people into it.
A school’s page and its record
Each school has its own page on Wise Sparks, at its own address. It shows the school’s name, logo and welcome, and how to sign in or join, and never its people, its learners or its figures. We keep a record of what happens in each school’s space: who invited, changed or approved what, and when a child’s shared practice was opened. The Wise Sparks team uses it to see how the space is run and to help the school. The Wise Sparks team can open a school’s space to help it, only to read, and each time is kept in that record. A request for help sent from a school’s space carries the school’s name, so the right person answers it.
Run each school’s space openly, and help it when it asks.
Family & school connections
Parent accounts, invitations, requested and approved relationships, permissions, school-directory and enrollment records, and review history.
Keep family access tied to the right learner and explain enrollment decisions.
Reports & next steps
School assessment evidence, uploaded PDF or image originals, extracted text or viewing copies, report context, draft findings, source quotations, confirmed transcriptions, practice summaries and shared learning plans.
Help an authorized family understand the evidence and choose a next step.
Help & safety
Tickets, replies, feedback, flagged text, review decisions and service targets.
Respond to requests, improve the product and review safety concerns.
Technical operation
Essential session cookies, browser storage and operational information handled by the hosting service, such as connection information. When request telemetry is switched on, a record of each page request goes to Microsoft’s Application Insights, part of the same Azure hosting, and is kept for 90 days: the page’s address without anything after a question mark, whether it worked, how long it took, and the database and model calls inside it. It never carries what you typed, your name, your email or network address, or your browser.
Keep the service available, remember your space and troubleshoot problems.
Public contact inquiries
The public contact form saves the sender’s name, reply email, optional phone number, inquiry type and message in a private administrator inbox. It also keeps receipt, status and duplicate-prevention records. Early access requests from the Plans page save only a reply email and whether the sender is a parent, tutor, school or other, in the same inbox, so the team can write when plans open. Contact details are supplied by the sender and are not verified. No account or marketing subscription is created. When inquiry email is configured, two messages are sent: a note to the team carrying only a topic, how many inquiries are waiting and a link, and a confirmation to the reply address you gave, carrying its reference. Neither repeats your message. The team uses these details to handle and follow up on the inquiry. When the care mailbox is connected to the platform, the team also sees, in its own administration pages, who wrote to that mailbox by email, the subject and when, for the latest 25 messages; never the message itself. Do not submit school reports, passwords or sensitive information about a child.
Who can see information
Learners use their own spaces. Authorized parents see information for the named child within the permissions of their connection. Platform staff can access information needed for their assigned responsibilities. The Architect manages platform access.
A parent account request is seen by the Wise Sparks administrator who decides it. Other staff do not see requests.
Support requests go to the requester and the authorized team; internal team notes stay with staff. Certain safety notices can be shown to a linked parent. These features are not an open public feed.
Microsoft Azure hosts the public pilot and its database. Microsoft Foundry processes permitted AI requests only when a separate AI feature is enabled. Resend delivers the letters this platform sends: the two around a contact-form inquiry, which carry a reply address, a topic and a reference and never the message you wrote, the one telling a family that their account request was decided, which carries the address that family gave and the username they chose, and the ones to a learner’s grown-up at the address given for them: the code that opens a learner’s own sign-up, and the notice that an account was made for their child, each carrying the learner’s username. No learner’s own address reaches it, because a learner account holds none. Optional external video links open another provider’s site when chosen. The complete provider and operator contact list requires confirmation before this policy is final.
Photos, schoolwork and questions
Managed-account progress can include saved organizer or task photos and the prepared hint helper’s conversation. Saving them to a hosted account is different from keeping them only on your device.
Organizer photos are references; the current helper does not inspect or grade them. The text tutor does not receive those photos or uploaded report files. Check photos for names, addresses or other people’s information before adding them.
The original report-import tools and the public student platform have different capabilities. Do not assume every file on a family device is uploaded to the public website.
Your private Report library
When report uploads are enabled, a learner can add their own PDF, PNG or JPG. A parent needs an approved learning connection for that learner. The Architect has administrative access; ordinary support or school-directory access does not open these files.
Original bytes are preserved privately, with a file receipt and source references. The hosted design uses private Azure Blob Storage for originals and viewing copies, and the account database for metadata, findings and review history. Files are not published in GitHub or exposed as public download links.
Uploading does not send a report to the model. An authorized adult must separately request report processing and check its notice. The report reader sends extracted PDF text or a cleaned screenshot to Microsoft Foundry, including any personal details still visible. Review and crop unnecessary information before uploading.
The reader can miss details or make incorrect suggestions. An authorized adult checks source quotations, scores and the correct learner before confirming findings or choosing a Journey focus. This does not verify the document with its publisher, change the profile grade or overwrite official assessment records.
School, district, city, county, state and country are optional report context. They do not grant access to other families or place private reports into a public research or training collection. Aggregated geographic research is not implemented.
AI processing and improvement
When enabled, Sparki · Learning companion sends a submitted question with permitted lesson context, selected grade and support choice to Microsoft Foundry. The service tries to remove some profile details, but a free-text question can still contain personal information.
The parent copilot sends the submitted question and descriptions of possible guidance cards. It does not automatically attach recorded report values or private ticket bodies; Wise Sparks fills in authorized facts after a card is selected. The Architect copilot sends the open conversation and the results of read-only lookups it asks for: counts, statuses, queue sizes, feature readiness and review-queue titles. Those lookups exclude children’s names, school reports, support and inquiry text, private messages and passwords. Information you paste into a question can still be sent, so leave private records out.
Tutor and copilot request logs record operational metadata, not raw model questions and replies. The separate Report library stores the original, extracted source, structured draft findings and confirmed review so the family can check the evidence. This does not mean all conversation features are unsaved, or that Microsoft has no processing or abuse-review records. No automatic training or fine-tuning pipeline uses learner records. See the AI use notice for the limits.
Cookies and saved copies
An essential sign-in cookie connects the browser to a server-side session. Browser storage is also used for preferences and saved work. Signing out closes the active sign-in; it does not necessarily erase local browser storage, downloaded backups or an account’s saved records.
Use your own browser profile on a shared device and sign out when finished. Removing a browser copy is not the same as requesting deletion of the hosted account. The reviewed application has no advertising tracker integration; the operator still needs to confirm all hosting and provider configurations.
Keeping and deleting information
Account records, work and support history persist so the platform can operate and families can return. Some short-lived security records expire. Disabling an account is not the same as deleting its information.
A complete schedule for deleting account data, learning records, photos, safety records, AI metadata and backup copies is not yet approved. Automated account-wide erasure is not currently offered through this page. These are release requirements, not permission to keep children’s information indefinitely.
The final policy must state actual retention periods and deletion procedures, including how requests and backup copies are handled. It must match tested operations rather than a promised timeframe that the service cannot perform.
Removing an uploaded report
Folders and categories organize one learner’s files; they do not grant access to another learner. The Report library offers removal from active use. It hides the report, removes its stored originals, viewing copies and saved findings, and retires a practice focus based on it. Existing practice and minimal operational receipts are kept. If storage is unavailable, the report stays hidden and removal can be retried.
A learner can remove an unreviewed report they uploaded; a parent or The Architect handles reviewed reports and reports uploaded by an adult. Removing a live report does not instantly erase backup copies, provider processing records or files someone already downloaded. The approved retention procedure must cover those copies before real-report collection is enabled.
Parent choices and privacy requests
A parent can request to review or correct a child’s information, ask for deletion, or ask to stop further collection or use. The team needs to confirm the requester’s authority for that child before disclosing or changing records.
While signed in, open Help & ideas, choose Privacy & safety, and describe the request. Keep passwords and identity documents out of the ticket. A ticket records a request; it is not confirmation that deletion or withdrawal has already been completed.
You can also email ortivs@ortivs.ai if you cannot sign in. The team must confirm your authority before sharing or changing a child’s records. Family access approval and consent to collection remain separate.
Updates to this policy
The operator must review this draft and provide a notice process before the final policy takes effect. Material changes to children’s data practices may require a new direct notice and consent step. A child’s next sign-in is not automatic consent.
Let’s help you find a way forward.
The welcome page answers the questions families ask most: how to join, and where a child starts. If yours is not there: a question, an idea or a privacy request? Get in touch with the Wise Sparks team. Please leave passwords and private documents out of your message.
- Wise Sparks is operated by
- Ortivs Intelligence, LLC
- Business location
- Florida, United States
- General help & privacy
- ortivs@ortivs.ai
- Business contact phone
- +1 (305) 731-5143
Already signed in? Open Help & ideas to follow your request inside Wise Sparks. For privacy requests, choose Privacy & safety.
The policies remain under review while the complete business notice and operating procedures are finalized.