Your information
Privacy notice
Updated 17 September 2026
1. Who this notice covers
Partner Passport lets businesses maintain publisher profiles that other businesses and affiliate networks can read through public pages and an API. This notice describes the current service, including registration, email verification and profile publication.
Service operator: Partner Passport. For privacy questions or requests, email contact@partnerpassport.io.
2. Information we process
Network directory submissions store the network name, website and contact email. The name, website and generated network code are listed publicly immediately and made available for partner profile setup. The contact email is kept private for administering the listing. Network submissions do not verify ownership or imply endorsement. Contact us to request a correction or removal.
Account information includes your email address, email-verification status and the partners you can manage. Partner records include the business name, domain, verification status and generated PassportNumber. We also store the profile details you enter: website, description, markets, sectors, promotion methods, network IDs, audience figures, audience selections and a partnerships contact.
Authentication uses emailed codes rather than passwords. The application stores a keyed hash of the current code, expiry times and attempt counters. Technical service logs can contain diagnostic information generated while operating the app.
3. What becomes public
Once a partner is verified, its business profile is available without a login through its public page and JSON API. This includes the partnerships contact you enter, network identifiers and audience information. Saved profile changes are available on subsequent public reads; there is no separate publish button.
Login email addresses, account memberships and authentication records are not included in the public profile. If you enter your login email as the partnerships contact, that address will be public in that role. Only provide information you are authorised to publish. Do not upload individual audience-member details or confidential information.
Public information can be copied by visitors, networks and other API users worldwide. Updating or removing it here does not automatically remove copies held elsewhere.
4. Why we use information
We use account and verification information to sign you in and control profile editing. Business and profile information provides the public publisher directory and network lookups. Attempt counters and diagnostics help prevent misuse and investigate faults.
For operator review: the proposed lawful bases are contract where processing is necessary to provide a requested service to the individual, and legitimate interests in business-profile discovery, account administration and service security where appropriate. The operator must confirm the applicable bases and balancing assessments. Publication must not be treated as blanket consent to unrelated marketing.
5. Cookies and email
Sign-in uses authentication and security cookies. Sessions currently expire 24 hours after code verification; signing out clears the browser session. Verification codes expire after 10 minutes. Expiry is not the same as deletion of a stored record. Blocking required cookies can prevent sign-in.
A dashboard preference cookie remembers your selected publisher for up to 30 days. It does not grant access; we check your signed-in account’s publisher permissions whenever you open the dashboard.
Amazon SES sends verification emails. The current application does not include advertising trackers or analytics scripts.
6. Providers and where information is handled
The service uses Amazon Web Services for application hosting, PostgreSQL storage, logs and email delivery. The infrastructure is configured in the Ireland region. This does not mean every provider operation or copy of public information is limited to Ireland.
If you choose Generate next to your profile description, we send your public website URL to OpenAI without query parameters or fragments. OpenAI retrieves public website content to suggest a short business description. We do not send your login email, contact fields or full profile form for this feature. Review the suggestion before selecting Save changes; generating alone does not save it to your profile.
If you choose Extract and pre-fill, we send your selected files, including their contents, and your publisher name and domain to OpenAI to identify supported profile information. Only upload files you are authorised to share. We do not retain the uploaded files in our database or object storage. Extracted values and source excerpts are returned to your browser for review; only profile values you save are published.
We request that these AI responses are not stored through the API, but this does not mean the provider has no operational or abuse-monitoring retention. Provider access, retention and any international-transfer safeguards must be confirmed by the operator in the final notice. Public API users may process their copies independently.
7. Retention and security
Account and profile records currently have no automatic expiry. Removal requires manual administration. Application log retention is configured to 60 days. Backups and retained snapshots can outlast removal from the active database.
The operator must confirm a retention and deletion schedule based on service needs, security, applicable obligations and backup handling. HTTPS, restricted database networking and authentication controls help protect the service, but no system can guarantee complete security.
8. Your choices and rights
You can update editable business-profile information in the dashboard. Depending on the applicable law and circumstances, you may request access, correction, erasure, restriction or portability of personal information.
Where processing relies on legitimate interests, you may object to that processing. Where consent is used, it may be withdrawn. These rights are subject to applicable conditions; they do not always require all information to be deleted.
Send requests to contact@partnerpassport.io. We may need to verify your identity before acting on a request. Where UK data-protection law applies, you can also complain to the Information Commissioner’s Office; elsewhere, contact the relevant supervisory authority.
9. Changes
We will update this notice when the service’s processing changes. The date above identifies this version. See the terms of use and public API documentation for how the service works.
