Public beta information · September 2026
Privacy
How information supports the current Arbor beta.
Operator and contact
Arbor is currently operated by Jonathan Isidoro, operating Arbor. Jonathan handles privacy questions and requests through support@arbor.ph.
Information you provide
Account access uses your email and password through Supabase Auth. Your saved profile can include your name, country, currency, financial-readiness answers, goal, timeline, selected approach and preferences. Investment records include the products, providers, dates, units and actual PHP amounts you enter. Arbor also stores reference-value history, monthly check-ins and unfinished provider recordings used by its tools.
Missing-investment requests
When you request a missing investment, Arbor stores its name, provider, your account ID, the received date and two identifiers for receipts and retries. Jonathan reviews these requests through an owner-only Admin view. Arbor also stores the current review status and its updated date; submitted details stay unchanged. Other customers cannot read them. Please do not include account numbers or personal details. We aim to remove identifiable requests after 90 days through reviewed manual cleanup, so removal may occur later. Review status follows the request’s retention and is included in your data export. Reviewed account erasure can remove them earlier; any necessary hold is reviewed separately.
Ask Arbor feedback
Answer feedback is optional. Arbor stores only Helpful/Not helpful, an optional fixed-choice reason, topic, answer version, your internal account ID, a random feedback ID for edits and retries, and a server date. No question, answer, holdings, financial amounts or customer email is included in feedback. You can create up to 20 feedback records per UTC day; edits keep the original date. Only Jonathan’s verified owner Admin account can read votes, topics, dates, fixed reasons and totals by topic, without customer identity or portfolio access. Feedback is included in your account export and reviewed account erasure. Records become eligible for reviewed manual cleanup after 90 days; scoped support holds may delay removal. No automatic cleanup or exact deletion deadline is promised.
Optional usage sharing
After onboarding, you may choose Allow to share limited usage steps with PostHog through its US project. This measures named screens, help openings and progress through your first recorded investment during a pilot of up to 30 days. Events use a random analytics ID, event ID and timestamp, with fixed screen, stage or error categories. No name, email, investment details, answers, chat text, page URLs or client IP are added to event payloads. Arbor keeps the account-to-analytics-ID mapping privately for consent, access and privacy requests. Nothing before consent is added later. You can opt out in Settings → Account & privacy; this stops future collection and does not erase earlier events. On PostHog Free, event queries cover the previous year from capture; this does not guarantee physical deletion after one year. Local receipts have separate reviewed retention. Account export includes your consent and local receipts; provider-held copies require a separate request through support@arbor.ph. Provider erasure is separately reviewed and is not automatic.
How Arbor uses information
Arbor uses account information to restore your account and saved plan, calculate and display your recorded portfolio, plan contributions and explain your choices. Ask Arbor sends your question to the Arbor backend. Its current explanations use deterministic calculations and templates, with your saved plan and, where needed, recorded portfolio information; the current question-processing path does not call an external AI model. Do not include passwords, bank details or other sensitive information in a question.
Services supporting the beta
Supabase provides authentication and database services. Vercel hosts the frontend website and application; Render hosts the backend application services and workers. Resend supports product reminder email delivery; eligible unfinished recordings can prompt a generic reminder sent to your account email. Zoho Mail handles correspondence sent to support@arbor.ph. Provider websites you choose to visit have their own privacy practices. Arbor does not connect to your brokerage account or ask for its password.
Terms acceptance
An explicit Terms acceptance records the document version, content digest, server acceptance time and whether it occurred during signup or later in your account. Signing in or reading this Privacy Notice is not recorded as agreement. Signup uses a single-use, email-bound intent that expires after ten minutes; only its hash and an email hash are stored pending use. Expired intents are cleaned opportunistically, so expiration is not a guaranteed physical-deletion deadline. Acceptance records are included in account export and reviewed account erasure.
Browser storage
The application stores its sign-in session in browser storage through the authentication client, and remembers your appearance preference locally. These support account access and presentation. These public pages do not add analytics or advertising trackers.
Corrections, records and deletion
You can correct supported investment records in Arbor. Deleting an investment entry removes it from active calculations but retains an audit record; it does not delete your account or all associated data. There is currently no self-service whole-account deletion action. For access, correction, portability, objection or erasure questions, contact support@arbor.ph. Requests require assessment under applicable law and the account-data process; this page does not promise immediate or permanent erasure.
Privacy requests and retention
Jonathan receives privacy requests at support@arbor.ph, verifies the requester's identity using proportionate information, reviews the applicable rights and explains what can be provided, corrected or deleted. The current investment ledger prevents deleting an account with ledger history, so complete erasure is not promised. Audit records are not exempt from deletion review or retained indefinitely without a justified reason. Account and plan information is kept while needed to provide the service, with retention assessed when closure is requested. Any continued hold must have a specific justified purpose. Arbor has adopted future targets of 30 days after resolution for reminder-delivery metadata and six months after resolution for ordinary support correspondence. These targets are not currently implemented automatic purges or fixed deletion promises. Privacy-request records are assessed separately and limited to what is needed for accountability.
Provider locations, logs and backups
The configured primary Supabase project region is ap-northeast-1 (Japan), and the Render application services are configured in Singapore. These settings do not establish where every provider processes or stores information. Resend’s published policy places stored email data in the United States; a sending region does not establish its storage location. Provider log windows depend on the service and plan. Actual backup settings, international-transfer arrangements, support-mail archives and operator-created exports have not all been verified. Removing active account data does not establish that every provider or exported copy has been erased. These copies require separate assessment and follow-up; no universal storage location or fixed backup-erasure deadline is promised.
About this notice
This notice explains the current beta and its known limitations. It is not a request for blanket consent or a claim of legal certification. Questions about processing grounds, provider handling or your applicable privacy rights can be sent to support@arbor.ph. No security certification, data-sale policy or AI-training exclusion is claimed here.
Questions? support@arbor.ph