Privacy at TryHabla

Who this notice covers

This notice applies to teachers, students, and other people who use TryHabla or contact us. TryHabla is designed for teacher-directed speaking assignments. It is not offered to children for independent personal use.

TryHabla is operated by David Garcia.

Information TryHabla handles

The information depends on how the service is used and can include:

• Account information: name, email address, sign-in provider profile, role, and authentication/session information.
• Classroom information: class and roster membership, assignment titles, instructions, rubrics, target language, and teacher-uploaded attachments.
• Submission information: a student-entered name, account email, audio recording, an optional or teacher-required camera video where authorized for the classroom, submission time, grade, rubric score, and teacher feedback.
• Support and operations information: contact-form messages, basic activity events, request information used for security and rate limiting, and local browser settings such as theme or dismissed notices.
• Public-site analytics, when enabled: page views and limited interaction events on consented adult-facing public marketing and contact pages. Student-facing, teacher-registration, billing, authentication, and classroom pages do not load the tag. TryHabla does not send student names, emails, recordings, transcripts, assignment text, rubric text, or classroom identifiers as analytics event parameters.
• Product billing information, only when paid features are used: Stripe billing status, AI-assisted recording allowance totals, and identifiers returned by Stripe. Stripe handles product-payment credentials on its own checkout and portal pages.
• Donation information: PayPal handles a voluntary donation on its own site if a person chooses a donation link. TryHabla does not use a PayPal donation to activate product access, subscriptions, or AI credits.

Public-site analytics

When Google Analytics or Google Tag Manager is enabled, TryHabla limits that instrumentation to an explicit set of adult-facing public acquisition and contact pages, and loads the tag only after the visitor chooses “Allow analytics.” Student-facing, registration, billing, authentication, student workspace, assignment-submission, teacher classroom, admin, and API routes are excluded from TryHabla's analytics event layer.

The limited events can include the page path, page title, navigation destination, and contact or school lead submission. Google may also receive ordinary technical information associated with web analytics, such as browser/device information, referrer information, and network information after consent. TryHabla configures its direct Google Analytics tag without Google Signals or ad-personalization signals. Visitors can keep analytics off; that choice does not affect access to TryHabla.

Optional AI transcription and grading

AI transcription and grading are optional and controlled by deployment settings and teacher actions. A teacher can request a transcript individually, request a transcript-only batch, or enable automatic transcription for future submissions to a specific assignment. When any of those options is used, the student's recorded answer may be processed by the AI service provider or providers configured for that TryHabla deployment. Students are told on the assignment page when automatic transcription is on. A transcript can be generated without an AI grade. If grading is requested, the transcript, assignment instructions, and rubric may also be processed. TryHabla may store the transcript, AI-generated score, rubric details, feedback, evidence excerpts, provider and model identifiers, usage details, and attempt status with the submission.

AI-generated grading suggestions remain teacher-only until a teacher reviews and explicitly saves the final score and feedback. Teachers can edit, replace, or decline a suggestion. TryHabla does not promise that a transcript or AI result is accurate, and teachers remain responsible for classroom grading decisions. The teacher or school is responsible for deciding whether AI is authorized for the activity. That decision does not remove TryHabla's responsibility for its own processing and notices.

On a video assignment, TryHabla stores the camera recording privately for teacher review. TryHabla does not use AI to assess video or appearance. The sound track is also saved as an audio recording, and the assignment's usual audio transcription setting may apply. The teacher reviews the video and chooses the final grade.

As of this notice's update date, the production service identifies OpenAI as its transcription and grading provider, with requests potentially routed through Vercel AI Gateway. TryHabla does not promise a particular provider retention mode; schools can ask for the current configuration and provider-control status before authorizing AI use.

Why TryHabla uses information

