Privacy Policy · Philippines-facing site

Table Plus Privacy Policy

This Privacy Policy explains how information may be handled when users access or interact with Table Plus and related website features. It is written for quick reading on mobile and desktop, so users can check what may be collected, why it may be used, and where privacy questions can be raised.

Website use
Account support
Technical help
User privacy
Cookies
Retention
Information

What may be collected

Depending on the service used, Table Plus may process personal, technical, account, communication, or transaction-related information.

Usage

Why it may be used

Information may be used for account handling, support, service delivery, security checks, and website maintenance where applicable.

Cookies

How cookies may help

Cookies may support login sessions, preferences, navigation, and basic site performance depending on the website configuration.

Choices

What users can do

Users may review the policy, manage browser settings where supported, and use the Contact page for privacy questions.

About this Privacy Policy

This page is here to explain privacy practices in a direct format. It is not a sales page, and it is not written to push users toward a specific action. If you are checking a privacy issue, a support question, or a data-related concern, this page points you to the relevant parts without burying the details.

For users in the Philippines, privacy concerns often come up around registration, login access, device changes, cookie prompts, and contact requests. That is why the language stays practical. If a feature is being used, the website may need limited information to keep that feature working.

Privacy note.

Users should review the current policy information on the website before sharing details through any support channel. If a request looks unusual, it is safer to pause and check the page again first.

A useful privacy habit is simple: share only what is needed for the task at hand.

Information We May Collect

Depending on the service or feature being used, Table Plus may process different categories of information. Not every category applies to every visitor. The point is simple: the site may need enough information to keep an account working, answer a request, or maintain basic technical functions.

Account Information

Where an account feature is available, the website may process information needed to create, access, manage, or maintain that account.

Contact Information

If users send a message or ask for help, the website may process the details shared in that communication so the request can be reviewed.

Technical Information

Depending on technical configuration, information such as browser type, device type, operating system, IP address, language settings, or logs may be involved.

Transaction Information

Where payment-related features are available, transaction-related information may be processed as necessary to support the requested transaction or recordkeeping.

Usage Information

The website may review how pages are opened, how features are used, and what content is accessed so the service can be maintained and improved.

Cookie Information

Cookies and similar tools may be used to support sessions, preferences, and basic navigation where applicable.

How Information May Be Used

Information may be used for relevant purposes tied to the service itself. That usually means keeping the website usable, handling account-related requests, and making sure support messages reach the right place. It may also help with security checks, technical maintenance, and policy enforcement where needed.

1

Service delivery

Some information may be needed to provide the requested feature, page, or account function.

2

Support handling

Messages, questions, and follow-up details may be used to understand what the user is asking.

3

Security checks

Technical and account signals may help spot unusual access, misuse, or other issues that need review.

4

Site improvement

Usage patterns may help the website understand what works well and what needs a cleaner path.

Information type Possible purpose Practical note
Account information Manage access and maintain account records Useful when a user needs to sign in, update details, or review an account issue.
Technical information Keep the site working and troubleshoot errors May help identify device or browser problems that affect page loading.
Communication information Respond to questions and support requests Used only for the message or follow-up linked to that request.
Transaction information Support payment-related processing where available Handled only when the feature is used and only as needed.

Cookies & Technical Information

Cookies are small data files that may help a website remember a session, a preference, or a basic setting. On a practical level, they can make it easier to move between pages without repeating the same action every time.

Cookie usage may depend on the website configuration. If cookies are enabled on the site, they may support login sessions, navigation, and basic performance checks. If a browser setting blocks certain cookies, some features may behave differently.

Browser tip.

Users who prefer tighter control can review browser privacy settings, clear stored cookies, or limit certain tracking functions where the device allows it.

A small detail can matter: after clearing cookies, a saved session or preference may no longer appear the same way.

Account & Transaction Information

When an account feature is available, certain information may be needed to create access, maintain records, or manage the user’s request. The exact fields depend on the service being used, so the page does not assume every visitor will be asked for the same details.

Where payment functionality is available, transaction-related information may be processed as necessary to support the requested transaction. That can include the information needed to complete, verify, or record the activity. No extra detail is added unless the service specifically requires it.

Helpful privacy practice

  • Use accurate account details where the service asks for them.
  • Do not send passwords, OTPs, PINs, or other sensitive credentials through unofficial channels.
  • Check that the request is coming from the correct page before sharing anything important.
  • If a transaction looks unfamiliar, review it before sending follow-up details.

Information Sharing

Information may be disclosed to relevant service providers or other parties where necessary for the operation of applicable services, where required by law, or where otherwise permitted. This can include technical support, service delivery, or related operational needs.

