Privacy Policy

Who operates UpNext

UpNext is independently operated by Earl Isaac Cordova-Buyco, based in Bacolod City, Negros Occidental, Philippines. For privacy questions, rights requests, or formal correspondence, contact support@upnextcreator.com.

Our privacy commitment

UpNext follows the transparency, legitimate-purpose, and proportionality principles of the Philippine Data Privacy Act of 2012 (Republic Act No. 10173). We collect only data reasonably needed to provide, secure, and improve the features you choose to use.

What UpNext processes

UpNext does not define its collection as all activity. Each category below has a specific product, security, or legal purpose:

• Account and access data: email, display name, one-way password hash, one-way email-verification, password-reset, and recovery-code hashes, consent records, and protected session identifiers, used to create, authenticate, recover, and separate creator workspaces.
• Creator workspace data: only the ideas, plans, analytics, private opportunity records, rates, deadlines, templates, settings, media-kit details, and other fields you choose to enter, used to provide the features you request.
• Connected-platform data: the provider account identifier, account name and image, encrypted authorization token, granted scopes, available metrics, and sync status, used only to connect and refresh the account you authorize.
• Login-abuse records: a one-way hash derived from the attempted email, network address, and action, plus attempt counts and timestamps, used only to rate-limit repeated sign-in or signup attempts.
• Error references and essential request information: a short error reference and the minimum technical request data processed by the hosting infrastructure, used to deliver the site, prevent abuse, and diagnose a specific failure.

What UpNext does not log

UpNext does not keep its own page-view history, clickstream, advertising identifier, cross-site browsing history, keystroke log, or a general record of everything you do. Product records change only when you create, edit, connect, sync, export, disconnect, or delete something, and technical security records are limited to the stated purposes above.

Cookies, device storage, and hosting analytics

UpNext uses an essential, secure session cookie to keep you signed in. A light-or-dark theme preference may be stored only on your device. UpNext does not set advertising cookies or use its own cross-site tracking. The hosting platform may process basic traffic, security, and reliability information to deliver and protect the service, including aggregated site-traffic analytics available to the operator.

Why it is processed and the legal bases used

Account and workspace data is processed because it is necessary to provide the service you request under the Terms of Use. Optional social connection data is processed with your authorization and can be withdrawn by disconnecting it. Limited security and abuse-prevention data is processed to protect creators and the service, subject to your rights and the proportionality requirements of applicable law. Some records may also be processed when necessary to comply with a legal obligation or establish, exercise, or defend a legal claim.

No selling, ad profiling, or brand access

UpNext does not sell, rent, trade, or broker personal data. It does not build advertising profiles, run targeted advertising, or give brands access to private creator records. Data is disclosed only to infrastructure providers that help operate the service, to a social platform you deliberately connect, when you intentionally create and share a media-kit link, or when disclosure is legally required.

No automated decisions about creators

UpNext does not use personal data to make eligibility, employment, credit, pricing, ranking, matching, or other decisions that legally or similarly affect a creator. Workflow priorities and calculated metrics organize records you control; they do not decide whether you receive a collaboration, payment, verification, or platform access.

Social connections and public media kits

Official social connections are read-only and never require you to give UpNext a social-media password. Provider access and refresh tokens are encrypted before storage, are never included in exports, and are used only for the connection you authorize. Disconnecting stops future syncing and removes the connection authorization used by UpNext; analytics already imported remain part of your private workspace under the retention schedule below until you delete them or your account. A media kit becomes accessible to anyone with its URL only when you save a public slug. UpNext does not list, recommend, distribute, or send that link to brands. You decide whether to share it, but recipients may forward it, so publish only fields you are comfortable making public.

Connected-platform data

When you choose to connect a provider, UpNext requests only the read-only permissions required for features currently shown in UpNext: Instagram professional profile, media, and available insights; Facebook Pages you select, Page content metadata, and available Page insights; TikTok basic profile, follower statistics, and public-video data; and YouTube channel information and read-only channel analytics. If a metric is unavailable through an approved permission, UpNext shows it as unavailable or offers manual entry; it does not request adjacent data just in case. UpNext does not request permission to publish, send messages, manage comments, run ads, or control your account.

Google API data and Limited Use

