1. Who handles your information
Signia is operated by a student thesis project team in the Philippines. For privacy questions, access or correction requests, or account closure, contact signiafsl@gmail.com and identify the Signia account concerned. Do not send your password or verification codes. The team may request proportionate verification before acting on an account request.
This notice describes the platform’s data handling. Acknowledging that you have read it is separate from agreeing to the Terms of Service and is not blanket consent to unrelated processing, marketing, or thesis research.
2. Account and sign-in information
Email registration uses your name, email address, password, and verification code. Passwords are stored as hashes. Google sign-in supplies your Google identifier, name, email and verification information, and profile picture when available. Google credentials are used to verify the sign-in request; Signia does not receive your Google password.
We keep account status, role, creation and activity dates, and authentication tokens to operate and secure accounts. For new registrations, we record the accepted terms version, acknowledged privacy-notice version, acceptance time, and whether registration used email or Google. We do not label an older account as having accepted this version simply because it exists.
3. Learning activity and public recognition
Signia stores profile information and learning activity such as lesson progress, quiz answers and attempts, scores, recognition results, accuracy, XP, streaks, achievements, heart balances and transactions, and story progress. These records provide feedback, preserve progress, and support the game rules.
Finisher and recognition features can publicly display your name, avatar, and learning statistics. Choose a display name and avatar you are comfortable making public. Contact the team if you need help correcting or removing displayed information.
4. Camera images and recognition
When you enable camera practice, the browser captures images and sends them to Signia’s configured recognition service for processing. This processing is not limited to your browser. Recognition produces results such as detected signs, confidence scores, and hand landmarks; learning records may retain results and accuracy.
The current practice flow processes images for predictions rather than providing a saved video-recording feature. This notice does not promise that hosting or diagnostic systems keep no technical records. Keep faces, bystanders, documents, and private surroundings out of view where possible. Stop the camera or revoke browser permission to stop further capture.
The current Signia learning app does not send camera-practice images or recognized sign words to Google Gemini. Its camera-practice flow uses Signia’s recognition service to return predictions.
A separate recognition testing page has a Gemini translation feature. If you use that testing page’s Translate with Gemini button or Auto-Translate option while Gemini is configured, it sends recognized sign words to Google Gemini to generate a sentence. That translation request contains text, not camera images. This testing feature is not part of the current Signia learning app.
5. Payments and support
Purchases and refunds create records including item, quantity, amount, currency, payment-provider references, status, timing, refund reasons, and support explanations. PayMongo and your selected payment provider handle payment credentials under their own policies. Signia uses transaction references and statuses to verify delivery, handle disputes, and reconcile payments.
Contact and support forms send your name or account identity, email, subject, and message to the team through its email service. Payment and refund notifications also use email. Avoid including sensitive details that are not needed to resolve your request.
6. Purposes and lawful grounds
We process information needed to provide the account, learning features, requested purchases, and support; to meet applicable legal obligations; and, where appropriate, for legitimate interests such as protecting accounts and investigating abuse, subject to your rights. Where consent is the applicable basis, it must be specific to the processing described and may be withdrawn subject to lawful limits.
Ordinary service use is not consent to participate in thesis research. Before using identifiable participant information for a separate study, the team must provide the study information and any required consent or guardian process. Research participation, publication of identifiable results, and optional recording must not be inferred from the signup checkbox.
7. Service providers and access
Authorized project administrators can access information needed for service administration and support. Relevant information is processed by the infrastructure and email providers used to run Signia, Google for Google sign-in, Cloudflare Turnstile for bot checks, and PayMongo and payment providers for checkout and refunds. Google Gemini is used only by the separate translation testing feature described above, not by the current learning app’s camera-practice flow.
Third-party services may process information outside the Philippines and have their own privacy notices and retention practices. Information may also be disclosed where required by law or necessary to address a lawful claim. Contact the team for information about the providers used in the deployed version.
8. Browser storage and security
Signia saves your player preferences, including sound, camera mirror view, preferred signing hand, high contrast, and the home-page practice reminder, with your account in its database. They remain available when you sign in to the same account on another device. Changing your IP address, signing out, or clearing browser storage does not delete saved account preferences, learning progress, or purchase records.
Cookies and local browser storage hold sign-in tokens, account display details, and temporary application state. Sign-in cookies can persist for up to 30 days, and the server rejects authentication tokens after 30 days. Some local browser data may remain until cleared. Each browser or device has its own session; signing out revokes that session when the server is reachable and clears local sign-in details. Sign out on shared devices. Camera permission is managed separately by each browser.
Access controls and password hashing help protect information, but no online service can guarantee absolute security. Report suspected unauthorized access to the team promptly.
9. Retention and account closure
Account and learning records remain associated with your account while it is maintained. Contact the team to request closure, deletion, or a review of information still needed. There is currently no automatic account-deletion schedule in the application.
The team must assess what may be removed and what must be retained for applicable legal obligations, unresolved transactions, security, or disputes. Payment records, email records, logs, and backups may have different retention periods. You can request details of the applicable period and the outcome of your deletion request; stopping use alone does not erase these records.
10. Your rights and complaints
Subject to the conditions and exceptions in Philippine privacy law, you may request information about processing, access to your data, correction, objection, erasure or blocking, and data portability where applicable. You may withdraw consent for processing based on consent and seek remedies for violations. Some requests may affect features that need the information.
Send requests to signiafsl@gmail.com. You may also raise a complaint with the Philippine National Privacy Commission through privacy.gov.ph. Acknowledging this notice does not waive your rights.
11. Changes and questions
This notice is dated and versioned so you can identify what was presented at signup. Material changes to purposes or data handling should be communicated before they occur, with separate consent sought where needed. Contact the project team if anything is unclear before enabling a feature or submitting personal information.