If third-party services are used, the website may rely on them for specific functions. The exact providers are not listed here unless they are confirmed in the current site information. Users should review the live policy details if they want the most current picture.

Data handling note

From a privacy perspective, the important question is not whether data is shared in every case. It is whether the sharing is tied to a real service need and handled in a way that matches the feature being used.

That is why this page keeps the wording narrow. It avoids guessing, and it avoids naming providers that are not verified.

Data Security

Reasonable measures may be used to help protect information from unauthorized access, misuse, or loss. Security practices can vary depending on the feature, the device, and the technical setup in use. For that reason, users should treat privacy and account safety as shared responsibilities.

One useful habit is to keep login details private and avoid passing them around in chat threads, social posts, or unofficial messages. If a request for sensitive information feels unusual, it is worth checking the page again before responding.

Privacy perspective

Only share details that are needed for the current task. Extra information is not always useful.

Security awareness

If a device is shared, remember to sign out after use and review browser storage where appropriate.

Unusual requests

Pause before sending sensitive data if the request does not match the normal support path on the site.

Data Retention

Information may be retained for as long as reasonably necessary for the relevant purpose, subject to applicable requirements and operational needs. That means the length of time can vary depending on the type of information, the feature involved, and whether the record still has a practical use.

Some records may need to stay available for account handling, support follow-up, technical review, or recordkeeping. Once they are no longer needed for those purposes, they may be removed or handled according to the website’s current process.

What this means in practice

  • Account records may stay available while the account remains active or under review.
  • Support messages may be kept long enough to complete the request.
  • Technical logs may be used for troubleshooting or security review.
  • Some records may remain where a legal or operational need still applies.

User Privacy Choices

Users may review the policy, ask privacy-related questions, and manage some browser settings where supported. If a feature depends on cookies or stored preferences, changing browser settings may affect how that feature behaves.

Where applicable, users may also review account information or ask for clarification about how a request is handled. The most practical step is often the simplest one: check the current policy information, then use the Contact page if something needs a closer look.

Review information

Check the policy whenever a feature, setting, or account flow feels different from what you expected.

Manage browser settings

Where supported, browser controls can help limit cookies or clear stored site data.

Raise a question

If something is unclear, use the Contact page rather than guessing how the site handles it.

Privacy Policy Updates

This policy may be updated when practices, services, or requirements change. Users should review the current page from time to time, especially before sharing new information or using a feature that has changed.

Policy updates may be reflected on this page when applicable. No extra promise is made about notice methods unless the live website states one clearly.

User control note.

A good privacy routine is to check the policy again after a major site change, a new device login, or a support request that involves account details.

Small updates can change how a feature handles data, even when the page looks familiar.

Privacy FAQ

These questions cover the practical parts users usually want to know first: what may be collected, why it may be used, and how to ask about it without turning the process into a long back-and-forth.

1. What information may Table Plus collect?
Depending on the service or feature being used, Table Plus may process personal, technical, account, communication, or transaction-related information. Not every category applies to every visitor.
2. Why may account information be used?
Account information may be used to create access, manage the account, maintain records, and support the service the user asked for. If no account feature is being used, that category may not be relevant.
3. Does the website use cookies?
Cookies may be used where applicable to support login sessions, preferences, navigation, and basic site performance. Cookie behavior can depend on the website configuration and the user’s browser settings.
4. What technical information may be collected?
Depending on technical configuration, information such as browser type, device type, operating system, IP address, language settings, or logs may be involved. These details can help the website stay usable and troubleshoot issues.
5. How may transaction information be handled?
Where payment-related features are available, transaction-related information may be processed as necessary to support the requested transaction or related recordkeeping. The exact details depend on the service being used.
6. Can users ask about their personal information?
Yes. Users may use the Contact page to raise privacy-related questions or ask for clarification about how information is handled. That is the cleanest route when something needs a human review.
7. How is information protected?
Reasonable measures may be used to help protect information from unauthorized access, misuse, or loss. Users can help too by protecting passwords, avoiding unofficial channels, and checking requests before sharing sensitive details.
8. How long may information be retained?
Information may be retained for as long as reasonably necessary for the relevant purpose, subject to applicable requirements and operational needs. The exact length of time can vary by record type and service use.
9. Can the Privacy Policy change?
Yes. This policy may be updated when practices, services, or requirements change. Users should review the current version from time to time so they know how the site is handling information.
10. Where can privacy questions be directed?
For privacy-related questions, users may refer to the website’s Contact page. That is the best place to start when a request needs clarification or when a user wants to check how a specific feature handles data.

Have a Privacy Question?

Review the policy information above and use the Contact page if you need to raise a privacy-related question or check a detail tied to your use of the site.