UpNext's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used only to provide or improve the user-facing YouTube analytics connection you request, is not used for advertising, and is not transferred except as needed to provide the feature, for security, to comply with law, or with your affirmative consent.

Retention and deletion

UpNext applies the following retention periods to records it controls. You can shorten any creator-record period by deleting the record, disconnecting the account, or deleting your UpNext account, as applicable.

• Account, profile, content, deal, template, media-kit, manual analytics, and content-level analytics records: retained while your account remains active or until you delete the record, then removed from the active database when you delete the account.
• Synced account-level analytics: UpNext keeps at most one detailed snapshot per connected platform and day for 90 days. After 90 days, it retains the latest synced snapshot for each platform and calendar month while the account remains active. Manual and content-level analytics are not compacted by this schedule.
• Connected-account authorization tokens and connection metadata: retained until you disconnect that platform, delete the account, or the authorization expires and cannot be refreshed, whichever comes first.
• Signed social-authorization state: valid for 10 minutes and not stored as a continuing activity log.
• UpNext login sessions: expire 30 days after creation, after 7 days without use, or sooner when you sign out, change access, or delete the account.
• Unconfirmed account registrations: retained for up to 7 days so you can request another confirmation email, then removed by routine maintenance if the email is never confirmed.
• Email-confirmation tokens: only a one-way token hash is stored. The token expires after 24 hours and is removed when used, replaced, or cleared by the next routine maintenance run.
• Email password-reset tokens: only a one-way token hash is stored. The token expires after 30 minutes and is removed when used, replaced, or cleared by the next routine maintenance run.
• Password recovery codes: only one-way code hashes are retained until a code is successfully used, you generate a replacement set, or you delete the account. Plain recovery codes are displayed in a protected browser session for no more than 5 minutes and are not stored in the active database.
• Login-abuse and rate-limit records: retained for 30 days after the latest recorded attempt, then deleted during routine authentication maintenance.
• Application-generated error references: kept only as long as needed to diagnose the reported failure and no longer than 30 days where UpNext controls the log.
• Active-database deletions take effect immediately in the application. Recoverable infrastructure backups, if created by the hosting provider, are isolated from normal use and allowed to roll off for no more than 30 days unless a longer period is required by law or needed for a documented legal claim.

Security

UpNext uses one-way password and recovery-code hashing, a server-held password pepper, verified-email activation, single-use and short-lived recovery links, optional single-use recovery codes, protected and expiring sessions, sign-in and recovery rate limits, server-side record ownership checks, encrypted connections, application-level encryption for social authorization tokens, platform-provided storage protection, signed and time-limited authorization state, restricted browser permissions, input and request limits, anti-framing controls, non-public creator routes, and non-revealing server errors. No internet service can promise zero risk, so security controls are reviewed as the service changes.

Security incidents and breach response

UpNext maintains a documented process to contain, investigate, record, and correct suspected security incidents. When a personal data breach meets a legal notification threshold, UpNext will notify the National Privacy Commission and affected people within the period required by applicable law, using the information reasonably available at the time. Not every technical error or blocked attack is a reportable personal data breach.

Your rights and choices

Subject to the Data Privacy Act and its implementing rules, you may ask to be informed, access or correct your data, object to or withdraw consent from processing, request erasure or blocking, obtain portable data where applicable, and file a complaint with the National Privacy Commission. You may also seek damages where the law provides. People in other jurisdictions may have additional mandatory rights, which UpNext will honor where those laws apply. Open Settings → Privacy & Data to view, download, correct, disconnect, or delete data, or contact support@upnextcreator.com for a privacy request.

Service providers and international processing

UpNext uses OpenAI Sites and its infrastructure providers to host the application and database; Resend to deliver confirmation and password-reset email; and Meta, TikTok, or Google only when you choose to connect the corresponding platform. Each provider receives only the categories needed for that function. These providers may process data in the Philippines or other countries. UpNext remains accountable for the personal data it controls and uses provider terms, access limits, encryption, and other reasonable safeguards intended to maintain comparable protection during processing.

Privacy governance, geographic scope, and changes

Earl Isaac Cordova-Buyco is the operator and accountable privacy contact for this independently run service. UpNext is operated from the Philippines and does not claim a privacy certification, regulatory seal, or universal compliance status. The service is not intended for children under 18. Material changes to this notice will be shown by a new effective date and, when appropriate, an in-product notice.