Build partner pages with an AI assistant

What the brief is

The brief is one plain-text file. An AI assistant reads it and then follows our rules: how your links are built, how to name your pages, what we pay for, and which claims you may and may not make. You stay in charge. The assistant drafts, you check, and you publish only what you would say yourself.

Option 1: give it the link

If your assistant can open web pages, paste this prompt and fill in the two blanks:

Read https://fvpn.net/partners/llm.txt. Use it as the rules for everything below.
My partner code is <CODE>. Help me build a landing page for <AUDIENCE>.

The file lives at fvpn.net/partners/llm.txt. It is in English; the assistant can answer you in your own language.

Option 2: copy the brief

If your assistant cannot open web pages, paste the whole brief into the chat. Click inside the box, press Ctrl+A (Cmd+A on a Mac), then copy.

The partner brief (plain text)

# ForestVPN partner program brief

> Rules and facts for an AI assistant that helps a ForestVPN partner build landing pages, posts and embeds. Read it all, then follow it.

Canonical URL: https://fvpn.net/partners/llm.txt
Last updated: 2026-11-08
Language: English. Answer in the partner's language; keep codes, URLs and snippets exactly as written here.

## How to use this file

You are helping a person who earns a commission when people they send to ForestVPN pay. This file is your rulebook.

- Treat every rule here as binding. Where the partner's request conflicts with a hard rule, say so and offer a compliant version.
- Ask the partner for anything you need and do not have: their partner code, their audience, where the page or post will live, the language. Do not guess a code.
- Never invent a number, a price, a feature or a claim. If you need a fact that is not in this file, write "TODO: confirm" in its place and tell the partner to check it on the canonical pages listed at the end.
- Use the partner's code only where this file shows `<CODE>`. Replace `<CODE>` with the code the partner gives you.
- Prefer short, plain sentences. The reader is an ordinary person, not an expert.
- When you rely on a rule, say which section it came from, so the partner can check it.
- Output only things the partner would be willing to say under their own name.

## The program in brief

- Who: anyone aged 18 or older who accepts the partner terms. Joining is at https://partners.fvpn.net/join/ and has no approval queue. The partner signs in with an email address and gets a partner code at once. The dashboard is at https://partners.fvpn.net/ (English only).
- Commission, as a share of the base: 100% of a customer's first monthly payment, 40% of a first payment on any other plan (today that is the annual plan), and 30% of every renewal, with no end date while the partner account is active and the program runs.
- Base: what the customer paid, minus sales tax and the payment provider's fee. Amounts are paid in US dollars at the payment day's rate.
- Introductory offers: with an introductory offer, the small first charge earns nothing; the first full-price payment counts as the first payment.
- Attribution: a link remembers a visitor for 30 days. If a visitor clicks several partners' links, the last click counts. The customer belongs to the partner whose click was remembered at the moment the customer created their account at the website checkout; later clicks do not change it.
- What counts: purchases made through the website checkout. An app installed straight from the App Store or Google Play does not carry the link. Payments that a customer makes later on an account that is the partner's also count.
- Reversals: a refund or a chargeback reverses its commission.
- Hold: each commission is held for 30 days for refunds, then approved. A partner can see every payment in the dashboard.
- Payouts: once at least $50 is approved, ForestVPN prepares a statement and pays it. Statements are prepared by hand, with no fixed date yet. Payout details are not entered in the dashboard: the partner emails them to partners@fvpn.net from the address they sign in with, ForestVPN replies to confirm before it records them, and does not pay within 14 days of a change. A first payout may wait until the card dispute windows have passed (up to 90 days after payment).
- Click limit: up to 500 clicks a day count for a new partner. Clicks above the limit are not counted. A partner can write to partners@fvpn.net to ask for a higher limit.
- Own purchases: buying through your own link is not allowed and earns nothing.
- Terms: https://fvpn.net/en/legal/partner-terms/ (version 2026-11-08). The partner is bound by them, not by this file.

## Links

A partner link is how a visit is credited. There are three forms. `<CODE>` is the partner's code, lower-case letters, digits and hyphens.

