TrendyBuilders logoTrendyBuilders
Open workspace ↗

Privacy Notice.

Proposed notice for public customers · effective date pending approval.

1. Who is responsible for your information

OLAN DEEMS, sole proprietor trading as ODBEST Management Consultancy Services and operating TrendyBuilders, DTI Business Name registration no. 6906278, established in the Philippines, with a business postal address at 10B08 Victoria de Manila Tower, 1655 Taft Avenue, Malate, Manila, Philippines 1004, is responsible for deciding how information is used to operate this service. Contact Legal@TrendyBuilders.com for privacy questions or requests and Support@TrendyBuilders.com for account help. OLAN DEEMS, proprietor and privacy contact, personally monitors Legal@TrendyBuilders.com for privacy and deletion requests. [ANY ADDITIONAL LEGALLY REQUIRED PRIVACY OFFICER OR LOCAL REPRESENTATIVE DETAILS] remain subject to the applicable-law assessment. This contact designation does not by itself appoint a statutory data protection officer. The intended service is worldwide; applicable local rights remain protected. The Terms select Philippine law without removing mandatory customer rights elsewhere. The Philippine Data Privacy Act of 2012 (Republic Act No. 10173) and other applicable privacy laws must be addressed in the final notice and operating procedures. The proprietor name OLAN DEEMS, sole-proprietorship status, business registration details and address were supplied by the owner. Check the proprietor particulars against the official DTI registration before activating these drafts; no independent registration or legal-name verification is represented.

2. Information we receive

We receive information from you, your chosen sign-in provider, service operation and people who report or reply to content. We do not need your social-provider password. Avoid sending sensitive personal information or third-party confidential data that is unnecessary for the request.

3. Why we use it

We use account and project information to provide the functions you request, verify access, save and retrieve your work, handle support, and administer your account. We use relevant security and moderation information to prevent misuse, investigate incidents, maintain reliability, and protect rights. We may retain a limited record when a specific legal obligation or claim requires it.

Where a law requires a legal basis, the proposed bases are performance of the service agreement for requested account/project functions, our legitimate interests in proportionate security and service administration, compliance with applicable legal obligations, and consent for uses that genuinely require it. Confirm the applicable bases for the operator and launch countries before this draft becomes effective. Optional login is a customer choice; acknowledging this notice is not consent to unrelated processing. Versioned Terms acceptance records document the agreement displayed during registration or authenticated confirmation; they are kept with the account and follow its deletion and documented legal-hold rules. Email-registration attempts remain marked unverified until the matching email verification succeeds. Historical acceptance dates are not fabricated. Short-lived Google acceptance intents expire after ten minutes and are removed by the existing authentication-record cleanup.

The current release does not include advertising trackers, a marketing-signup workflow or paid checkout. The owner intends to offer both Free and paid subscriptions using the established plan features, prices and monthly/annual offers. PayPal and PayMongo are the selected payment providers. Before payment collection is enabled, confirm their actual billing/contact/tax data flows and transaction identifiers received by the operator, specify who handles card details, and set applicable retention periods. Future gateways require assessment and updated disclosures before use. The owner has approved automatic monthly/annual renewals, advance annual-renewal reminders, cancellation with access through the paid period, a seven-day failed-renewal grace period with email reminders, and advance notice of price changes for a future renewal. Billing contact details, payment status and transaction references may be needed to administer these functions once enabled; the exact fields, providers and retention must be verified before collection. The owner has approved the voluntary first-purchase and accidental-renewal refund windows set out in the proposed Terms. Refund requests may require the account email, payment reference, request timestamp and, for renewal eligibility, relevant paid-feature usage records. Confirm the minimal actual records and retention before paid launch; no new refund-use tracking is represented as deployed by this draft. Tax treatment and statutory billing-record retention remain flagged pending confirmation with the owner’s accountant. These payment data flows are not yet confirmed or deployed. A new purpose, payment service, marketing integration or project-data AI processing feature will require an updated assessment and appropriate notice or consent before introduction. Construction calculations do not determine your eligibility for employment, lending, housing or similar services.

4. Who can see your information

Your customer account remains separate from administrator accounts. Project and ticket APIs check the signed-in owner; authorized staff can access support records for service administration. Staff and service providers should receive only access needed for their work. Linking Google or ChatGPT to a customer account requires proof of access and does not grant administrator permissions.

Display names and community contributions are visible to anyone who can access the community; this may include the public after launch. Account email addresses and private ticket attachments are not published as part of a community post. We may disclose necessary information to comply with a valid legal requirement or protect rights and safety, with safeguards appropriate to the request.

5. Providers, email and international processing

The service currently uses OpenAI Sites for hosting/platform operation, Cloudflare-backed database and file storage, Resend for transactional email, Google for optional login and the support mailbox, and OpenAI for optional ChatGPT login. These services process relevant identifiers, messages or operational information for their respective roles. A login provider also operates its own account under its own privacy policy.

