Política de privacidade

Scope and responsibility

This Privacy Policy describes how Terrier Plan (the “Planner”, “we”, “us”) handles information when you visit this website, create an account, save an academic plan, or use its AI assistant. The website maintainer is responsible for the Planner’s own data practices and can be contacted at terrier-plan-support.sprung163@slmail.me.

The Planner is an independently maintained planning tool. It is not Boston University’s official registration system, does not use BU single sign-on, and does not request your BU Portal password or Duo approval. Public university course information is used as a reference. A plan or AI answer does not constitute an official university decision or confirmation of graduation eligibility. This policy covers the Planner; third-party websites and services also have their own policies.

Information we process

Account information includes a username, an internal account identifier, an account creation date, accepted terms version when recorded, and a password hash for password-based accounts. We do not store your password as readable text. If you choose Google sign-in, we receive and store the verified email address and stable Google account identifier needed to recognize that account; Google may also provide a display name and basic public profile information. We do not receive your Google password.

Planning information is information you enter or choose: degree and minor, semesters, selected courses and sections, course status, grades or GPA if supplied, external credits, equivalencies, approval status, notes, graduation target, career interests, and course, Hub, and workload preferences. You should enter only information relevant to planning and avoid unnecessary sensitive information about yourself or other people.

Technical information may include an IP address used for request limiting, browser and request information processed by the hosting platform, timestamps, request paths, response status, diagnostic events, and model/token usage counters. If you email us, we process your email address, message, and information needed to respond. Public course and professor-review data comes from public sources and is distinguished from your private academic records.

How information is used

We use account information to authenticate you, maintain sessions, keep accounts separate, and protect saved plans. Planning information is used to show your plan, calculate modeled degree and Hub progress, check prerequisites and published schedules, propose changes, and tailor recommendations to your stated interests. Preferences you submit during setup are saved for later planning and assistant requests.

Technical information supports reliability, abuse prevention, request limiting, error diagnosis, and monitoring AI usage and cost. We use correspondence to handle support and privacy requests. The Planner does not add advertising trackers or sell personal information. Where a legal basis is required, processing depends on the requested service, necessary security and operational interests, applicable legal obligations, or consent where required. This policy itself is not a substitute for consent that applicable law separately requires.

AI requests and provider selection

Using the AI assistant sends your current question, recent conversation, saved planning preferences, and relevant live-plan and course information to the selected AI provider so it can answer in the context of your degree, missing Hub requirements, selected courses, and workload. The automatically prepared model context excludes raw course grades, GPA, private course notes and secret credentials; it may include course status, derived requirement checks and relevant external-credit details. Anything you type or paste into the conversation is still part of your submitted message. Degree setup and course recommendations also send the relevant plan, requirements, preferences and course evidence to shared Cloudflare AI when you choose AI planning. Standard planning is available without model inference; it is used when the shared free allowance is unavailable. When a Chinese course page has no matching stored translation, the Planner can send that public official course description or prerequisite text to shared Cloudflare AI for translation. This translation request does not include your plan, grades, preferences, chat messages or personal API key. Public translated text is cached by its source version and can be reused across accounts; this cache is distinct from private account data.

Chat requires your connected personal API from DeepSeek, OpenAI, Google Gemini, Groq or OpenRouter. Shared degree planning does not use your personal key or switch to a paid provider: when the free allowance is reached, it uses standard planning, and shared AI can be used again after the daily reset. This is a website-wide allowance, not a separate allowance for each user. A new account does not inherit the maintainer’s private key. The Planner selects available models automatically by default; advanced users can specify models. Simple and complex questions may use different models or reasoning settings. OpenRouter supports free models and personally configured paid models, and may route your request to an underlying model host that also receives the submitted content. Automatic selection uses its free router; paid model IDs you configure use your own API balance. Free plans remain subject to provider quotas and availability. Google states that unpaid Gemini services may use submitted content and responses to improve its products; consult the applicable terms for your account. Your provider handles billing and may charge your API balance; this Planner does not collect your payment details.

AI providers handle submitted information under their applicable service terms and privacy policies. Their retention and model-improvement practices may differ; this website does not make a blanket promise that every provider retains nothing or never uses inputs for model improvement. Review the provider policies before submitting information you consider sensitive. Model output can be incorrect. Proposed course changes remain subject to your review and confirmation; the assistant does not make admissions or official academic eligibility decisions.

Google sign-in

Google sign-in is available only after this website’s real Google client configuration is enabled. It requests basic identity scopes (openid, email, and profile). It does not request access to Gmail, Google Drive, your Google Calendar, or offline access. The Planner uses the verified account identifier and email to authenticate the Google account; it does not store Google access or refresh tokens.

