Privacy Policy

Using the EdVoice Data plugin

The public MCP connection does not require an EdVoice account or Google sign-in. It receives only the search terms and record references your assistant sends to its tools; it does not request your full conversation, name, email, or private student records. Search terms are sent to Chroma Cloud for search and embedding processing. Record references are sent to Chroma Cloud to retrieve public legal text. These providers process requests under their own policies. Your assistant provider separately handles your conversation.

The MCP handler does not save queries or tool results in our website chat database. The seven-day chat-log period below applies to website chat, not the MCP connection. Hosting providers may process request addresses and technical request information for service operation and security under their retention policies. We do not set a separate retention period for their infrastructure records. Keep tool queries limited to your research topic and do not include confidential or sensitive personal information. You can disconnect the plugin through your assistant settings and contact us about data handling.

Trying chat without signing in

You can try two research questions without signing in. Starting a new chat does not reset your allowance. An essential guest cookie records this browser trial for up to 30 days. Temporary chats remain available for up to 24 hours from chat creation; expired text is excluded and removed on later activity, so physical deletion may be delayed while the service is idle. Diagnostic logs have their separate seven-day expiry. After Google sign-in, all available guest chats are added to that account’s private history, including an existing account. Your prior saved chats remain available. After a completed save, a later signed-out visit can start another trial within our usage limits.

To limit automated use, our server converts the network address supplied by our hosting provider into a private hashed identifier. We do not store the original address in guest records. Hourly and daily limit records expire with their window and are removed on later activity. A trial’s hashed budget identifier is retained until its 30-day expiry. Shared networks can reach these limits; Google sign-in remains available.

Google sign-in and your account

When you sign in, EdVoice Data receives and stores your Google account identifier, name, and verified email address. We associate submitted questions and follow-ups with your account so the site operator can understand usage, review research quality, and investigate errors. We do not request access to Gmail or Google Drive.

Questions, answers, and research logs

We store questions, follow-ups, answers, and search activity privately in our application database. Research logs expire after seven days and are deleted on the next accepted chat request. Sidebar conversations are separate from research logs, private to your signed-in account, and retained until you delete them from chat history. The assistant’s separate recall history keeps questions and server-generated answers for 365 days from conversation creation. Archived recall conversations are excluded from recall. Expired recall text is deleted on subsequent chat requests; physical deletion may be delayed while the service is idle. Retrieved recall text may be sent to OpenAI when you request recall or continuation. Deleting a sidebar conversation also deletes its linked recall text. In local development, they are saved only in the local app. Deleting a saved conversation does not remove research logs before their expiry or revoke shared snapshots. Account records are separate and do not automatically expire with these logs. Sign-in sessions last up to seven days; signing out revokes the current session.

Services used to answer your question

Conversation content and relevant source material are sent to OpenAI. Research queries may also be sent to web-search providers, including Keenable. Our login integration does not add your Google name or email to research prompts. Providers process the data sent to them under their own policies. Do not submit confidential information or sensitive personal information.

Shared answers

Choosing Share Link publishes the conversation through that answer for anyone with the link. Shared snapshots do not automatically expire with private research logs. Your Google name and email are not added to shared answers, but any personal information you type into the conversation may be included. Contact us if you want a shared snapshot removed.

Cookies, drafts, and technical information

Essential cookies keep you signed in. Your browser temporarily saves your draft and conversation during sign-in. The draft is valid for 30 minutes and is removed when restored or when an expired draft is checked; browser session storage may retain it until then or until the tab closes. We use your signed-in account to limit chat requests. Our hosting and analytics services process technical usage information to operate and measure the site.

Anonymous browsing on Home and Schools

We use a random browser cookie shared by the home page and school inspector. Its 400-day expiry is renewed when you request a page, keeping the same identifier while the cookie remains in your browser. A separate session cookie expires after 30 minutes without recorded browsing activity. These cookies are independent of Google sign-in. We privately record gateway requests with these identifiers, page, school name, city and code when available, selected year and district, response status, and response time. Logs expire after 30 days and are removed in batches on subsequent page requests. They do not include visitor names, emails, IP addresses, typed searches, or full referring URLs. We also record navigation inside the school inspector, including school codes, names and cities when available, and selected year, district, dashboard tab and teacher benchmark. These records are stored privately on Render with the same 30-day expiry. They identify a browser, not a person. Blocked logging requests, cached assets and browser-only errors may leave gaps. Clearing or blocking these cookies creates separate or unlinked activity.

Your choices and contact

You can sign out at any time and revoke Google access through your Google Account settings. Revoking Google access does not itself delete records held by EdVoice Data. For privacy questions or to request access to or deletion of your account, research records, or shared snapshots, email stopman@gmail.com. We may need to verify that the request comes from the account holder.

Updates

We may update this policy as the service changes. The date below identifies this version.