Resend processes email recipients, message content and delivery metadata. Support notifications can contain your submitted name, email and message; attachments stay in protected site storage rather than being attached to these notifications. Email copies delivered to support or your mailbox have a separate lifecycle from the application ticket.

Information may be processed outside your country, including the United States. Resend states that its stored email data is in the United States even when a different sending region is selected. [CONFIRM ACTUAL HOSTING/STORAGE/BACKUP COUNTRIES, PROVIDER CONTRACTS AND THE APPLICABLE TRANSFER SAFEGUARDS FOR EACH LAUNCH MARKET]. We do not claim that selecting a Tokyo sending region makes all data resident in Japan or establishes compliance with another country’s transfer rules.

6. Cookies and your browser

Secure sign-in cookies keep you authenticated and remember the selected Administrator/Customer mode. Google sign-in also uses short-lived state and verification cookies. Login and account-mode cookies are currently set for up to seven days; sign-in challenge cookies for up to ten minutes. The site uses browser local storage for user-specific project drafts and display preferences. These functions are used to provide the requested service; third-party login providers may use their own cookies during sign-in.

Logging out does not necessarily erase local drafts, downloaded backups or files you exported. On a shared device, export what you need and clear the site’s browser data after use. Blocking required storage can prevent sign-in or draft restoration. No optional analytics/advertising cookie system is part of the current application; assess consent requirements before adding one.

7. Approved retention periods and deletion workflow

The owner has approved the application retention periods below. Customer deletion is request-driven and email-confirmed; verified accounts are not deleted for inactivity, logout, cancellation or limits. Application cleanup is implemented as bounded maintenance batches. External mailbox/provider copies and backup configuration still require documented follow-up; approval of a target is not proof of those settings. Retention should follow the purpose and any applicable legal requirement, rather than a universal period for all records. Expiry of access is different from deletion of stored data.

Approved application periods and remaining provider/operational checks
InformationPeriod / ruleOwner implementation check
Privacy requests and erasure follow-upKeep a minimal request/audit record for 24 months after completion. During confirmed deletion, prior request content is scrubbed; the contact email is removed once external follow-up is recorded as complete.Requests with unresolved external follow-up or a documented hold remain visible for resolution. The separate pseudonymous R2 erasure registry supports reapplying deletions after database-only restoration.
Verified account and linked login identitiesWhile the account is open; remove or irreversibly deidentify within 30 days after a verified closure/deletion request is accepted, unless a specific legal exception applies.Email-confirmed deletion queues a customer-only erasure job and immediately revokes customer sessions. A separate staff-only dashboard tracks legal holds, retries and external-copy follow-up. No verified-account inactivity deletion is implemented.
Unverified registrationsDelete 30 days after registration if still unverified.Maintenance removes unverified unfinished signups after 30 days, using the latest registration attempt where recorded. Email-link expiry alone is not account deletion.
Projects, saved versions, libraries and uploaded project evidenceWhile you keep them; remove active copies and associated history/files within 30 days of deletion or account closure.Customer account erasure removes owned records, histories, libraries and personal/company file prefixes. Orphaned personal-project evidence is also cleaned up. Exports and independently held copies remain outside the app’s control.
Contact requests and support tickets, including replies24 months after the last substantive support interaction, or sooner when a valid erasure request requires it.Apply this to application records and staff-mailbox copies. Retain only a documented minimum for a live dispute or legal obligation.
Support attachments90 days after ticket closure; earlier for a valid deletion request when no exception applies.Maintenance removes the stored file after 90 days closed; a later substantive interaction resets the closed-record clock. The retained ticket can remain without an attachment.
Community posts and repliesUntil removed under the community rules or a valid deletion request. On account closure, assess removal or deidentification within 30 days.Other people’s replies and lawful independent copies may remain; do not promise to erase the wider internet. Add the request-handling process before launch.
Moderation reports and decision records12 months after the report is resolved, unless needed for an active abuse investigation or legal claim.Staff can record report resolution. Maintenance purges resolved reports after 12 months; unresolved reports are retained for review. Hiding a post alone does not start the resolved-report clock.
Application security/rate-limit records30 days after the recorded event or latest rate-limit activity; documented incident evidence may be kept through an active investigation.Confirm fields, logging settings and deletion mechanism. Provider operational logs have their own separately confirmed schedules.
Session and verification/recovery recordsLogin access expires after 7 days, verification after 24 hours, password recovery after 30 minutes, and Google sign-in challenges after 10 minutes. Proposed stored-record purge: within 24 hours after expiry or revocation.Daily maintenance removes already-expired stored session/token records at the next run, targeting cleanup within 24 hours of expiry; single-use tokens are consumed when used. Deletion confirmations expire after 30 minutes, and accepted account deletion revokes sessions immediately.
Browser drafts and preferencesUntil overwritten, removed by you, or cleared from browser site data; no guaranteed browser-storage expiry.Drafts are separated by user identifier. Logging out or deleting a server project does not necessarily clear a local draft or an exported file.
Resend email content and delivery logsResend publishes a 30-day email/log period for standard plans; confirm the account’s plan and exceptions. Its published backup period is 7 days.Support mailbox copies are separate. Record verified provider settings and any exception before publishing the final notice.
Backups and disaster-recovery copiesProposed maximum: 90 days after deletion from active systems, with restricted recovery-only use.This is a target, not a verified current guarantee. Confirm every managed backup/export schedule; D1 publishes 7-day Free / 30-day Paid point-in-time recovery. Reapply valid deletions after a restore.
Future billing/tax recordsFree and paid subscriptions are intended; checkout is currently disabled. Set a jurisdiction-specific statutory schedule before collecting billing records.Do not invent a universal tax or accounting period. Keep only the fields required by the relevant obligation.