A Google identity is not automatically attached to a password account simply because email text matches. Google consent and account-security controls are managed by Google. Password-based registration and login remain independent of Google. If Google sign-in is not available, use a username and password.

Service providers and disclosure

Cloudflare provides application hosting, plan/account storage, security and request-limiting infrastructure, and the optional shared AI service. Google provides identity verification when you select Google sign-in. Your selected personal provider receives the AI request when you use that service. Information is disclosed to these providers as needed for the selected function, rather than making your plan public to other Planner accounts. Email sent to our support alias is forwarded by SimpleLogin to a Microsoft Outlook mailbox. These mail services process the sender and recipient addresses, message contents and delivery metadata needed to forward, store and respond to that correspondence; they do not receive your saved plan simply because you use the website.

The website maintainer may access information as reasonably necessary for support, security, maintenance, or a verified privacy request. We may disclose information where applicable law requires it or when reasonably necessary to investigate abuse, protect the service or its users, or respond to a valid legal request. Links to BU, Rate My Professors, Reddit, and other external sources take you to services with their own data practices; following a link is distinct from publishing your academic plan.

Storage, transfers, and retention

Account records, saved plans, and preferences are stored using Cloudflare infrastructure. Providers can process information in countries different from where you live. Do not assume this website or its AI providers process all information only in your home country. Where applicable law requires transfer safeguards, those requirements remain relevant to the provider relationship and the particular processing.

Saved account and plan records currently have no automatic inactivity-deletion deadline. You can delete a registered account after identity confirmation in Account settings. They remain until you change them or a verified deletion request is handled, subject to justified retention for security or legal obligations. Unsaved-plan backups remain in your browser until removed or browser storage is cleared. Current chat messages are held in the page’s temporary browser state and are not saved by this application as a durable server chat archive; the recent conversation is still transmitted when you send another AI request.

Our AI usage logs contain provider/model and actual token/cache counters, rather than the question text or API key. Hosting-platform request and diagnostic logs follow the platform’s current settings and retention limits. Provider-side copies and service logs follow the provider’s own policies; clearing this browser does not delete them. We do not promise instant removal from every provider or backup system. A deletion request can be made using the contact address below.

Cookies and local browser data

The Planner uses a necessary sign-in cookie, with a lifetime of up to 30 days, and language-preference cookies, with a lifetime of up to one year. A temporary Google verification cookie is valid for up to 10 minutes. Expiry describes how long it can be used, not a claim that every related server record is deleted at that exact moment.

Cookies used for login are protected with HttpOnly, Secure, and same-site restrictions. Browser storage keeps unsaved-plan backups scoped to an account and a temporary indicator that a provider-switch notice has been shown. These serve continuity and interface behavior, not advertising. Blocking cookies can prevent login. Clearing browser storage can remove unsaved work. Sign out on shared devices; browser backups can remain on that device after sign-out.

Security and account separation

We use password hashing, signed expiring sessions, account-specific storage and browser-backup identifiers, origin checks, request limits, and owner-only access for shared catalog changes. Stored personal API keys are encrypted on the server and are not returned to the browser as plain text. Google sign-in uses server-side verification, a one-use state check, PKCE, and a nonce. Registration can use Cloudflare Turnstile to detect automated requests. When enabled, Cloudflare processes the visitor’s IP address, technical browser signals and a short-lived verification token; the Planner validates the token on the server before creating the password account. This check does not verify legal identity or require an identification document.

These measures reduce risk but cannot guarantee absolute security. Use a unique password and protect the account and devices you use. Do not send passwords, API keys, identification documents, or unrelated sensitive records in support email or assistant messages. The Planner does not obtain authority to change your official BU records or enroll you in a course.

Your choices and privacy requests

You can edit your course plan, degree settings, external-credit information, and planning preferences through the available tools; change the interface language; sign out; and choose not to use the AI assistant or Google sign-in. Password accounts can change their login details in account settings. Google accounts manage their Google credentials through Google.

You may contact terrier-plan-support.sprung163@slmail.me to request information about your account data, a copy, correction, or deletion, or to raise a privacy concern. Depending on applicable law, you may also have rights to restrict or object to certain processing, receive portable data, withdraw consent where consent is the basis, or complain to an appropriate supervisory authority. These rights can be subject to legal conditions and exceptions.