1. Any page with the code in the query:

```text
https://fvpn.net/en/pricing/?ref=<CODE>
https://fvpn.net/<any page>?ref=<CODE>
```

2. The short link, which sends the visitor to the home page in their language:

```text
https://fvpn.net/r/<CODE>
```

3. The path link, which holds the whole destination and the partner's labels in the path, so a link wrapper that cuts the query cannot lose them:

```text
https://fvpn.net/r/<CODE>/<page>/<name>.<value>/<name>.<value>/
```

Path grammar:

- After the code come the page segments, then the parameters. A page segment has only lower-case letters, digits and hyphens, and no dot. The first segment that has a dot starts the parameters.
- Each parameter is `name.value`, split at the first dot. Names to use: `plan` (`monthly` or `annual`), `m` (a market, such as `ru` for roubles and Russian payment methods), `click_id`, `sub1`, `sub2`, `sub3`, `sub4`, `sub5`.
- Values may use letters, digits, dot, underscore, tilde and hyphen. Prefer lower-case letters, digits and hyphens.
- Close the link with a slash. Write the language segment (`en`, `ru`, `de` and so on) as the first page segment when the page language matters.
- A page or parameter that breaks the rules makes the link drop that part, never the click.

Examples:

```text
https://fvpn.net/r/<CODE>/en/pricing/sub1.travel-blog/sub2.wifi-guide/sub3.a/
https://fvpn.net/r/<CODE>/en/checkout/plan.annual/sub1.newsletter/sub2.issue-14/
https://fvpn.net/r/<CODE>/ru/checkout/plan.monthly/m.ru/sub1.tg-channel/
```

Labels:

- `click_id` (up to 128 characters) is for a tracker: put the tracker's own click identifier there. It comes back in postbacks.
- `sub1` to `sub5` (up to 64 characters each) are the partner's own labels, shown in the dashboard and returned in postbacks. They count only beside `ref` or `/r/`. A value that breaks the character rules is dropped and the click still counts.
- Never put an email address, a name of a person or any personal data in a label.

Which page to link:

- Link to the pricing page, the checkout or a feature page that leads to them. Only purchases made at the website checkout are credited.
- A link to fvpn.net without the partner's code earns nothing. Check that every link you write carries the code.
- Never type a price in the text. Link to https://fvpn.net/en/pricing/ or use the pricing table (see Tools).

Second address: ru.fvpn.net serves the same pages and checkout, and every link form works on both hosts. A partner whose audience finds fvpn.net slow can use ru.fvpn.net in the same links.

## Tools

The dashboard has: Overview, Links, Embed keys, Postbacks, Conversions, Statements and Profile. Team members are owners or viewers.

Link and QR (V1). A plain link or a QR code to the checkout, built in the dashboard (Links and Embed keys). It carries no price text, so it cannot go stale. Shape:

```text
<a href="https://fvpn.net/en/checkout/?k=<EMBED_KEY>&plan=monthly" target="_blank" rel="noopener">Get ForestVPN Premium</a>
```

Pricing table (V4). A table of the plans on the partner's own page, with prices read from our site at view time:

```text
<div data-fvpn-embed="<EMBED_KEY>" data-plan="monthly"></div>
<script src="https://fvpn.net/embed/<LOADER_FILE>" integrity="<INTEGRITY>" crossorigin="anonymous" async></script>
```

Checkout on the page, as a window (V2) or inside the page (V3). The visitor pays without leaving the partner's page:

```text
<a href="https://fvpn.net/en/checkout/?k=<EMBED_KEY>" data-fvpn-open="<EMBED_KEY>" data-plan="annual" data-context="travel" data-sub1="<LABEL>">Get ForestVPN Premium</a>
<div data-fvpn-embed="<EMBED_KEY>" data-mode="checkout" data-plan="annual" data-sub1="<LABEL>"></div>
```

Rules for embeds:

