Section 01
Who is responsible
Jabez Collano operates Taramon and is responsible for decisions about the personal information described in this notice. Contact support@taramon.app for privacy questions or requests.
This notice covers Taramon's website, accounts, contribution tools, support button, and early-access registration. It takes effect on October 15, 2026. It does not replace the independent privacy notices of external websites or sign-in providers.
Taramon does not run advertisements, use analytics tracking, or sell personal data. Necessary authentication, service operation, and abuse-prevention processing still occur as explained below.
Section 02
Information the service handles
The information involved depends on which parts of Taramon you use:
- Accounts: email address, account identifier, authentication records, and information provided by your chosen sign-in method. Email-and-password sign-in is handled by Supabase Auth. Google sign-in may supply your email address and basic profile information; it does not give Taramon your Google password.
- Profiles: the name, username, and age you enter, your membership role, account timestamps, and your public-credit preference.
- Contributions: the Filipino phrase, Bikol translation, selected dialect, confidence level, ownership confirmation, submission time, and review status. Older submissions or other supported clients may also contain examples or notes. Review records can include reviewer identifiers, decisions, and rejection reasons.
- Early access: your email address, signup time, and a hashed representation of your network IP address.
- Support button: a randomly generated browser identifier, support time, and a hashed representation of your network IP address. A flag on your device remembers that you have already supported the project.
- Technical information: requests necessarily expose network and browser information to the infrastructure serving the website. Service providers may keep operational and security logs.
- Messages you send: contact information and the contents of requests, feedback, or reports you choose to send to the operator.
An IP hash and a browser identifier are pseudonymous identifiers, not a guarantee of anonymity. Please do not put passwords, private contact details, or information about other people into translation submissions.
Section 03
Why information is used
Account and profile information supports sign-in, account management, age-related feature restrictions, and access permissions. Contributions and review records support checking translations, managing submissions, and recognizing community work. Early-access details support the updates you request. Network hashes and browser identifiers help limit repeated submissions and misuse.
Information may also be needed to answer requests, investigate security incidents, resolve disputes, and meet applicable legal obligations. Not every activity relies on consent: the appropriate basis depends on the information and purpose, including providing a requested service, legitimate security interests, a legal obligation, or consent where required. Reading this notice does not itself give blanket consent to unrelated uses.
Section 04
What other people can see
Approved translations may be included in Taramon's public collection. When your credits setting is enabled and you have an approved contribution, the credits wall can display your username, role, and number of approved translations. The current profile setting starts enabled; you can turn it off using the credits control on the Contribute page.
Your email address, profile name, and age are not displayed on the credits wall. Authorized administrators and reviewers have access needed for their roles. Submissions awaiting review are not intended as public posts.
Public material can be copied or indexed by others. Turning off credits removes your listing from Taramon's credits display, but cannot recall copies already made by other people or search engines.
Section 05
Cookies and browser storage
Authentication uses cookies to maintain and refresh your signed-in session. Blocking or clearing these cookies can sign you out or prevent account features from working.
The support button stores a random identifier and a supported flag in your browser's local storage. Local storage remains until it is cleared by you or your browser; it does not automatically disappear when you close a tab. Clearing it does not remove the corresponding server record.
You can manage cookies and site storage through your browser settings. Google applies its own cookie and privacy practices when you choose Google sign-in.
Section 06
Service providers and disclosures
We use Vercel, Hostinger, Supabase, and Google sign-in to support the service. Their access depends on the function they provide and the information passing through it:
- Vercel and Hostinger: website and supporting hosting, domain, or infrastructure services, as configured. These providers may process technical requests and operational records. See Vercel's Privacy Policy and Hostinger's Privacy Policy.
- Supabase: authentication and database services for accounts, profiles, contributions, support records, and the waitlist. See Supabase's Privacy Policy.
- Google: optional Google sign-in. Google handles authentication under its own terms and provides the account information needed for sign-in. See Google's Privacy Policy.
Authorized people may access information to administer the service, review contributions, respond to requests, and investigate abuse. Information may also be disclosed when required by law or reasonably necessary to protect legal rights and safety, subject to applicable safeguards. We do not share data with advertisers or data brokers.
Section 07
Where information is processed
Our providers operate internationally. Depending on deployment regions, support access, and provider infrastructure, information may be processed outside your country. The website does not promise storage exclusively in the Philippines or any other single country.
Applicable transfer requirements and appropriate contractual and security safeguards must be observed when personal information is handled across borders. You may contact the operator for information about the providers and locations relevant to your data.
Section 08
Retention and deletion
Planned account retention: delete inactive accounts after 50 consecutive days of inactivity. Planned early-access retention: expire and remove waitlist email registrations 7 days after signup.
Current status: scheduled deletion is not yet active. Account and waitlist records do not currently disappear automatically at these deadlines. Until the schedules are operational, request removal by emailing support@taramon.app. We will update this notice when the schedules are active and explain how account activity is measured.
Contribution and review records support the community collection and moderation. Deleting an account can also remove its linked profile, contributions, and review records; do not treat account deletion as a way to preserve contributions anonymously. Public material already copied by others cannot necessarily be recalled.
Support identifiers and hashed IP records currently have no automatic expiry. The 24-hour abuse-check window is not a deletion schedule. Contact us to request removal of personal information associated with these records; identifying a browser-only record may require additional details.
Information necessary for legal obligations, security investigations, or disputes may need to be retained for the relevant purpose. Provider logs and backup copies may remain for their applicable retention cycles after removal from active systems. We cannot promise instantaneous erasure from every backup; contact us for details relevant to your request.
Section 09
Security and access
Taramon uses authentication and role-based access controls to restrict account and review functions. Service credentials belong on the server, and users should keep passwords and sign-in links private. No internet service can promise perfect security.
If you suspect unauthorized access, contact the operator promptly and secure your sign-in account. Where an incident triggers notification duties under applicable law, affected people and the relevant authority must be informed as required.
Section 10
Children and younger users
Taramon's account, contribution, and early-access services are intended for people aged 13 and older. Users below the age of legal adulthood should involve a parent or guardian, and any stricter local age or consent requirement applies.
The account-setup form asks for age, but this is not independent age verification. We do not intentionally invite children under 13 to provide personal information. If you believe a child under 13 has created an account or submitted information, contact support@taramon.app so we can investigate and arrange appropriate removal or restriction.
Section 11
Your choices and privacy rights
You can change your public-credit preference on the Contribute page and manage browser storage locally. Contact the operator to request account access, correction, deletion, removal from the early-access list, or help with information you cannot change in the interface. The website currently has no self-service account-deletion button.
Depending on the law and circumstances, you may have rights to be informed, access and correct your personal data, object to processing, request erasure or blocking, withdraw consent, obtain portable data, and seek remedies for privacy violations. These rights are subject to applicable conditions and exceptions; withdrawing consent does not undo lawful processing already completed.
A request may require proportionate identity verification. Do not send your password. If information must be retained for a legal obligation or dispute, the response should explain the relevant limitation.
For Philippine privacy rights and complaints, see the National Privacy Commission's guidance and official contact channels. Contacting Taramon first does not remove your right to approach the regulator.
Section 12
Changes to this notice
We may update this notice when the service, providers, retention practices, or legal requirements change. The date at the top identifies the current version. Material changes will be communicated through an appropriate notice, and consent will be requested where required before a new consent-based use begins.
A change to this notice does not by itself authorize an unrelated use of information already collected.
Section 13
Contact and requests
Jabez Collano
Taramon operator and privacy contact
support@taramon.app
For privacy requests, include the email or username associated with your account, the request you want us to handle, and enough context to locate the information. If possible, write from the registered email address. We may need to verify your identity, but will not ask for your password.
You may use the same address to leave the early-access list, report a child-safety concern, request a correction, or ask about deletion. Requests will be handled in accordance with applicable legal requirements; some requests may require clarification or be subject to lawful exceptions.