Please identify the account and the request without sending its password or API key. We may ask for reasonable verification before disclosing or deleting private information, and will handle the request according to applicable requirements. Registered accounts can use Delete account in Account settings after identity confirmation. This removes the account’s saved plan, preferences, stored API configuration and sign-in associations. A minimal deletion marker prevents late in-flight requests from restoring that data. Browser drafts on this or other devices and provider-side records are separate; clear local website data on each device if needed. Deleting the stored API key does not revoke the key at its provider or delete your Google account. Removing a course or clearing your browser is not the same as deleting the server account. Withdrawing an optional choice does not undo processing already lawfully performed.

Young users

The Planner is intended for university course planning and is not designed as a service directed to children. It does not currently verify every user’s age. If a parent or guardian believes that a child has submitted information that should not have been collected, contact terrier-plan-support.sprung163@slmail.me so the matter can be investigated and appropriate action taken. Users who require a parent or guardian’s permission under applicable rules should obtain it before submitting information.

Policy updates

We may update this policy when the website’s features, providers, data practices, or applicable requirements change. The effective and last-updated dates will be revised on this page. Where a material change requires additional notice or consent, it will be handled as required rather than treating publication alone as sufficient. The available language versions are intended to describe the same practices; contact us if a translation appears unclear or inconsistent.

Course-file imports and exports

If you choose a MyBU PDF or CSV, the import reader processes the file in your browser. The original document, its filename and its full extracted text are not uploaded to the Planner server or sent to an AI provider by this import function. The reader uses a locally served PDF library; it does not sign into MyBU or obtain authority to access your university account.

Recognized course identifiers are sent to our course catalog endpoint to locate their public records. The preview can show course identifiers, terms, status, grades and units recognized from the file. You can correct available fields, exclude rows, cancel, or confirm adding the selected records. Unrecognized fields and scanned PDFs may require manual entry. A successful import is not confirmation that the source record or its interpretation is correct.

Once you confirm an import, the selected records become part of your working plan and can be saved to your account using the same plan-storage process as manually entered records. The automatic plan-save behavior also applies. Closing the preview before confirmation does not import the records. The page releases its active import state when closed, but cannot erase the original file from your device or promise secure erasure of browser memory.

Downloaded plan exports and draft backups can contain academic information. They are generated on your device and remain under your control after download. Protect them as you would any other academic record. Sending an export to someone else is your separate disclosure; account deletion cannot remove copies you downloaded or shared.

Personal API credentials and account controls

You choose whether to connect a supported personal API. The configuration can include a provider, encrypted key, model selections and usage preferences. Your key is sent to this website server when you save it and to the chosen provider as an authentication credential when a request uses it. It is not added to the model prompt. Other Planner accounts do not receive your key or configuration.

The website maintainer operates the server and its encryption configuration. Encryption reduces exposure from a stored record; it does not mean that the maintainer or running service is technically incapable of accessing a key when operating the authorized integration. We do not describe this storage as end-to-end encryption or as a separate secret vault controlled solely by you.

Replacing or removing a key changes the configuration stored by the Planner. It does not revoke that key at its provider, stop requests already accepted by the provider, erase provider logs or settle any provider charges. If a key may have been exposed, revoke or rotate it through the provider. Do not send passwords, API keys or verification codes in chat messages.

Automated planning and information you choose to provide

The planning tools use selected degree rules, the course catalog, prerequisite and offering evidence, stated interests, workload estimates and available instructor-review information to propose courses and semester arrangements. The application also applies rule checks to proposed changes. These are automated planning suggestions for you to inspect, not decisions by the university about admission, academic standing or graduation.

Career interests, Hub preferences, international-student status and writing placement are supplied by you. They help distinguish applicable academic rules and appropriate course choices. The Planner does not infer legal immigration status, access a placement-exam system or verify the information with BU. You may update your preferences and academic profile when they change.

A derived check or recommendation can still reveal information about your plan, even when raw grades and private notes are omitted from an automatically prepared AI context. Do not assume that a provider learns nothing about you simply because a raw field is excluded. You control whether to use personal chat and what to type in it.

Advertising, tracking signals and external resources

The Planner does not operate advertising, sell personal information, or share it for cross-context behavioral advertising. Its application does not currently add advertising pixels or third-party marketing analytics. Public font, logo, catalog and PDF-reader assets are served by the website rather than loading a marketing font tracker.

The application does not change its necessary account, security or storage processing in response to the browser Do Not Track signal. Because it does not sell or share information for cross-context behavioral advertising, there is no such advertising activity for it to opt you into. This statement is not a promise that every external service interprets browser privacy signals identically.