A legal hold should cover only information needed for a documented obligation, dispute or investigation. Record the basis, responsible person and review date; remove the retained copy when the exception ends. Restricted backups are for recovery, not ordinary account access. If a backup is restored, valid deletions must be reapplied. Recipient-held email copies, exported files and independent copies made by others cannot always be removed by us.

8. Your choices and requests

Depending on the law that applies, you may request confirmation/access, correction, deletion, restriction, portability, objection, or withdrawal of consent for processing that relies on consent. Withdrawal does not undo prior lawful processing. You may also complain to the relevant data-protection or consumer authority, including the Philippine National Privacy Commission where applicable. Mandatory rights and shorter legal response deadlines are preserved.

Send requests to Legal@TrendyBuilders.com from your registered email where practical, explaining what you need. We may ask for proportionate proof of identity or authority before releasing private data or making an irreversible change; do not send a password or unnecessary identity documents. We will respond within the applicable legal deadline and explain a lawful refusal or permitted extension. The owner is the designated mailbox monitor; an identity-verification, escalation and request-tracking procedure must still be completed before this notice takes effect.

Project export and project-record deletion are available in the workspace. The Privacy & account control page lets signed-in customers request access/export, correction, restriction/objection, consent withdrawal and account deletion. A deletion request requires an expiring registered-email confirmation and an explicit DELETE confirmation. Customer sign-in is then disabled and a customer-only erasure job is queued. Staff track other requests, record proportionate verification, apply documented legal holds where necessary and review external-copy tasks. Native administrator identities are excluded from customer-account erasure. We will explain what can be removed, what must temporarily be retained and why, subject to applicable law.

9. Security and adult-only registration

Current controls include hashed passwords, expiring single-use verification/recovery tokens, secure account cookies, ownership checks and restricted staff functions. No system is risk-free; contact support promptly about suspected unauthorized access. Any legally required incident notification will be handled according to applicable law.

The owner has approved adult-only registration for the initial public launch. Registered customers must be at least 18 and have reached the age of majority where they live. Minors may not register, subscribe or participate through an account during this launch, including with parental permission. This is an account-registration rule; it does not establish that children cannot visit a public page or send information through a contact form. Login providers also impose their own requirements.

Current registration control: email, Google and optional ChatGPT signup require an explicit adult self-declaration checked by the server. We store its timestamp and policy version with the account for eligibility administration, while the account remains open and subject to the account-deletion rules above. Existing customer accounts without a declaration must authenticate and confirm it before customer access resumes; earlier customer sessions do not bypass this requirement. We do not collect a date of birth or identity document for this control or infer age from Google or ChatGPT sign-in. Self-declaration cannot establish actual age. Operational review of existing test accounts and suspected-underage procedures remain public-launch requirements. Assess and disclose any additional age-assurance data before collecting it, and avoid unnecessary identity documents. If we learn that a child may have supplied information, assess the circumstances, restrict inappropriate processing and address deletion or any necessary lawful retention under applicable law. Parents or guardians can contact Legal@TrendyBuilders.com; verify their authority proportionately.

Registration for minors is deferred. Any future introduction requires a separate assessment of child-friendly notices, applicable parental notice/verifiable consent, guardian rights, data minimization and retention, and safer community participation before launch. An adult-only statement by itself does not remove applicable duties concerning children.

10. Changes to this notice

The approved notice will show an effective date. We will provide appropriate notice of material changes and seek consent when required for a new purpose. This draft is not a certification of compliance with every jurisdiction and does not replace the current early-access notice until adopted.

Owner decisions and release gates

Application retention jobs, customer account/file deletion, privacy-request tracking, legal holds, report resolution and an erasure registry are implemented and tested separately. Before this becomes effective, verify provider/mailbox/backup settings, test the operational restore process, complete other launch decisions and ensure all remaining promises match actual service operation.

Review sources

Primary guidance and provider documentation checked on 13 November 2026. Jurisdiction examples are reference material, not a determination of which law applies to TrendyBuilders.

Review the proposed Terms of Use →