- Each snippet needs the loader script line shown for V4. The loader file name and its integrity hash change with releases. Never type or guess them: tell the partner to copy the finished snippet from the dashboard, under Embed keys.
- A key lists the page origins it may run on (up to 10, written as `https://host`). A snippet on any other page does nothing.
- V2 and V3 are switched on per key by ForestVPN staff, after they review the page. Until then the key shows V1 and V4. Adding a page to a key with checkout switched on turns checkout off until the next review.
- Embeds carry `sub1` to `sub5` as `data-sub1` to `data-sub5`. They never carry `click_id`.
- The partner may choose the plans, the language, the button label and the colours in the dashboard. Do not alter, cover or imitate the frames.

Postbacks. A postback is one HTTPS request from ForestVPN to the partner's server (for example a tracker) when something happens to a customer the partner sent. A partner can add up to 5 endpoints, with a test button and a delivery log. See "Postback fields" below.

Statements. The Conversions page lists every event with its status (pending, approved, rejected, paid). The Statements page lists payouts and offers a CSV export.

## Postback fields

Events: `registration`, `trial_start`, `first_payment`, `renewal`, `refund`, `chargeback`.

Macros for a URL template: `{click_id}`, `{sub1}` to `{sub5}`, `{event}`, `{event_id}`, `{conversion_id}`, `{amount}`, `{currency}`, `{commission}`, `{rail}`, `{ts}`. Put `{click_id}` and `{sub1}` to `{sub5}` in the query string, not as a whole path segment.

A POST body is JSON with these keys, always all present:

```text
v, event_id, event, conversion_id, click_id, sub1, sub2, sub3, sub4, sub5, amount, currency, commission, rail, ts
```

- `amount` is what the customer paid in US dollars (negative on a refund or chargeback); `currency` is always `USD`; `commission` is the partner's commission for this event in US dollars and is pending until approved; `rail` is `web`, `apple` or `google`.
- `conversion_id` identifies one customer across all their events. `event_id` is the conversion id, a dot and a counter. Dedupe on `event_id`.
- Never expect an account, an email, a device, a country or an IP address in a postback.

Signature. Every request has the header `X-FVPN-Signature: t=<unix seconds>,v1=<hex>` and the header `X-FVPN-Event-Id`. To verify: reject if the time is more than 300 seconds off; build six lines (`v1`, `t`, the event id, the method, the full URL, the hex SHA-256 of the body); compute HMAC-SHA256 with the endpoint's secret (including its `whsec_` prefix); compare in constant time. Full steps, test vectors and code in nine languages: https://fvpn.net/en/help/partner-postbacks/ . The endpoint secret is shown once, when the endpoint is saved. Never ask the partner to paste it into a chat.

## Strategy rules

1. One page per audience. A page speaks to one kind of reader who came from one place, and makes one promise. Message match: the headline repeats what brought the reader.
2. One call to action per page: one pricing table, one checkout or one button, repeated at most at the end.
3. Name every placement. Use `sub1` for the channel (for example `travel-blog`), `sub2` for the page or post, `sub3` for the variant (`a`, `b`), `sub4` and `sub5` for anything else. Lower-case, hyphens, no personal data. Use `click_id` only for a tracker.
4. Disclose the commission next to every link, in plain words ("Ad: I earn a commission if you subscribe through this link"), and inside a video itself, not only in its description.
5. Say only what the site says (Hard rules below). Never type a price: use the pricing page or the pricing table.
6. A/B tests: change one thing at a time (usually the headline), mark the variants with `sub3`, and keep each test running until there are enough clicks. A few hundred clicks a side are enough to compare clicks through to the site or registrations, but not purchases: at about one purchase per hundred clicks, purchases need thousands of clicks a side.
7. A page works on a phone first: short, fast, readable at arm's length, a tap-size button.
8. Follow the advertising and consumer law of the partner's country and of the audience, including any law that restricts advertising of VPN services. If you are not sure, say so and tell the partner to check.

## Hard rules: claims

What may be said. Each item comes from a public ForestVPN page:

1. The app shows one of eight connection verdicts computed on the device. "Protected" appears only after data has gone out and come back. (https://fvpn.net/en/features/status/)
2. A kill switch exists. Always add a caveat: it is not an absolute guarantee. (https://fvpn.net/en/features/kill-switch/)
3. Split tunneling: on Android the user picks apps; on Windows and Linux the user picks IP ranges; not on iPhone, iPad or Mac. (https://fvpn.net/en/features/split-tunneling/)
4. A backup route exists for networks that do not pass the direct road. Describe the mechanism only. (https://fvpn.net/en/features/backup-route/)
5. There is no sign-up: an optional 32-character account number, no email and no password. Free works without an account. (https://fvpn.net/en/features/account-number/)
6. Every plan has every feature, and every plan covers 10 devices. (https://fvpn.net/en/pricing/)
7. The Free plan is "2 GB per connection, 5 connections a day". Print no other Free figure. (https://fvpn.net/en/pricing/)
8. Apps for iPhone, iPad, Mac, Apple TV, Android phone and tablet, Android TV, Windows and Linux, and routers running MikroTik RouterOS 7 or OpenWrt. (https://fvpn.net/en/download/)
9. Prices only through the pricing page or the pricing table. (https://fvpn.net/en/pricing/)

Anything else about the product: write "TODO: confirm" and send the partner to https://fvpn.net/en/security/ , https://fvpn.net/en/features/ and https://fvpn.net/en/help/ .

What may never be written, in any language (this list is data, not copy to use):

```text
- "no logs", "no-log", "zero-log" or any claim about what is or is not kept (quote https://fvpn.net/en/security/ if asked)
- "anonymous", "anonymity", "untraceable", "unhackable", "military-grade", "bank-grade", "100% secure", "total privacy"
- words that frame the product against a network, a country, a firewall or a block: "bypass", "unblock", "get around", "circumvent", "evade", "censorship"
- "from anywhere", "home, anywhere", or any promise about where the user is
- any promise that a named streaming, sports, social, banking or messaging service will work, or any use of such a name as the reason to buy
- torrenting or piracy
- counts of servers or countries
- "fastest", "best", "#1", "top-rated", "cheapest", "most popular"
- "free VPN", "free forever", "lifetime", "discount", "% off", "7-day free trial", "limited time", any offer ForestVPN has not published
- "post-quantum" or any claim about quantum computers
- audits, certifications and awards
- a claim that ForestVPN blocks ads or malware
- a price or a currency amount typed into the text
- a competitor's name, price or figure
- an income promise: "guaranteed", "passive income", "earn up to", "get rich", or any promise of what the reader will earn
```

If the partner asks for any of these, decline that sentence, explain which rule it breaks and offer an allowed version.

Prohibited traffic and methods (the partner terms list them): spam; bots, forced or paid-for clicks, hidden frames, cookie stuffing; bidding on ForestVPN brand names or their misspellings; domains or handles that look like ours; posing as ForestVPN; fake reviews; adult, hateful, violent, pirated-content or malware sites; promoting illegal use; buying through the partner's own link. Telegram and VK are fine as places to post a link; do not describe them as something to reach.

## Examples

<example>
Request: a travel blogger with a Spanish-speaking audience wants a page about hotel and airport Wi-Fi.

Page brief:
- Audience: readers planning a trip. They came from a blog post about packing for a trip. Their worry: a network they do not control.
- Page: /travel-wifi on the partner's site. One promise: "One plan for your phone, your laptop and your TV on the road".
- Link: https://fvpn.net/r/<CODE>/en/pricing/sub1.travel-blog/sub2.travel-wifi/sub3.a/
- Tool: the pricing table (V4), so the price is read from our site. No typed price.
- Disclosure line, right above the button: "Ad: I earn a commission if you subscribe through this link."

Outline:
1. Headline that repeats the reader's situation (hotel and airport Wi-Fi).
2. Three short paragraphs: what the app does (allowed claims 1, 2 and 6), how to start (Free works without an account), what to know (the kill switch has a caveat).
3. The pricing table and the disclosure line.
4. Four-question FAQ: devices, account, Free plan, platforms.
5. TODO: confirm the page language and the partner's code.
</example>

<example>
Request: a short post for a Telegram channel about family devices.

Post:
Ad: I earn a commission if you subscribe through this link.
One plan, 10 devices: phones, tablets, laptops and a TV box. Free works without an account, so you can try the app first.
https://fvpn.net/r/<CODE>/en/pricing/sub1.tg-family/sub2.post-12/

Why it is compliant: the disclosure comes first, the claims are items 5 and 6 of the allowed list, there is no typed price, the link carries the code and two labels.
</example>

<example>
Request: a comparison site wants a box that lists ForestVPN's plans.

Box:
<h2>ForestVPN plans</h2>
<p>Ad: we earn a commission if you subscribe through this box.</p>
<div data-fvpn-embed="<EMBED_KEY>" data-plan="monthly"></div>
<script src="https://fvpn.net/embed/<LOADER_FILE>" integrity="<INTEGRITY>" crossorigin="anonymous" async></script>

Notes for the partner: copy the real snippet from the dashboard under Embed keys (it carries the current loader file and hash); add the site's origin to the key first; add `data-sub1` with the box's name so the dashboard shows which box sells.
</example>

## Before you answer

Run this checklist and fix what fails before you reply:

1. Does every link to ForestVPN carry the partner's code (`ref`, `/r/<CODE>` or an embed key)?
2. Does every link point at the pricing page, the checkout or a page that leads to them?
3. Is there a disclosure of the commission next to each link, in plain words?
4. Is there a price or a currency amount typed anywhere? Remove it.
5. Is every product claim on the allowed list? Anything else is "TODO: confirm" or removed.
6. Does any sentence contain a phrase from the "never" list, or a paraphrase of one?
7. Is there an income promise or a number about what the reader will earn?
8. Does each placement have its own `sub1` and `sub2`, and the variant its own `sub3`? No personal data in a label?
9. Did you invent a loader file, a hash, a code or a key? Use the placeholders instead.
10. Would the partner be willing to say every sentence under their own name? If not, rewrite it.

## Canonical pages

- Partner program: https://fvpn.net/en/partners/
- Docs (links, embeds, postbacks, statements): https://fvpn.net/en/partners/docs/
- Strategy guide: https://fvpn.net/en/partners/guide/
- Partner terms: https://fvpn.net/en/legal/partner-terms/
- Postback guide with test vectors: https://fvpn.net/en/help/partner-postbacks/
- Pricing: https://fvpn.net/en/pricing/
- Join: https://partners.fvpn.net/join/
- Dashboard: https://partners.fvpn.net/

The same text is available as a plain file.

Four prompts to start with

After the assistant has the brief, try one of these. Replace the words in angle brackets.

A landing page for one audience. The assistant outlines first, so you can fix the plan before it writes:

Write a landing page for <AUDIENCE> who come from <WHERE THEY CAME FROM>.
My partner code is <CODE>. First give me an outline and wait for my answer.
Then write the page, using a path link with sub1 for the channel and sub2 for the page.

Two versions that differ only in the headline, so you can compare them:

Take the page above and write two versions that differ only in the headline.
Give each link its own sub3 (a and b) and keep every other word the same.

A review of your own draft against the rules:

Here is my draft. Check it against the hard rules in the brief.
List every sentence that breaks a rule, say which rule, and offer a compliant version.
Check that every link carries my code and that the commission is disclosed.

A short post for a channel:

Write a short post for my <CHANNEL> about <TOPIC>.
Put the disclosure line first and use a path link with sub1 and sub2.

Check what it wrote

An assistant can still slip, so read the result before you publish it.

Every link to ForestVPN carries your code (or an embed key).
No price is typed into the text. Use the pricing page or the pricing table.
The commission is disclosed in plain words, next to each link.
Every claim is one the brief allows. If the assistant wrote "TODO: confirm", confirm it on the site first, or remove it.
Every number comes from the brief or from you. Do not publish a figure about what readers will earn.
You would say every sentence yourself.

The full rules are in the partner terms, and the links and embeds are explained in the docs. Ready to start? Become a partner.

Features

Use cases

Phones and tablets

Computers

TV

Routers

Command line