Privacy Policy

When you use Google with Instagrity, the Google user data Instagrity accesses depends on the feature you choose to connect.

Google Sign-In. Instagrity may receive your Google account email address and Google account identifier to authenticate you, create or locate your Instagrity account, protect account access, and route you into the correct teacher, student, or admin workspace.

Google Drive import. Instagrity may receive your Google account email address, basic profile information, Google account identifier, selected file metadata, and the contents of files you explicitly select through the Google Drive Picker or an equivalent Google file-selection flow. Instagrity uses this data to import files you choose as classroom materials, assignment materials, or student-submission attachments.

Google Classroom integration. Instagrity may receive your Google account email address, basic profile information, Google account identifier, course lists, course metadata, roster information (Google Classroom user identifiers and student display names), grade-category data, coursework metadata, due dates, links, and related Classroom identifiers. Instagrity does not import or collect Google Classroom student email addresses. Instagrity uses this data to help teachers or authorized school users connect classes, map Google Classroom courses to Instagrity classes, preview or import rosters as Google Classroom roster placeholders, map categories, and import or sync coursework where the integration is enabled. Roster placeholders are matched to Instagrity student accounts when the student signs in or connects their Google account.

How Instagrity uses Google user data. Instagrity uses Google user data only to provide and improve user-facing Instagrity features that the user or organization authorizes. Google user data is used for authentication, account identity, selected Google Drive file import, Google Classroom course and class mapping, roster preview, import, and roster placeholder matching, category and coursework mapping, import, and sync, and for security, abuse prevention, support, audit, and legal compliance where needed.

No sale of Google user data. Instagrity does not sell Google user data.

Prohibited uses. Instagrity does not use Google user data for targeted advertising, personalized advertising, retargeting, interest-based advertising, selling to data brokers, providing to information resellers, determining credit-worthiness, lending, surveillance, or creating unrelated databases. Instagrity does not use Google user data to train AI models unrelated to the Instagrity service. If Google-derived classroom content is included in an Instagrity AI-assisted workflow requested by a teacher, student, or authorized school user, that processing is limited to providing the requested user-facing Instagrity feature.

Sharing and transfer. Google user data may be processed by Instagrity’s authorized infrastructure and service providers (Supabase, Vercel, OpenAI, Stripe, Google, Resend, and similar providers) only as needed to operate the service. Instagrity does not transfer Google user data to third parties for advertising, resale, data brokerage, credit, lending, surveillance, or unrelated model training. AI providers process classroom content only when an AI-assisted feature is requested and only to provide that feature. Stripe generally processes billing data rather than classroom or Google-derived content unless incidental account metadata is involved.

Data protection. Instagrity uses encryption in transit and managed infrastructure protections for data at rest. Access to Google user data is limited to authorized personnel and service providers who need access to operate, secure, support, or maintain the service. Instagrity uses application access controls, server-side integration routes, Supabase row-level security where applicable, rate limiting, challenge verification where configured, security-event logging, and audit-oriented records to help protect user data from unauthorized access, disclosure, alteration, or loss.

Human access. Humans do not review Google user data except when needed to provide support requested by the user or their school, investigate abuse or security issues, comply with legal obligations, or operate internal aggregated or de-identified service operations. When a teacher or school administrator intentionally imports or uses Google-derived content in Instagrity, normal teacher, administrator, and authorized collaborator access inside the product is part of the authorized classroom workflow.

Retention and deletion. Google account identifiers and connected external-account metadata are removed or disconnected from active service records when you delete your Instagrity account or disconnect the integration, subject to backup, legal, and audit retention. Google Drive files imported into Instagrity become classroom, assignment, or submission content and follow the same deletion and retention practices as other classroom content. Google Classroom imported or mapped classes, rosters, invitations, assignments, mapping records, and sync logs follow product deletion, administrative handling, and legal or audit retention practices. If Google access is revoked or tokens expire, Instagrity marks the connection state and stops syncing until reauthorization occurs.

When Microsoft sign-in is enabled and a user chooses it, Instagrity may receive the user’s Microsoft account email address, account identifier, and basic profile details needed for authentication. Instagrity uses this data to create or locate the user’s Instagrity account, protect account access, and route the user into the correct workspace. Microsoft sign-in data is used only for authentication and account identity within the Instagrity service. Instagrity does not sell Microsoft sign-in data or use it for advertising, data-broker resale, credit-worthiness, lending, or unrelated AI model training.

Instagrity uses Stripe to support subscription checkout, billing, seat purchases, invoices, refunds, disputes, and payment-status handling. Instagrity may store Stripe customer identifiers, subscription status, purchased seat counts, invoice or checkout references, refund and dispute metadata, and entitlement records needed to operate paid plans. Payment card details are handled by Stripe and are not stored or used by Instagrity for classroom workflows. Billing data is used for account administration, payment support, accounting, audit, abuse prevention, and legal obligations. Stripe does not receive classroom content or external-provider user data from Google or Microsoft integrations unless incidental account metadata is involved.

When a teacher, student, or authorized school user requests an AI-assisted feature, Instagrity may process relevant classroom content through AI service providers to provide grading, feedback, coaching, assessment, rubric, or instructional-support features. AI processing is limited to the requested Instagrity feature and related service operations. Instagrity does not sell classroom content or external-provider user data to AI providers. Instagrity does not use that data for targeted advertising, data-broker resale, credit-worthiness, lending, or training AI models unrelated to the Instagrity service. Premium teacher seats and entitlement rules govern whether AI features are available for a given classroom workflow.

Instagrity uses infrastructure providers to host the application, authenticate users, store product data, deliver transactional emails, monitor reliability, and protect the service.

Supabase may process authentication, database, storage, and access-control data.

Vercel may process hosting, deployment, performance, and request data needed to serve the application.

Resend may process recipient, sender, subject, delivery, and message-content data needed to send service emails.

These providers process data only as needed to operate, secure, support, or maintain Instagrity. They do not receive data for advertising, data-broker resale, credit-worthiness, lending, or unrelated model training. Additional infrastructure providers may be introduced as the product evolves. See the Service providers and subprocessors section below for additional detail.