Privacy & GDPR Notice
Last updated: 9 June 2026. This notice explains how MagnetAPI.org handles personal data for the public website, client dashboard, admin dashboard, API gateway, wallet ledger, setup instructions, support, and transactional email.
Controller and contact
MagnetAPI.org is operated by Open ISP cc, Registration Number: 2005/156968/23, based in South Africa. Privacy, account, access, correction, deletion, and portability requests can be sent to support@magnetapi.org. We may ask for information needed to verify the requester before making account changes or releasing account data.
Personal data processed
- Account identifiers: username, email address, optional phone number, first name, surname, address, city, region, country, dashboard password fields, API token metadata, session records, account status, and admin-created marketplace delivery details.
- Service and billing records: Token Wallet balance, wallet adjustments, usage transactions, model name, request timestamps, token counts, charge amounts, and recent account activity.
- Technical and security data: IP address, user agent, request route, error details, authentication events, and operational logs needed to protect and operate the service.
- Registration abuse-prevention data: one-way hashes derived from the registration IP address and browser/device fingerprint. These hashes enforce the one-trial-account rule without storing the raw device fingerprint in the registration guard ledger.
- Support and communication data: email messages, SMTP delivery metadata, referral invitation names and email addresses, referral and reward status, and any information a user or administrator sends to support.
Purposes and legal basis
- Contract and service delivery: create accounts, authenticate users, provide dashboard access, generate setup scripts, proxy API requests, maintain wallets, and show usage records.
- Legitimate interests: secure the platform, prevent abuse, debug errors, maintain service reliability, respond to support requests, and preserve audit records for administrators.
- Legal obligations: keep records where required for accounting, disputes, fraud prevention, tax, regulatory, or law enforcement requests.
- Consent: optional website analytics and advertising measurement run only after the corresponding cookie choice. Refusing or withdrawing optional consent does not prevent use of your account or purchases.
Recipients and processors
Personal data is available to authorised MagnetAPI administrators and technical operators where needed. Data may be processed by hosting providers, database services, SMTP/email providers, upstream coding model/API providers, and security or infrastructure vendors needed to run the service. API prompts, completions, tool results, and metadata may be sent to upstream model/API providers to fulfil API requests.
International transfers
Infrastructure and providers may operate in countries outside the European Economic Area or the United Kingdom. Where GDPR transfer rules apply, MagnetAPI.org relies on appropriate contractual, technical, and organisational safeguards available through the relevant provider relationship.
Retention
Account, wallet, usage, and security records are kept while the account is active and for a reasonable period afterwards for support, billing, dispute, abuse-prevention, and legal record purposes. Data that is no longer needed is deleted or anonymised where practical, unless retention is required for legal, security, or accounting reasons.
Cookies and browser storage
Necessary cookies and browser storage support sign-in, security, fraud prevention, checkout you request, and your cookie choice. Optional analytics and marketing stay off until you opt in through our cookie controls. You may reject them as easily as accepting, select categories separately, and withdraw at any time using Cookie settings in the footer. We remember your choice for up to 180 days and ask again after expiry or a material policy change. Global Privacy Control and Do Not Track keep optional tools off.
Analytics includes first-party visit statistics and configured Google Analytics. Marketing includes configured Meta and Reddit pixels; Google Tag Manager needs both categories. The browser consent layer does not send authenticated contact details to these pixels or treat registration as a paid purchase. Providers may process browser and visit information internationally under their own published policies. See our Cookie Policy for storage, purposes, provider information and withdrawal.
First-party visit statistics are also optional, including when cookieless. They use the visited page, time, general device/browser category, referrer hostname and a one-way keyed pseudonymous visitor identifier, without retaining raw IP addresses or full user-agent strings in those analytics rows. Detailed visit rows are removed after 90 days. Security, payment and service logs needed to deliver and protect the service are separate.
Your rights
Depending on location and applicable law, users may have rights to access, correct, erase, restrict, object to processing, withdraw consent, and receive a portable copy of personal data. Users may also have the right to lodge a complaint with their local data protection authority. Requests should be sent to support@magnetapi.org.
Security
MagnetAPI.org uses HTTPS, authenticated dashboards, API bearer tokens, server-side access controls, operational logging, privacy-focused response headers, and administrator-only account issuance. Users should keep dashboard credentials and API tokens private and request token rotation if a token is exposed.
Children
MagnetAPI.org is intended for business and developer use and is not directed to children. Administrators should not knowingly create accounts for children.
Changes to this notice
This notice may be updated when services, providers, legal requirements, or operational practices change. The latest version is published on this page.
Security and payment-dispute records
To secure your account, prevent payment abuse and answer genuine billing disputes, we keep relevant purchase, fulfilment, account-access and service-usage records. These may include the source IP observed by our trusted infrastructure, timestamps, browser/app information, existing app-provided device identifiers, request references, payment references and support-delivery metadata. Device claims and IP addresses are signals, not proof of a unique person or exact location.
We do not collect passwords, private device files, MAC addresses or coding contents for this evidence feature. Optional analytics consent remains separate. Access is restricted to authorized staff; relevant evidence may be shared securely with the payment processor, issuer or professional adviser when necessary to resolve a dispute. New security receipts are retained for 540 days unless a specific dispute/legal hold requires longer preservation. Existing financial records retain their applicable accounting and legal retention. You can ask about your information or exercise applicable privacy rights through customer support. Notice version: 30 October 2026.