Cloudflare security verification and Google authentication may make requests to their own services when you use those functions. They can process technical information for their stated purposes under their policies. Following an external course, rating or provider link also exposes the request to that destination. Blocking third-party resources may prevent optional sign-in or verification from working.

How privacy requests are handled

Use the published support alias to identify the account, the information or action you request, and an appropriate way to respond. We may request reasonable proof of control of the account before disclosing, correcting or deleting private records. We will not ask you to send a password, API secret or university login credential by email.

The response and any available rights depend on the law applicable to you and the circumstances. Requests may be subject to identity verification, authorized-representative requirements, lawful exceptions and information we actually hold. We do not promise to retrieve information held only by BU or an independent API provider, or to provide a technical feature the service does not have.

If we cannot carry out a request in full, we will explain the relevant reason where required and provide any applicable review or appeal information. Making a good-faith privacy request is not grounds for punitive treatment. You may also contact a competent regulator where applicable. We do not use this policy to waive non-waivable rights or to claim certifications the website has not obtained.

Operational incidents and legal preservation

When investigating a security incident, malfunction or credible abuse report, we may use the relevant account identifiers, request metadata and records necessary to understand and address the event. We aim to limit access and disclosure to that purpose. Diagnostic details shown to a user should not expose another account’s data or secret credentials.

A material incident may require notifications, investigation or preservation of specific records under applicable law. The action depends on the facts and applicable requirements; this policy does not promise that every failed request constitutes a breach or that all affected information can always be restored.

Legal or security preservation may require retaining limited information after an ordinary deletion request. Any such exception must have a legitimate basis and does not authorize indefinite retention of the entire plan merely for convenience. The ordinary deletion process and its minimal anti-restoration marker are described in Your choices and privacy requests.

Account email and update requests

New accounts supply a bu.edu email address, including new accounts created through Google. For username registration, the service checks the email domain and records the address as unverified; it does not send an email verification message or prove university affiliation. Google-created accounts use the email returned by Google after token verification. Previously created accounts remain usable. The email appears in your own settings and is not published in a public profile.

You may set and change a nickname in Settings. It is stored separately from your sign-in identifier and Google account ID, appears within your private workspace, and is deleted with your account. Changing a nickname does not rename or merge accounts.

You may save an optional contact email in Settings. It is stored with your account, is not shared with other users, and does not change your sign-in identifier, grant access to your mailbox, or establish a verified identity. You may replace or clear it. The email supplied at registration remains part of the sign-in account record until account deletion.

An update request stores its type, semester or course reference, optional explanation, request identifier and submission time within your account. The site owner can view those requests to review course-data issues. The shared inbox index stores only account identifiers and recent request times; it does not hold your request text, contact email or API key. Requests are removed after 30 days by scheduled storage cleanup; deleting your account also deletes its request records and removes its inbox index entry. Do not include passwords, API keys, private university documents or unnecessary personal information in a request.

When you submit an update request, the website also submits an email notification through FormSubmit to the site owner’s published support forwarding address. The notification includes your Planner username and the request fields; a username may itself be an email if you chose that identifier. No separate account-email or contact-email field, private plan, password or API credentials is added. FormSubmit processes the notification under its privacy policy and service terms; the owner’s forwarding and mailbox providers handle the resulting email. If FormSubmit rate-limits the shared server, your browser may submit the same notification directly through its AJAX form endpoint. Your browser then reports the result to your account; the owner inbox distinguishes this source, which is not independent proof of delivery. This fallback sends the same request fields and username, without Planner session cookies or API credentials. Provider acceptance is not proof of inbox delivery. If delivery fails or awaits activation, the request remains available in the site inbox. Deleting your Planner account does not automatically erase emails already transmitted or copies kept by those email providers.

Submitting an update request does not automatically refresh the catalog. The owner reviews requests and decides whether to update public data. Submission is not a promise of a response time, correction or new semester availability.

To manage shared AI capacity and prevent abuse, we retain usage records linked to your account, including usage amounts, the model and feature used, and the date, for up to 31 days. Only the site owner can view these records; they do not contain conversation text or API keys. Account deletion removes identifiable usage records; unattributed totals may remain until expiry.

Contact and provider policies

The contact for this website’s privacy and data requests is terrier-plan-support.sprung163@slmail.me. Identify the relevant account and explain your request. Do not send passwords, API keys or verification codes.

You can also review the independent policies of Cloudflare, our email services SimpleLogin and Microsoft, Google, and the supported personal API providers: DeepSeek、OpenAI、Google Gemini、Groq、OpenRouter. These links are provided for transparency and do not incorporate a claim that this Planner has adopted every practice described by those companies.