A Legal Article in the Philippine Context
I. Introduction
A technology business that owns a brand, mobile application, website, software platform, customer database, content, trademarks, source code, and revenue-generating operations should be structured carefully from the beginning. In the Philippines, many founders start informally as sole proprietors or small partnerships, then later discover that the brand is not protected, the app code is not clearly owned by the company, the business name is not the same as a trademark, investors want a cleaner corporate structure, or personal assets are exposed to business risks.
One common solution is to form a holding company or a corporate group structure. A holding company is a company created mainly to own shares, intellectual property, brand assets, subsidiaries, investments, and strategic rights. It may operate directly, or it may own an operating company that runs the app business.
For a brand and app business, the corporate structure should answer several legal questions:
- Who owns the brand?
- Who owns the app, source code, UI/UX designs, content, and database?
- Who contracts with users, vendors, developers, advertisers, and payment providers?
- Who receives revenue?
- Who bears operational liability?
- Who employs staff?
- Who owns the trademarks and domain names?
- Who can raise investment?
- Who can license the brand or app to affiliates?
- How are founders protected from personal liability?
- How are investors protected?
- How can the business be sold, franchised, licensed, or expanded?
A holding company structure can be very useful, but it must be done properly. Simply forming a corporation and calling it a “holding company” is not enough. The business must also address intellectual property ownership, contracts, data privacy, tax, corporate governance, foreign ownership restrictions, labor compliance, app store agreements, payment rules, cybersecurity, licensing, consumer protection, and future investment or exit planning.
II. What Is a Holding Company?
A holding company is a corporation whose main purpose is to hold assets or investments rather than directly conduct day-to-day business operations.
In the app and brand context, a holding company may hold:
- shares in operating subsidiaries;
- trademarks;
- copyright;
- software rights;
- domain names;
- brand assets;
- patents or utility models, if any;
- trade secrets;
- database rights and contractual rights;
- licenses;
- investment assets;
- equity in affiliates;
- franchise or licensing rights.
The holding company may be called the parent company, while the business that deals with customers may be called the operating company.
Example:
- ABC Holdings Corporation owns the brand, app intellectual property, and 100% of shares in ABC App Corporation.
- ABC App Corporation operates the platform, hires employees, signs user terms, receives payments, and handles customer service.
- The holding company licenses the brand and app technology to the operating company.
This structure separates ownership of core assets from operating risk.
III. Why Use a Holding Company for a Brand and App Business?
A holding company can serve several purposes.
A. Asset Protection
The most important assets of an app business are often intangible:
- brand name;
- trademark;
- source code;
- user interface;
- algorithms;
- database;
- domain names;
- social media accounts;
- business model;
- content library;
- goodwill;
- user relationships.
If these are owned by the operating company, they may be exposed to operational liabilities such as consumer claims, vendor disputes, employee claims, tax assessments, cybersecurity incidents, data privacy complaints, app store disputes, or debt collection.
If the holding company owns the assets and licenses them to the operating company, the core assets may be better insulated from day-to-day operational risks.
B. Investor Readiness
Investors prefer clean ownership. Before investing, they usually ask:
- Is the corporation properly incorporated?
- Are founders’ shares properly issued?
- Is the cap table clean?
- Does the company own the IP?
- Did developers assign rights?
- Are trademarks filed?
- Are there unpaid taxes?
- Are data privacy documents in place?
- Are there founder disputes?
- Is there a shareholders’ agreement?
- Are employee stock options authorized?
- Are material contracts assignable?
A holding structure can make fundraising easier if properly documented.
C. Brand Licensing
A holding company can license the brand to different operating entities.
Example:
- one operating company for the Philippine app;
- another for regional expansion;
- another for merchandising;
- another for franchising;
- another for enterprise software licensing.
The holding company keeps central control over the brand.
D. Risk Segregation
Different business lines can be separated.
Example:
- app operations;
- e-commerce;
- logistics;
- advertising;
- financial technology;
- content production;
- software licensing;
- foreign expansion.
Each operating subsidiary can bear its own risks while the holding company owns the strategic assets.
E. Tax and Accounting Planning
A holding company may help organize dividends, intercompany service fees, royalties, cost-sharing, investments, and future sale transactions. However, tax planning must be lawful and properly documented. Artificial structures without business purpose may be challenged.
F. Exit Planning
If the founders later sell the app, they may sell:
- shares of the operating company;
- shares of the holding company;
- specific intellectual property assets;
- license rights;
- regional rights;
- the brand separately from operations.
A clean holding structure creates flexibility.
IV. Holding Company Versus Operating Company
A. Holding Company
The holding company usually owns assets and investments.
It may:
- own trademarks;
- own source code;
- own shares in subsidiaries;
- license IP;
- receive royalties;
- raise investment at parent level;
- own strategic contracts;
- manage brand standards;
- approve major decisions.
It may not necessarily deal directly with customers.
B. Operating Company
The operating company conducts daily business.
It may:
- operate the app;
- contract with users;
- collect revenue;
- pay suppliers;
- hire employees;
- manage customer support;
- handle disputes;
- comply with consumer rules;
- process personal data;
- maintain business permits;
- file taxes on operations.
C. Why Separate Them?
The separation helps preserve the most valuable assets if the operating business faces claims. It also allows the group to create new operating subsidiaries without transferring brand ownership each time.
However, separation works only if the companies actually observe separate legal personalities, maintain proper contracts, and avoid commingling funds.
V. Is a Holding Company Always Necessary?
No. A holding company is not always necessary.
A simple corporation may be enough if:
- the business is small;
- there is only one app and one revenue stream;
- there are no outside investors;
- the risk level is low;
- there are no foreign expansion plans;
- cost must be minimized;
- IP ownership is simple;
- founders want straightforward compliance.
A holding structure may be better if:
- the brand is valuable;
- there are multiple products;
- investors are expected;
- the app has high user or data risk;
- the company will license or franchise the brand;
- founders want to separate IP from operations;
- foreign expansion is planned;
- there are multiple founders and equity arrangements;
- the business may spin off subsidiaries;
- the app may enter regulated sectors.
The best structure depends on cost, risk, tax, and business goals.
VI. Common Corporate Structures for a Brand and App Business
A. Single Corporation Structure
One corporation owns and operates everything.
Example:
BrandApp Corporation
- owns trademark;
- owns source code;
- operates app;
- hires staff;
- signs all contracts;
- receives all revenue.
Advantages:
- simpler;
- cheaper;
- easier accounting;
- fewer intercompany contracts;
- easier for early-stage startups.
Disadvantages:
- all assets exposed to operating liabilities;
- less flexible for spin-offs;
- harder to isolate business lines;
- IP may be exposed to creditors.
B. Holding Company Plus Operating Company
Example:
BrandApp Holdings Corporation
- owns trademark and app IP;
- owns shares in operating company.
BrandApp Operations Corporation
- operates app;
- signs customer contracts;
- receives operating revenue;
- pays license fee to holding company.
Advantages:
- separates IP from operations;
- investor-friendly if documented;
- easier to add subsidiaries;
- brand control centralized.
Disadvantages:
- more expensive;
- more compliance;
- intercompany contracts needed;
- transfer pricing and tax documentation required;
- substance must be respected.
C. Founder-Owned Holding Company
Founders own a holding company that owns the operating company.
Example:
Founders → Holding Company → Operating Company
This is common for groups that plan to create several businesses under one parent.
D. IP Holding Company Only
The IP company owns trademarks and software, while one or more operating companies license the IP.
Example:
Brand IP Corporation
- owns trademarks, software, domain names.
Brand PH Corporation
- operates Philippine app.
Brand SG Pte. Ltd.
- operates Singapore app.
This is useful for regional expansion, but it requires strong tax and legal planning.
E. Offshore Holding Company
Some startups use a foreign parent company for venture capital, foreign investors, or regional expansion.
This requires careful analysis of:
- Philippine foreign ownership rules;
- tax consequences;
- intellectual property transfer;
- exchange controls;
- withholding taxes;
- substance requirements;
- securities laws;
- investor requirements;
- exit planning.
An offshore parent should not be used casually.
VII. Choosing the Corporate Vehicle
In the Philippines, the usual vehicle for a holding company is a stock corporation.
A. Stock Corporation
A stock corporation is suitable if founders want shares, dividends, investors, and future transferability.
It is the usual vehicle for startups and holding companies.
B. One Person Corporation
A One Person Corporation may be useful for a solo founder. It allows a single stockholder to incorporate, subject to restrictions.
It may be useful as:
- a solo founder’s holding company;
- an IP holding company;
- a consulting or development entity.
However, investors may later prefer conversion or restructuring.
C. Partnership
A partnership is generally less ideal for app businesses seeking investors because partners may have broader liability and transfer issues.
D. Sole Proprietorship
A sole proprietorship is not ideal for a scalable app business because it has no separate juridical personality from the owner. The owner is personally liable.
A sole proprietorship may be acceptable for early testing, but not for serious app operations, brand protection, or investment readiness.
VIII. Incorporation With the SEC
To form a corporation or holding company in the Philippines, incorporation is done through the Securities and Exchange Commission.
The usual incorporation documents include:
- proposed corporate name;
- articles of incorporation;
- bylaws;
- details of incorporators;
- details of directors and officers;
- principal office address;
- corporate purpose clauses;
- capital structure;
- treasurer’s affidavit or certification where required;
- beneficial ownership information;
- other SEC forms and declarations.
After SEC registration, the corporation obtains a certificate of incorporation and becomes a juridical person.
IX. Corporate Name Versus Brand Name Versus Trademark
Many founders confuse these three.
A. Corporate Name
This is the legal name registered with the SEC.
Example: Blue Mango Holdings Corporation
It identifies the corporation as a juridical person.
B. Business Name or Trade Name
This is the name used for business operations.
Example: Blue Mango App
A corporation may use a trade name, subject to proper registration and compliance.
C. Trademark
This protects the brand as an intellectual property asset.
Example: BLUE MANGO for downloadable software, online marketplace services, payment services, advertising services, or related classes.
Registering a corporate name with the SEC does not automatically give trademark protection. A company may be incorporated under a name but still face a trademark dispute if another party has superior trademark rights.
The brand should be protected through trademark registration.
X. Drafting the Primary Purpose Clause
A holding company’s primary purpose clause should be drafted carefully.
It may include authority to:
- hold shares in other corporations;
- acquire, own, hold, sell, exchange, and dispose of investments;
- own, license, assign, and manage intellectual property;
- develop, acquire, license, and commercialize software;
- own brands, trademarks, copyrights, domain names, and digital assets;
- provide management, administrative, technical, and strategic services to affiliates;
- receive royalties, dividends, and service fees;
- engage in lawful business incidental to the foregoing.
The exact language should be tailored to SEC requirements and the company’s business model.
If the operating company will operate the app directly, its purpose clause should include:
- software development;
- operation of digital platform;
- e-commerce or marketplace activities, if applicable;
- advertising;
- subscription services;
- data processing;
- content distribution;
- technology services;
- payment facilitation, if applicable and lawful;
- other app-specific activities.
If the app enters regulated activities, the purpose clause alone is not enough. Special licenses may be required.
XI. Capitalization
A corporation must have an authorized capital stock, subscribed capital, and paid-up capital consistent with law and business needs.
For a holding company, capitalization should consider:
- future investors;
- founder equity split;
- option pool;
- preferred shares;
- voting and non-voting shares;
- foreign ownership rules;
- minimum capital for regulated activities;
- paid-up capital required for business permits or licenses;
- tax and accounting treatment.
A startup may begin with modest capital, but undercapitalization may create practical problems when opening bank accounts, entering contracts, or applying for permits.
XII. Share Classes
Founders may consider different classes of shares, such as:
- common shares;
- preferred shares;
- voting preferred shares;
- non-voting preferred shares;
- redeemable preferred shares;
- founder shares;
- employee option shares.
Share classes must be properly authorized in the articles of incorporation.
Investors may later request preferred shares with rights such as:
- liquidation preference;
- anti-dilution protection;
- board seat;
- veto rights;
- information rights;
- conversion rights;
- redemption rights.
It is easier to plan early than to restructure under pressure.
XIII. Founders’ Agreement
Before or soon after incorporation, founders should sign a founders’ agreement.
It should cover:
- equity split;
- roles and responsibilities;
- vesting of shares;
- cliff period;
- intellectual property assignment;
- confidentiality;
- non-solicitation;
- non-compete to the extent enforceable;
- decision-making;
- deadlock resolution;
- founder departure;
- bad leaver and good leaver rules;
- transfer restrictions;
- dispute resolution;
- funding obligations;
- salaries;
- reimbursement;
- use of company name and assets.
Many startup disputes arise because founders verbally agree on equity but never document vesting, IP ownership, or exit rights.
XIV. Share Vesting
Vesting protects the company if a founder leaves early.
Example:
- founder receives 40% equity;
- shares vest over four years;
- one-year cliff;
- unvested shares are subject to repurchase or forfeiture if founder leaves.
Without vesting, a founder may leave after two months and still own a large percentage permanently, making the company unattractive to investors.
Vesting must be properly structured under Philippine corporate and tax law. Shares cannot simply disappear without legal mechanism.
XV. Shareholders’ Agreement
A shareholders’ agreement governs relations among shareholders.
It may include:
- voting arrangements;
- reserved matters;
- board composition;
- pre-emptive rights;
- right of first refusal;
- tag-along rights;
- drag-along rights;
- transfer restrictions;
- founder lock-up;
- confidentiality;
- non-circumvention;
- anti-dilution;
- dividend policy;
- exit rights;
- dispute resolution;
- deadlock mechanisms;
- valuation methods.
For a holding company, the shareholders’ agreement is central because it controls the parent company that owns the group’s key assets.
XVI. Board and Officers
A corporation must have directors and officers.
Typical officers include:
- president;
- treasurer;
- corporate secretary;
- compliance officer, where needed;
- data protection officer, where applicable;
- other officers such as CEO, CTO, COO, CFO.
A holding company should have board resolutions approving:
- incorporation of subsidiaries;
- acquisition of IP;
- licensing of brand and software;
- bank accounts;
- investment transactions;
- issuance of shares;
- appointment of officers;
- intercompany agreements;
- major contracts.
Corporate acts should be documented to preserve limited liability.
XVII. Post-Incorporation Requirements
After SEC incorporation, a corporation must complete other registrations.
These commonly include:
- barangay registration;
- mayor’s permit or business permit;
- BIR registration;
- books of accounts;
- official receipts or invoices;
- authority to print or electronic invoicing compliance where applicable;
- registration with SSS, PhilHealth, and Pag-IBIG if hiring employees;
- business bank account;
- data privacy registration or compliance where applicable;
- permits for regulated activities;
- annual SEC filings;
- annual tax filings;
- audited financial statements where required.
A holding company with no operations may have fewer local permit needs, but it still has corporate, tax, and reporting obligations.
XVIII. BIR Registration and Tax Compliance
A corporation must register with the Bureau of Internal Revenue.
Key tax matters include:
- registration of tax types;
- issuance of receipts or invoices;
- withholding taxes;
- income tax;
- value-added tax or percentage tax, depending on status;
- documentary stamp tax on share issuances and certain instruments;
- tax on royalties;
- tax on dividends;
- compensation withholding if employees are hired;
- expanded withholding tax on services;
- tax filing deadlines;
- audited financial statements.
A holding company receiving royalties, dividends, or management fees must account for them properly.
XIX. Local Business Permits
The local government unit where the corporation has its principal office may require a business permit.
A pure holding company may still need local registration depending on local practice. An operating app company definitely needs local business permits where it conducts business from an office.
If the app has physical branches, warehouses, kiosks, or local operations, additional permits may be required.
XX. Bank Account Opening
Banks usually require:
- SEC certificate;
- articles of incorporation;
- bylaws;
- general information sheet;
- board resolution;
- IDs of authorized signatories;
- beneficial ownership declarations;
- business permit or proof of registration;
- BIR registration;
- company profile;
- source of funds explanation.
A holding company should have separate bank accounts from the operating company and founders.
Never mix personal funds, holding company funds, and operating company funds.
XXI. Maintaining Separate Legal Personality
A holding company structure works only if corporate separateness is respected.
To preserve separate personality:
- maintain separate bank accounts;
- maintain separate books;
- sign contracts in correct company name;
- issue invoices from the proper entity;
- pay intercompany fees under written agreements;
- avoid using one company’s funds for another without documentation;
- hold board meetings and issue resolutions;
- maintain corporate records;
- observe tax filings;
- avoid undercapitalizing operating companies;
- avoid misleading creditors;
- avoid using the holding company to commit fraud.
If companies are used interchangeably, creditors may attempt to pierce the corporate veil.
XXII. Intellectual Property Strategy
For a brand and app business, IP protection is central.
Key assets include:
- trademarks;
- copyrights;
- source code;
- UI/UX designs;
- databases;
- trade secrets;
- domain names;
- social media handles;
- app store developer accounts;
- content;
- logos;
- icons;
- design systems;
- documentation;
- algorithms;
- business processes;
- patents or utility models, if applicable.
The company must identify, assign, register, and protect these assets.
XXIII. Trademark Protection
A brand should be protected by trademark registration with the Intellectual Property Office of the Philippines.
A. What can be registered?
Possible trademarks include:
- brand name;
- logo;
- slogan;
- app name;
- product name;
- service name;
- icon;
- stylized word mark;
- combination mark.
B. Why register?
Trademark registration helps prevent others from using confusingly similar marks for related goods or services. It also supports app store complaints, takedowns, licensing, franchising, investor diligence, and brand valuation.
C. Classes
Trademarks are registered by class of goods or services. An app business may need classes covering:
- downloadable software;
- software as a service;
- online marketplace services;
- advertising services;
- financial services, if applicable;
- telecommunications or platform services;
- education or entertainment services;
- e-commerce retail services;
- delivery or logistics services;
- other business-specific categories.
The correct classes depend on the app’s actual services.
D. Word mark and logo
It is often wise to file both:
- word mark for the brand name; and
- logo mark for the design.
A word mark gives broader protection for the name regardless of logo style.
E. Search before filing
Before investing in a brand, conduct clearance searches to reduce risk of conflict with prior trademarks, company names, domain names, and market users.
XXIV. Business Name Is Not Trademark Protection
Registering with the SEC or DTI does not equal trademark ownership.
A corporation may register ABC Tech Corporation, but another business may own the trademark ABC for software services. The corporate name registration may not protect against trademark infringement.
The brand should be separately cleared and filed as a trademark.
XXV. Copyright Protection for Software
Software source code is generally protected by copyright as a literary work. UI designs, graphics, text, images, videos, and documentation may also be protected.
Copyright may exist upon creation, but registration or deposit can help prove ownership.
Important point: the company must own the copyright. If freelancers, agencies, employees, or founders created the code or designs, there must be proper assignment or employment documentation.
XXVI. Who Owns the App Code?
This is one of the most important issues.
The app code may have been written by:
- founder;
- employee developer;
- freelance developer;
- software agency;
- offshore contractor;
- open-source contributors;
- AI-assisted tools;
- interns;
- consultants.
Ownership depends on contracts, employment status, scope of work, and intellectual property clauses.
A company should not assume it owns code just because it paid for development. A written IP assignment is essential, especially for contractors.
XXVII. Developer Agreements
Every developer or agency should sign a written agreement covering:
- scope of work;
- deliverables;
- milestones;
- payment;
- ownership of source code;
- assignment of copyright;
- moral rights waivers or consents where applicable;
- confidentiality;
- open-source software use;
- third-party components;
- warranties of originality;
- security standards;
- documentation;
- access credentials;
- repository ownership;
- handover obligations;
- bug fixes;
- maintenance;
- non-solicitation;
- dispute resolution.
The company should ensure that all code repositories are owned or controlled by the company, not the developer’s personal account.
XXVIII. Employee IP Clauses
Employment contracts for developers, designers, marketers, product managers, and content creators should include:
- work-for-hire or assignment language;
- confidentiality;
- invention assignment;
- duty to disclose creations;
- return of company property;
- non-use of company IP after employment;
- data protection obligations;
- cybersecurity rules;
- access control;
- open-source compliance;
- social media account control;
- non-solicitation where lawful.
Employees should create work within the scope of employment using company systems where possible.
XXIX. Founder IP Assignment
If founders created the brand, app concept, prototype, domain, code, logo, or content before incorporation, they should assign the relevant IP to the company.
This is commonly missed.
A founder IP assignment should cover:
- brand names;
- logos;
- domains;
- source code;
- designs;
- prototypes;
- business plans;
- databases;
- social media accounts;
- content;
- app store accounts;
- trade secrets;
- related goodwill.
Investors will ask whether the company owns founder-created IP.
XXX. IP Ownership Between Holding Company and Operating Company
A common structure is:
- holding company owns IP;
- operating company receives license.
The IP license should cover:
- licensed trademarks;
- software;
- domain names;
- content;
- territory;
- exclusivity;
- duration;
- royalties;
- quality control;
- data rights;
- sublicensing;
- termination;
- breach;
- improvements;
- ownership of updates;
- support obligations.
If the operating company creates improvements, the agreement should state whether improvements automatically belong to the holding company or are assigned periodically.
XXXI. Intercompany IP License
An intercompany IP license is important for tax and legal purposes.
It should answer:
- What IP is licensed?
- Who owns improvements?
- Can the operating company sublicense?
- What royalty is payable?
- Is the royalty arm’s length?
- What happens if the operating company defaults?
- Can the holding company terminate?
- What happens to users if license terminates?
- Who handles enforcement against infringers?
- Who bears maintenance and registration costs?
Without a written license, the structure may be questioned.
XXXII. Domain Names and Social Media Accounts
Digital identity assets must be controlled.
The company should ensure that it owns or controls:
- domain names;
- DNS account;
- hosting account;
- SSL certificates;
- cloud accounts;
- app store developer accounts;
- social media pages;
- email domain;
- analytics accounts;
- ad accounts;
- payment gateway accounts;
- code repositories;
- design tools;
- customer support tools;
- CRM tools.
These should not remain under a founder’s personal email without documentation.
Access control should be documented and protected by multi-factor authentication.
XXXIII. App Store Accounts
For mobile apps, the developer accounts with Apple, Google, Huawei, Samsung, or other platforms are important assets.
The company should consider:
- account owner;
- developer legal name;
- payment account;
- app listing ownership;
- app transfer rules;
- compliance with app store policies;
- privacy labels;
- in-app payment rules;
- user data handling;
- age ratings;
- content moderation;
- refund policies;
- takedown risk.
If the app is published under a developer’s personal account, the company may have problems later.
XXXIV. Trade Secrets
Trade secrets may include:
- algorithms;
- business logic;
- pricing models;
- customer lists;
- supplier lists;
- growth strategies;
- user acquisition methods;
- source code not publicly available;
- security architecture;
- analytics data;
- AI models and prompts;
- internal documentation.
To protect trade secrets, the company should use:
- NDAs;
- confidentiality clauses;
- access controls;
- encryption;
- need-to-know permissions;
- exit procedures;
- device management;
- password management;
- repository controls;
- audit logs;
- employee training.
A trade secret is protected only if the company takes reasonable steps to keep it secret.
XXXV. Patents and Utility Models
Most app ideas are not patentable merely because they are business methods or software concepts. However, certain technical inventions may be protectable if they meet legal requirements.
Possible protectable items may include:
- technical process;
- hardware-software integration;
- novel technical system;
- device-related invention;
- utility model.
Patent strategy should be assessed early if the business has genuine technical innovation.
XXXVI. Branding and Trademark Clearance
Before launching a brand, check:
- IPOPHL trademark records;
- SEC corporate names;
- DTI business names;
- domain availability;
- app store names;
- social media handles;
- marketplace usage;
- search engine results;
- foreign trademark databases if expanding abroad.
Avoid choosing a brand that is:
- generic;
- descriptive without distinctiveness;
- too similar to competitors;
- geographically misleading;
- offensive;
- legally restricted;
- already used for similar services;
- hard to protect.
A strong brand is distinctive and registrable.
XXXVII. Data Privacy Compliance
An app business almost always processes personal data.
Personal data may include:
- name;
- email;
- phone number;
- address;
- birthdate;
- government ID;
- location;
- device ID;
- IP address;
- payment details;
- photos;
- messages;
- transaction history;
- behavioral data;
- health data;
- financial data;
- children’s data;
- biometrics.
The company must comply with the Data Privacy Act and related rules.
XXXVIII. Data Privacy Program
A proper data privacy program should include:
- privacy notice;
- terms of use;
- consent mechanisms where needed;
- lawful basis for processing;
- data inventory;
- data flow mapping;
- data sharing agreements;
- outsourcing agreements;
- security measures;
- breach response plan;
- data subject rights procedure;
- retention policy;
- deletion policy;
- privacy impact assessment;
- appointment of Data Protection Officer where required;
- registration where applicable;
- employee training;
- incident logs.
Data privacy compliance is not just a privacy policy copied from another app.
XXXIX. Privacy Notice for App Users
The privacy notice should explain:
- who controls the data;
- what data is collected;
- why data is collected;
- legal basis for processing;
- how data is used;
- who receives the data;
- whether data is transferred abroad;
- how long data is retained;
- user rights;
- how to contact the DPO;
- security measures;
- complaint process.
It should be clear, accessible, and consistent with actual app behavior.
XL. Terms of Use
The app must have terms of use governing the relationship with users.
Terms may include:
- account registration;
- eligibility;
- user obligations;
- prohibited conduct;
- content rules;
- payments;
- refunds;
- subscriptions;
- service limitations;
- intellectual property;
- user-generated content license;
- disclaimers;
- limitation of liability;
- suspension and termination;
- dispute resolution;
- governing law;
- privacy references;
- updates to terms.
Terms should match the business model. A marketplace, fintech app, delivery app, SaaS tool, dating app, gaming app, and health app need different terms.
XLI. User-Generated Content
If the app allows users to post content, upload photos, send messages, review products, comment, livestream, or publish listings, the terms should address:
- ownership of user content;
- license to display and distribute content;
- prohibited content;
- takedown procedure;
- moderation rights;
- reporting mechanism;
- copyright complaints;
- defamation issues;
- illegal content;
- child safety;
- harassment;
- community guidelines;
- account suspension.
The company should have a content moderation policy.
XLII. Consumer Protection
If the app sells goods or services to consumers, consumer protection rules apply.
The app should disclose:
- seller identity;
- product or service description;
- price;
- fees;
- taxes;
- delivery terms;
- refund policy;
- warranty terms;
- complaint process;
- cancellation rights;
- subscription renewal terms;
- payment security;
- customer support.
Misleading advertisements, hidden charges, unfair terms, fake scarcity, unauthorized recurring billing, and refusal to honor lawful refunds can create liability.
XLIII. E-Commerce Compliance
If the app operates an online marketplace or e-commerce platform, it should address:
- seller onboarding;
- seller verification;
- product listing rules;
- prohibited items;
- counterfeit goods;
- consumer complaints;
- refund and return mechanisms;
- logistics terms;
- payment processing;
- platform liability;
- tax invoicing;
- data privacy;
- terms between buyer, seller, and platform.
The platform should clearly state whether it is the seller, marketplace, agent, payment facilitator, or technology provider.
XLIV. Payment Processing
If the app accepts payments, the company must structure payment flows carefully.
Options include:
- payment gateway;
- e-wallet integration;
- bank transfer;
- card processor;
- in-app purchase;
- subscription billing;
- escrow-like arrangement;
- marketplace payout system.
If the company holds customer funds, facilitates payments, remittances, stored value, e-money, lending, or investment activity, special regulation may apply.
The app should not accidentally operate a regulated financial service without a license.
XLV. Fintech and Lending Features
If the app involves lending, credit, buy-now-pay-later, e-wallets, remittance, investment, crowdfunding, insurance, virtual assets, or payment services, additional licenses may be required.
Possible regulated activities include:
- lending;
- financing;
- securities offering;
- crowdfunding;
- e-money issuance;
- remittance;
- payment systems;
- insurance brokerage;
- investment advice;
- virtual asset services.
A corporate purpose clause is not enough. The company must obtain the proper regulatory authority before operating.
XLVI. Foreign Ownership Restrictions
Foreign ownership is a critical issue in Philippine corporate structuring.
A foreigner may own up to 100% of many technology and software companies, but restrictions may apply depending on the business activity.
Potentially restricted areas include:
- mass media;
- advertising;
- public utilities;
- retail trade under certain thresholds;
- land ownership;
- educational institutions;
- financing or lending under certain rules;
- professions;
- nationalized activities;
- certain security-sensitive industries.
A holding company with foreign investors must be structured carefully so it does not violate nationality restrictions of the operating subsidiaries.
XLVII. App Business and Mass Media Risk
Some digital platforms may raise mass media concerns if their primary business is publishing, broadcasting, or disseminating content to the general public.
A purely software tool may not be mass media. But a content platform, news app, publication, streaming channel, or ad-supported media business may need careful analysis.
If foreign investors are involved, this becomes important.
XLVIII. Advertising Business Restrictions
If the app operates as an advertising agency or derives revenue from advertising services, foreign ownership restrictions may be relevant.
A platform that merely sells ad inventory may be treated differently from an advertising agency, depending on the facts. The structure should be reviewed before accepting foreign investment.
XLIX. Retail and Marketplace Restrictions
If the app sells goods directly to consumers, retail trade rules may matter, especially if foreign-owned.
If the app is only a marketplace connecting sellers and buyers, the analysis may differ. But if the platform itself buys and resells goods, inventory ownership and retail restrictions should be examined.
L. Employment and Contractor Issues
The operating company may hire:
- developers;
- designers;
- product managers;
- marketing staff;
- customer support;
- content moderators;
- sales staff;
- operations staff;
- consultants;
- freelancers.
The company must distinguish employees from independent contractors.
Misclassification can lead to labor claims.
Employment contracts should cover:
- position;
- salary;
- benefits;
- work hours;
- confidentiality;
- IP assignment;
- data privacy;
- remote work;
- company equipment;
- code of conduct;
- termination;
- non-solicitation;
- conflict of interest.
Contractor agreements should avoid control elements that make the relationship look like employment unless employment is intended.
LI. Remote Work
App businesses often use remote work. Policies should address:
- work hours;
- deliverables;
- equipment;
- cybersecurity;
- data access;
- confidentiality;
- monitoring;
- reimbursement;
- occupational safety;
- tax and labor compliance;
- cross-border contractors;
- return of equipment.
Remote work does not remove employer obligations.
LII. Confidentiality and NDAs
The company should use confidentiality agreements with:
- founders;
- employees;
- contractors;
- investors;
- advisors;
- beta testers;
- vendors;
- agencies;
- potential partners;
- acquisition prospects.
An NDA should define confidential information, exclusions, permitted use, duration, return or destruction, remedies, and governing law.
For investor discussions, many investors resist NDAs at early pitch stage. The company should avoid disclosing sensitive source code or trade secrets too early.
LIII. Non-Compete and Non-Solicitation
Non-compete clauses are enforceable only if reasonable as to time, geography, scope, and legitimate business interest. Overbroad non-competes may be challenged.
Non-solicitation clauses are often more practical. They may restrict solicitation of employees, contractors, customers, vendors, or users for a reasonable period.
Use these clauses carefully.
LIV. Cybersecurity
An app business must protect its systems.
Cybersecurity measures should include:
- secure development practices;
- code review;
- vulnerability testing;
- access control;
- multi-factor authentication;
- encryption;
- secure cloud configuration;
- incident response plan;
- regular backups;
- least privilege access;
- vendor security review;
- logging and monitoring;
- penetration testing where appropriate;
- employee training;
- secure API management.
Poor cybersecurity can create contractual, privacy, consumer, and reputational liability.
LV. Data Breach Response
If personal data is compromised, the company may have notification obligations.
A breach response plan should identify:
- incident response team;
- DPO role;
- technical containment;
- forensic review;
- legal assessment;
- user notification;
- regulator notification;
- public communication;
- remediation;
- evidence preservation;
- vendor coordination.
The operating company and holding company should know who is the personal information controller and who is the processor.
LVI. AI, Automation, and Algorithmic Features
If the app uses AI, recommendation engines, automated scoring, chatbots, or user profiling, the company should address:
- transparency;
- bias;
- data sources;
- consent;
- user rights;
- intellectual property in AI outputs;
- third-party AI terms;
- confidentiality of prompts and data;
- hallucination risk;
- human review;
- prohibited uses;
- sector-specific restrictions.
If AI processes sensitive personal information or makes significant decisions about users, risk increases.
LVII. Open-Source Software Compliance
Many apps use open-source libraries.
The company should track:
- library name;
- license type;
- version;
- obligations;
- attribution requirements;
- source disclosure obligations;
- copyleft risk;
- security vulnerabilities;
- update obligations.
Failure to comply with open-source licenses may create IP and investor diligence problems.
LVIII. Software Development Lifecycle Documentation
Investors and acquirers may ask for:
- code repository history;
- contributor list;
- IP assignments;
- open-source inventory;
- architecture documentation;
- security documentation;
- bug tracking;
- release notes;
- development roadmap;
- test records;
- deployment controls;
- incident history.
A startup should organize these early.
LIX. Vendor Contracts
App businesses depend on vendors such as:
- cloud providers;
- payment gateways;
- SMS providers;
- email service providers;
- analytics tools;
- ad networks;
- customer support tools;
- outsourced developers;
- cybersecurity firms;
- content moderation providers;
- logistics providers.
Vendor contracts should cover:
- scope;
- service levels;
- fees;
- data protection;
- confidentiality;
- security;
- intellectual property;
- liability;
- indemnity;
- termination;
- business continuity;
- audit rights;
- dispute resolution.
If vendors process personal data, data sharing or outsourcing agreements may be needed.
LX. Customer Contracts
Depending on the app, customer contracts may include:
- terms of use;
- subscription agreement;
- service agreement;
- enterprise SaaS agreement;
- marketplace seller agreement;
- advertiser agreement;
- API license;
- data processing agreement;
- support terms;
- service level agreement.
Enterprise customers often require stronger warranties, uptime commitments, data protection clauses, and indemnities.
LXI. Brand Protection Online
To protect the brand online:
- register trademarks;
- secure domain names;
- secure common misspellings;
- reserve social media handles;
- monitor app stores;
- monitor marketplaces;
- monitor fake pages;
- use takedown mechanisms;
- send cease-and-desist letters;
- document infringement;
- enforce consistently.
A brand can be lost or weakened if infringement is ignored.
LXII. App Name Conflicts
App store approval does not guarantee trademark safety. Another party may file a trademark complaint and force takedown if it owns superior rights.
Before launch, the company should clear the app name and file trademarks.
LXIII. Domain Name Disputes
If someone registers a confusingly similar domain, remedies may include:
- demand letter;
- domain dispute procedure;
- trademark complaint;
- court action;
- negotiation or purchase;
- platform takedown.
Trademark registration strengthens the company’s position.
LXIV. Social Media Handle Disputes
Social media platforms often require proof of trademark rights or impersonation before transferring or removing handles.
Keep:
- trademark certificates;
- brand guidelines;
- company documents;
- evidence of first use;
- screenshots of impersonation;
- user confusion reports.
LXV. Brand Guidelines
A holding company licensing the brand should create brand guidelines covering:
- logo use;
- colors;
- typography;
- slogans;
- tone of voice;
- prohibited uses;
- co-branding;
- quality standards;
- app design standards;
- marketing claims;
- approval process.
Brand guidelines help preserve trademark quality control.
LXVI. Licensing the Brand
If the holding company licenses the brand to affiliates or third parties, the license should include:
- licensed marks;
- territory;
- field of use;
- quality control;
- royalty;
- reporting;
- inspection rights;
- marketing approval;
- restrictions;
- termination;
- post-termination obligations;
- ownership acknowledgment.
Trademark licensing without quality control can weaken the brand.
LXVII. Franchising
If the business expands by allowing third parties to use the brand and system, it may become a franchise or quasi-franchise.
Franchise documents may include:
- franchise agreement;
- operations manual;
- brand license;
- training agreement;
- territorial rights;
- fees and royalties;
- performance standards;
- audit rights;
- termination rules.
Franchising requires careful legal planning, especially for consumer-facing businesses.
LXVIII. Tax Issues in Holding Structures
A holding structure may involve several tax issues.
A. Dividends
Operating company profits may be distributed to the holding company as dividends, subject to applicable tax rules.
B. Royalties
If the operating company licenses IP from the holding company, royalty payments may be taxable and may be subject to withholding.
C. Management Fees
The holding company may charge management or administrative fees if it provides real services.
Fees should be supported by contracts, invoices, and actual services.
D. Transfer Pricing
Related-party transactions should be commercially reasonable and properly documented.
E. VAT or Percentage Tax
Royalties, management fees, and service fees may have VAT or percentage tax consequences depending on registration and thresholds.
F. Documentary Stamp Tax
Share issuances, debt instruments, and certain transactions may trigger documentary stamp tax.
G. Tax Avoidance Risk
A structure with no business purpose, artificial pricing, or sham transactions may be challenged.
Tax advice is important before implementing intercompany charges.
LXIX. Accounting for Intercompany Transactions
The holding company and operating company should document:
- IP license fees;
- management fees;
- cost-sharing;
- shareholder advances;
- loans;
- dividends;
- expense reimbursements;
- asset transfers;
- software development charges.
Each transaction should have:
- agreement;
- invoice;
- board approval where appropriate;
- payment records;
- tax withholding;
- accounting entries.
LXX. Funding the Business
Funding may come from:
- founder capital contributions;
- shareholder loans;
- convertible notes;
- simple agreements for future equity;
- preferred share investment;
- venture capital;
- angel investors;
- bank loans;
- grants;
- strategic partners;
- revenue financing.
Each funding method has legal and tax consequences.
A holding company structure should identify whether investors invest in the holding company or operating company.
LXXI. Founder Loans Versus Equity
If founders put money into the company, document whether it is:
- paid-in capital;
- additional paid-in capital;
- shareholder loan;
- reimbursable expense;
- convertible instrument.
Unclear founder funding creates disputes later.
LXXII. Convertible Notes and SAFEs
Startup financing may use convertible instruments. Philippine law treatment should be reviewed carefully.
Key terms include:
- principal amount;
- maturity;
- interest;
- valuation cap;
- discount;
- conversion trigger;
- qualified financing;
- company sale;
- default;
- governing law;
- tax treatment;
- corporate approvals.
Investors may prefer a foreign holding company if they are used to foreign-law SAFEs, but this must be weighed against Philippine law and business realities.
LXXIII. Securities Law Concerns
Issuing shares or investment instruments may involve securities law. Private placements must be structured properly.
A company should not publicly solicit investments without compliance.
Offering app tokens, revenue shares, profit participation, or investment contracts may trigger securities regulation.
LXXIV. Employee Stock Option Plans
Startups may give equity incentives.
An employee stock option plan should address:
- eligible participants;
- option pool size;
- vesting;
- exercise price;
- exercise period;
- termination;
- tax treatment;
- board approval;
- shareholder approval;
- dilution;
- documentation.
In the Philippines, equity compensation requires careful tax and corporate planning.
LXXV. Corporate Records and Cap Table
Maintain:
- stock and transfer book;
- minutes book;
- board resolutions;
- shareholder resolutions;
- subscription agreements;
- share certificates;
- cap table;
- option ledger;
- investment agreements;
- founder vesting records;
- beneficial ownership records.
A messy cap table can block investment.
LXXVI. Protecting Against Founder Disputes
Founder disputes commonly involve:
- equity split;
- unequal work contributions;
- IP ownership;
- personal use of company funds;
- side projects;
- removal from management;
- deadlock;
- sale of shares;
- dilution;
- use of brand after departure.
Preventive tools include:
- founders’ agreement;
- vesting;
- clear job roles;
- reserved matters;
- deadlock mechanism;
- buy-sell provisions;
- IP assignment;
- expense policy;
- conflict of interest policy.
LXXVII. Related-Party Transactions
A founder may own a supplier, developer agency, marketing company, or landlord that deals with the app company.
Related-party transactions should be:
- disclosed;
- approved properly;
- commercially reasonable;
- documented;
- priced fairly;
- recorded in accounts.
Undisclosed related-party transactions can create investor and tax issues.
LXXVIII. Protecting the Brand From Founders
The brand should belong to the company, not an individual founder, unless intentionally structured otherwise.
Transfer to the company:
- domain registrations;
- social media pages;
- trademark applications;
- logo files;
- design files;
- app store accounts;
- code repositories;
- marketing content;
- customer lists.
If a founder leaves while controlling the domain or app store account, the business may be paralyzed.
LXXIX. Protecting the Company From Contractors
Contractors should not retain:
- source code control;
- production server access;
- domain access;
- admin credentials;
- cloud root accounts;
- app store access;
- customer database copies;
- confidential documentation;
- design files.
Use:
- written contracts;
- access revocation;
- code escrow where needed;
- milestone handover;
- repository ownership;
- confidentiality;
- IP assignment;
- post-termination obligations.
LXXX. Regulated App Categories
Some app categories require special caution.
A. Lending and Credit Apps
Require lending or financing compliance and may trigger SEC regulation.
B. Payment and Wallet Apps
May require BSP regulation.
C. Investment Apps
May trigger securities regulation.
D. Health Apps
May involve health data, medical advice, professional regulation, and sensitive personal information.
E. Education Apps
May require education-related compliance if offering formal instruction or credentials.
F. Transport or Delivery Apps
May involve transport, labor, logistics, and consumer rules.
G. Food Apps
May involve food safety, seller compliance, and marketplace liability.
H. Dating or Social Apps
May involve child safety, content moderation, harassment, and privacy.
I. Gaming Apps
May involve gambling rules if chance, prizes, betting, or cash-out features are present.
J. Crypto or Token Apps
May involve securities, virtual asset, anti-money laundering, and BSP-related issues.
LXXXI. App Terms for Regulated Features
If the app includes regulated features, terms should not pretend the company is merely a software provider if it actually controls regulated services.
The legal structure must match the actual business.
For example:
- A lending app cannot avoid lending regulation by calling itself a “technology platform” if it effectively lends money.
- A wallet app cannot avoid payment regulation by calling stored value “credits.”
- An investment app cannot avoid securities rules by calling returns “rewards.”
- A gambling-like game cannot avoid gambling rules by calling bets “tokens.”
Substance matters.
LXXXII. Anti-Money Laundering Considerations
Certain businesses may have AML obligations, especially if they involve financial services, virtual assets, remittances, payments, investments, or high-value transactions.
AML compliance may require:
- customer identification;
- recordkeeping;
- suspicious transaction monitoring;
- reporting;
- sanctions screening;
- staff training;
- compliance officer;
- risk assessment.
A typical non-financial app may not be covered, but fintech apps must check.
LXXXIII. Platform Liability
An app platform may face liability from:
- user misconduct;
- seller fraud;
- counterfeit goods;
- data breach;
- payment failure;
- misleading listings;
- harmful content;
- illegal products;
- unsafe services;
- defective digital content;
- consumer complaints.
Terms of use help but do not eliminate all liability.
The platform should implement:
- user verification;
- reporting mechanisms;
- seller rules;
- takedown procedures;
- moderation;
- refunds process;
- fraud detection;
- complaint escalation.
LXXXIV. Insurance
Insurance may help manage risk.
Possible insurance includes:
- general liability;
- cyber liability;
- directors and officers insurance;
- professional liability;
- errors and omissions;
- crime or fidelity insurance;
- property insurance;
- employer liability;
- key person insurance.
Startups often ignore insurance until a major incident occurs.
LXXXV. Brand and App Due Diligence Checklist
Before launching or raising funds, prepare:
- SEC documents;
- business permits;
- BIR registration;
- tax filings;
- audited financials, if applicable;
- cap table;
- founders’ agreement;
- shareholders’ agreement;
- IP assignments;
- developer contracts;
- trademark filings;
- copyright records;
- domain ownership proof;
- app store account proof;
- privacy policy;
- terms of use;
- vendor agreements;
- employment agreements;
- contractor agreements;
- data privacy program;
- cybersecurity documentation;
- financial statements;
- board resolutions;
- intercompany agreements;
- licenses for regulated activities.
LXXXVI. Step-by-Step: Forming the Holding Company Structure
Step 1: Define the business model
Identify what the app does:
- SaaS;
- marketplace;
- e-commerce;
- social platform;
- fintech;
- health;
- education;
- gaming;
- logistics;
- content;
- subscription;
- advertising;
- enterprise software.
The business model determines legal requirements.
Step 2: Identify assets and risks
List:
- brand assets;
- IP assets;
- user data;
- contracts;
- revenue streams;
- regulated activities;
- operational risks;
- possible liabilities.
Step 3: Choose structure
Decide whether to use:
- single corporation;
- holding company plus operating company;
- IP company plus operating company;
- foreign parent plus Philippine subsidiary;
- one person corporation;
- multiple subsidiaries.
Step 4: Confirm foreign ownership rules
Before incorporating, confirm whether foreign shareholders are allowed for the chosen business activities.
Step 5: Draft corporate purposes
Prepare purpose clauses appropriate for holding, IP ownership, software, and operations.
Step 6: Incorporate with SEC
File articles, bylaws, and required documents.
Step 7: Register with BIR and LGU
Complete tax and local registration.
Step 8: Open bank accounts
Use separate bank accounts for each entity.
Step 9: Assign founder IP
Transfer pre-incorporation assets to the holding company or operating company.
Step 10: Register trademarks
File brand names, logos, and app names with IPOPHL.
Step 11: Sign developer and contractor assignments
Ensure all contributors assign rights to the proper company.
Step 12: Create intercompany agreements
If there is a holding and operating company, sign:
- IP license;
- management services agreement;
- cost-sharing agreement;
- data processing agreement, if needed;
- loan or funding agreements, if any.
Step 13: Prepare user-facing legal documents
Draft:
- terms of use;
- privacy policy;
- refund policy;
- seller terms;
- subscription terms;
- community guidelines;
- data processing terms;
- cookie policy, if applicable.
Step 14: Set up compliance systems
Implement:
- accounting;
- tax calendar;
- corporate secretary records;
- data privacy program;
- cybersecurity policies;
- HR contracts;
- vendor review;
- legal approvals for regulated features.
Step 15: Prepare for investment
Clean up:
- cap table;
- IP chain of title;
- financial records;
- licenses;
- contracts;
- founder vesting;
- data room.
LXXXVII. What Should the Holding Company Own?
A typical holding company may own:
- shares of operating company;
- main trademarks;
- app name;
- logos;
- domain names;
- source code;
- platform architecture;
- copyrights;
- patents or utility models;
- business manuals;
- brand guidelines;
- strategic contracts;
- investment assets.
But there may be reasons to let the operating company own some assets, especially if simplicity matters. Tax and operational consequences should be reviewed.
LXXXVIII. What Should the Operating Company Own?
The operating company may own:
- customer contracts;
- local permits;
- employment contracts;
- vendor contracts;
- operational equipment;
- user support systems;
- receivables;
- working capital;
- local tax registrations;
- app operational accounts;
- licenses needed to operate.
It may use IP under license from the holding company.
LXXXIX. Data Ownership Between Holding and Operating Company
Data is not “owned” in the same simple way as physical property because personal data is regulated. The group should define:
- who is personal information controller;
- who is processor;
- who can access user data;
- whether data can be shared with holding company;
- whether data can be used for analytics;
- whether data can be transferred abroad;
- retention and deletion rules;
- data breach responsibilities.
The operating company usually controls user relationships, but the holding company may need limited access for analytics, strategy, or group management.
XC. Assignment of Contracts
If the business started before incorporation, founders may have signed contracts personally.
These should be assigned or novated to the proper company where possible.
Examples:
- developer contracts;
- domain registration;
- hosting;
- app store accounts;
- payment gateway;
- vendor contracts;
- customer contracts;
- advertising accounts;
- software subscriptions.
Some contracts cannot be assigned without consent.
XCI. Pre-Incorporation Contracts
If founders signed contracts before incorporation, the company does not automatically become a party after incorporation. Ratification, assignment, or novation may be needed.
The contract should be reviewed to ensure the company has the rights and obligations intended.
XCII. App Revenue and Invoicing
The operating company that provides services should generally issue invoices or receipts and recognize revenue.
If the holding company receives royalties, it should invoice the operating company properly.
Payment flows should match the contracts.
Avoid collecting app revenue into personal accounts.
XCIII. App Store Revenue
App store payouts should go to the proper company bank account.
Check:
- developer account legal name;
- tax forms;
- payout bank;
- app ownership;
- app store agreement;
- in-app purchase rules;
- withholding taxes;
- revenue recognition.
If app store revenue goes to a founder personally, this creates tax and ownership issues.
XCIV. Advertising Revenue
If the app earns ad revenue from networks, the account should be in the company’s name if possible.
Check:
- ad network terms;
- tax forms;
- payout account;
- user consent for ad tracking;
- privacy policy;
- children’s data restrictions;
- foreign withholding tax;
- invoicing.
XCV. Subscription Revenue
Subscription apps should disclose:
- price;
- billing cycle;
- free trial terms;
- renewal;
- cancellation;
- refund policy;
- auto-renewal;
- account deletion;
- service limitations.
Consumer complaints often arise from unclear recurring billing.
XCVI. Marketplace Revenue
Marketplace revenue may include:
- commission;
- platform fee;
- listing fee;
- advertising fee;
- subscription fee;
- payment processing fee;
- logistics fee.
The platform must clearly disclose fees to sellers and buyers.
XCVII. Protecting Against Copycats
To protect against copycats:
- register trademarks early;
- document first use;
- register copyright where useful;
- control source code;
- use NDAs;
- monitor competitors;
- send demand letters;
- file takedown notices;
- enforce app store complaints;
- secure domains and handles;
- maintain brand guidelines.
Ideas alone are hard to protect. Execution, code, brand, data, contracts, and trade secrets are more protectable.
XCVIII. Cease-and-Desist Letters
A cease-and-desist letter may be sent to infringers using similar marks, copied content, stolen code, fake pages, or counterfeit apps.
It should include:
- sender’s rights;
- infringing acts;
- demand to stop;
- demand for takedown;
- demand for accounting or damages, if appropriate;
- deadline;
- reservation of rights.
Do not send aggressive threats without legal basis, as this may backfire.
XCIX. App Takedown Requests
Takedown requests may be filed with app stores, hosting providers, social media platforms, marketplaces, or domain registrars.
Evidence may include:
- trademark registration;
- copyright ownership;
- screenshots;
- app links;
- infringing content;
- proof of confusion;
- company authorization.
C. Handling Customer Complaints
The operating company should have a complaint process.
Include:
- support email;
- response timelines;
- escalation;
- refund review;
- account issues;
- data privacy requests;
- dispute resolution;
- consumer complaint handling.
Good complaint handling reduces regulatory and reputational risk.
CI. Recordkeeping
Keep records of:
- user terms acceptance;
- privacy consents;
- transaction history;
- payments;
- refunds;
- complaints;
- security incidents;
- data requests;
- vendor contracts;
- employment records;
- tax filings;
- board approvals.
Records are essential in disputes.
CII. Corporate Compliance Calendar
A holding company and operating company should track:
- annual SEC reportorial filings;
- general information sheet;
- financial statements;
- beneficial ownership updates;
- business permit renewal;
- BIR filings;
- tax payments;
- books of accounts;
- payroll filings;
- SSS, PhilHealth, Pag-IBIG remittances;
- trademark deadlines;
- domain renewal;
- data privacy registration or renewal where applicable;
- permits and licenses;
- board meetings.
Compliance failures can affect fundraising and operations.
CIII. Dissolution, Exit, and Sale
Eventually, founders may:
- sell the app;
- sell the brand;
- sell the operating company;
- merge with another company;
- license the platform abroad;
- shut down operations;
- dissolve subsidiaries;
- buy out a founder.
A holding structure can help, but exit documents must address:
- IP transfer;
- employee transfer;
- user data transfer;
- tax;
- regulatory approvals;
- creditor consent;
- user notification;
- assignment of contracts;
- warranties;
- indemnities;
- escrow;
- post-closing support.
CIV. Common Mistakes
Common mistakes include:
- using a sole proprietorship too long;
- failing to register trademarks;
- assuming SEC name protects the brand;
- letting a freelancer own the source code;
- publishing app under a developer’s personal account;
- no founders’ agreement;
- no vesting;
- no shareholders’ agreement;
- mixing personal and company funds;
- no privacy policy;
- copying terms from another app;
- collecting excessive user data;
- ignoring foreign ownership restrictions;
- operating regulated features without license;
- no written intercompany license;
- using holding company and operating company interchangeably;
- accepting investment without securities compliance;
- failing to file taxes and SEC reports;
- not documenting board approvals.
CV. Practical Checklist for a Brand and App Holding Structure
Corporate
- SEC incorporation of holding company;
- SEC incorporation of operating company, if separate;
- articles and bylaws with proper purposes;
- founder share subscriptions;
- shareholders’ agreement;
- founders’ agreement;
- board resolutions;
- corporate records;
- BIR registration;
- business permits;
- bank accounts.
Intellectual Property
- trademark clearance;
- trademark applications;
- founder IP assignment;
- developer IP assignment;
- employee IP clauses;
- copyright registration where useful;
- domain transfer;
- app store account control;
- social media account control;
- brand guidelines.
Contracts
- IP license between holding and operating company;
- management services agreement;
- employment agreements;
- contractor agreements;
- vendor agreements;
- terms of use;
- privacy policy;
- data processing agreements;
- customer agreements;
- investor documents.
Compliance
- data privacy program;
- cybersecurity policies;
- tax calendar;
- labor registration;
- consumer complaint process;
- regulated activity licensing;
- corporate filings;
- accounting system;
- incident response plan.
Investment Readiness
- clean cap table;
- vesting documents;
- IP chain of title;
- financial records;
- due diligence folder;
- permits and licenses;
- tax compliance;
- privacy and security documentation;
- material contracts.
CVI. Sample Holding Company Structure
A basic structure may look like this:
Founders and Investors ↓ BrandTech Holdings Corporation
- owns trademarks;
- owns source code;
- owns domains;
- owns shares in operating company;
- licenses IP.
↓ BrandTech App Corporation
- operates app;
- contracts with users;
- hires employees;
- receives customer revenue;
- pays royalties to holding company;
- handles customer support and compliance.
This structure is simple enough for a startup but flexible enough for future growth.
CVII. Sample Intercompany Arrangement
The holding company and operating company may sign:
Trademark and Software License Agreement
- operating company may use brand and app;
- holding company retains ownership;
- royalties payable;
- quality control required.
Management Services Agreement
- holding company provides strategic, finance, legal, HR, or management support;
- operating company pays service fee.
Data Processing or Data Sharing Agreement
- if personal data flows between entities;
- defines controller and processor responsibilities.
Cost-Sharing Agreement
- if both companies share expenses;
- allocates costs fairly.
These contracts should reflect real activities.
CVIII. Sample Founder IP Assignment Clause
The Founder hereby assigns, transfers, and conveys to the Company all rights, title, and interest in and to all intellectual property, works, inventions, developments, designs, source code, object code, documentation, business concepts, trademarks, logos, domain names, social media accounts, content, databases, trade secrets, and other materials created, developed, conceived, authored, acquired, or used by the Founder in connection with the Company’s business, whether before or after incorporation, including all related goodwill and rights to sue for past, present, and future infringement.
The Founder shall execute all documents and perform all acts reasonably necessary to perfect, register, enforce, or evidence the Company’s ownership of the assigned intellectual property.
CIX. Sample Developer IP Assignment Clause
All deliverables, source code, object code, documentation, designs, works, inventions, improvements, modifications, discoveries, processes, databases, graphics, user interface materials, and other outputs created by the Developer under this Agreement shall be deemed specially commissioned for the Company and shall be exclusively owned by the Company upon creation or, where assignment is required, are hereby irrevocably assigned to the Company.
The Developer waives, to the extent allowed by law, any claim inconsistent with the Company’s ownership and shall execute further documents necessary to confirm, register, or enforce such ownership. The Developer represents that the deliverables are original or properly licensed and do not infringe third-party rights.
CX. Sample Trademark License Clause Between Holding and Operating Company
The Licensor grants to the Licensee a non-transferable, [exclusive/non-exclusive] license to use the trademarks, trade names, logos, app names, domain names, and brand assets listed in Schedule A solely in connection with the operation, marketing, and commercialization of the approved app and related services in the territory of [territory].
All goodwill arising from use of the licensed marks shall inure exclusively to the benefit of the Licensor. The Licensee shall comply with the Licensor’s brand guidelines and quality standards. The Licensee shall not register, challenge, imitate, or use confusingly similar marks without the Licensor’s written consent.
CXI. Sample Data Protection Clause for Vendors
The Vendor shall process personal data only upon documented instructions of the Company and solely for purposes necessary to perform the services. The Vendor shall implement appropriate organizational, physical, and technical security measures to protect personal data against unauthorized access, loss, alteration, disclosure, or destruction.
The Vendor shall not disclose, sell, transfer, or use personal data for its own purposes. The Vendor shall promptly notify the Company of any actual or suspected security incident or personal data breach and shall cooperate in investigation, mitigation, notification, and remediation.
CXII. Final Practical Sequence
For a founder building a Philippine brand and app business, the practical order is:
- clear the brand name;
- choose corporate structure;
- incorporate holding company and operating company if needed;
- register with BIR and LGU;
- open bank accounts;
- assign founder IP to the proper company;
- sign developer and contractor IP assignments;
- file trademarks;
- secure domains, app store accounts, and repositories;
- draft terms of use and privacy policy;
- implement data privacy and cybersecurity program;
- sign intercompany license agreements;
- document founder equity and vesting;
- prepare accounting and tax systems;
- check special licenses for regulated features;
- launch with compliance records in place;
- maintain corporate filings and tax compliance;
- build an investor due diligence folder early.
CXIII. Conclusion
A holding company can be an effective structure for protecting a brand and app business in the Philippines. It allows founders to centralize ownership of trademarks, software, domains, source code, and strategic assets while placing day-to-day operations in a separate operating company. This can improve asset protection, investor readiness, licensing flexibility, expansion planning, and exit options.
However, a holding company is not a magic shield. It works only if the entities are properly incorporated, separately maintained, adequately documented, and commercially justified. The group must have clear IP assignments, trademark filings, developer contracts, data privacy compliance, tax documentation, intercompany agreements, corporate approvals, and operating permits.
For a brand and app business, the most important legal rule is ownership clarity. The company that claims to own the brand and app must actually own them. Founders, developers, contractors, designers, agencies, and employees must assign rights properly. The brand must be protected as a trademark. The app must have lawful user terms, privacy documentation, cybersecurity controls, and regulatory compliance if it touches financial, health, marketplace, advertising, or other regulated activities.
The safest structure is one that matches the real business: a properly capitalized holding company that owns and protects the core brand and IP, a compliant operating company that deals with users and revenue, and a complete set of contracts and records showing how the group functions. Done correctly, this structure can protect the business, attract investors, reduce disputes, and preserve the long-term value of the brand and app.