• Authenticate users and provide the teacher and student classroom workflows.
• Store, play back, grade, and display speaking submissions.
• Operate optional AI transcription and grading and enforce AI recording allowances when those features are enabled.
• Prevent abuse, enforce limits, troubleshoot problems, and secure the service.
• Respond to support messages and understand basic service activity.

Optional Google Drive export

When this feature is enabled, a teacher can choose to export a transcript or original recording to a clearly named TryHabla folder in the teacher's or school's Google Drive. The export is user-directed and uses Google's limited drive.filepermission, which lets TryHabla create and work with files created through this feature; it does not give TryHabla permission to read the user's entire Drive.

The short-lived Google access token is held only in browser memory for the export. TryHabla does not store a Google Drive refresh token. Exported copies are controlled by the teacher or school through its own Google Drive account and policies. They remain there independently until an authorized Google Drive user deletes them. Deleting the related content from TryHabla does not delete a previously exported Drive copy.

Who information may be shared with

The application uses service providers to operate. Depending on deployment settings, these can include Google or Microsoft for sign-in; Google Analytics and Google Tag Manager for the limited public-site analytics described above when enabled; Vercel for hosting and file storage; Turso for the application database; Upstash for rate limiting; Resend or an operational notification service for messages; Stripe for optional product billing; PayPal only when a person chooses to make a separate voluntary donation; and configured AI infrastructure and model providers when AI is enabled.

Classroom information is made available in the application to the student who owns a submission and the teacher who owns the class, as appropriate. The TryHabla operator and service providers may also handle information where needed to operate, secure, support, or comply with valid legal requirements. TryHabla does not provide a student-to-student recording-sharing feature.

Which optional providers are active, their processing locations, and their own log or backup schedules depend on the production configuration. A school can ask for the current deployment details before approving use of TryHabla.

Retention and deletion

Active classes, assignments, submissions, recordings, grades, and feedback remain while they are needed for the classroom workflow. When an authorized user deletes a class, assignment, or submission, TryHabla currently keeps the soft-deleted record for a 30-day recovery period. After that, the scheduled cleanup hard-deletes the database record and attempts to delete associated media.

AI transcript and attempt records follow the related submission. Contact messages remain until an administrator deletes them. Account records and basic activity events do not yet have an automatic deletion schedule. If public-site Google analytics is enabled, analytics data follows the retention settings of the configured Google Analytics property. Service-provider logs and backups may follow separate schedules that are still being verified for district use.

Where video is enabled, private video files are deleted after the configured video retention period of up to 90 days. Files become eligible for deletion at that point; scheduled cleanup normally removes them within the next 24 hours. Unsubmitted uploads become eligible after 24 hours and are normally removed within 48 hours. Failed deletions are retried; outages or cleanup backlogs can delay removal. The submission record, sound track, grades, and feedback may remain under the classroom and deletion schedule above. Service-provider backups may last longer.

TryHabla does not promise permanent storage. A user-directed Google Drive export is a separate copy governed by the teacher's or school's Google account, not an extension of TryHabla's retention or deletion process.

Access, correction, and deletion requests

Teachers can delete the classes, assignments, and submissions they control. Students can delete their own submissions from the student dashboard. For an account, roster, support-message, access, correction, export, or other deletion request, email davidsgarcia325@gmail.com. We may need to verify the requester and coordinate requests about school-managed student data with the school. Parents and guardians should normally begin with the student's school.

Students and school authorization

Students, including minors, should use TryHabla only for a teacher- or school-directed activity. The teacher or school must decide whether the service and any optional AI use are appropriate and obtain any authorization or consent its policies and applicable law require. TryHabla remains responsible for its own legal obligations and for responding to verified requests it is required to handle. A public TryHabla page does not establish district approval.

Security and updates

TryHabla uses measures such as authenticated sessions, role and class-ownership checks, input validation, access-controlled media routes, rate limiting when configured, and scheduled deletion. No online service can guarantee absolute security. Service controls, providers, and this notice may change; material updates will be posted here with a new date.