Privacy Policy

1. Who we are

git-royal (“git-royal,” “we,” “us”) provides smart links, landing pages, conversion tracking, and related tools for musicians. This policy applies to our website at git-royal.com, the pages we host on artist subdomains, and our dashboard.

2. Information we collect

Information you give us

• Account data — your email address, display name, and handle. Authentication and passwords are managed by our infrastructure provider; we do not store your password.
• Content — release details, artwork, audio previews, links, and other material you upload to build your pages.
• Payment data — subscriptions are processed by Stripe. We receive limited billing details (such as your plan and a customer identifier) but never see or store your full card number.
• Store & purchase data — if you sell through git-royal, sales are processed directly on your own connected Stripe account; we record order details (item, amount, and the buyer's email) so we can deliver the purchase and show you your sales. If you buy from an artist's store, we collect the email you provide at checkout and any message you send with an offer, to fulfill your purchase and pass it to the seller.
• Waitlist data — if you join a waitlist, the email and any preferences you provide.
• Royalty statements — if you use the royalties tool, the statement files you upload and the earnings data we parse from them.

Information we collect automatically

• Usage and device data — pages viewed, actions taken, approximate location (such as country or city, derived from your IP address), browser and device type, referring site, and log data.
• Session and operational data — to keep the service running and secure, we record short-lived records of active sessions, including the pages being viewed and approximate location. These are used for operations, abuse prevention, and support, and are deleted automatically within 48 hours (see “Data retention”).
• Cookies and similar technologies — used to keep you signed in, to understand how our site is used, and — on our own marketing pages — for advertising measurement (see “Cookies and tracking” below).

3. Data we process on behalf of artists

When someone visits a page an artist publishes with git-royal, we record engagement events (such as page views, preview plays, and click-throughs) so the artist can measure performance. For any artist — on any plan, free or paid — who connects their own Meta or TikTok pixel, we also send these events, which may include the visitor's IP address, user agent, ad-click identifiers (such as Meta's fbclid or TikTok's ttclid), and event details. They go to that artist's Meta dataset through Meta's Conversions API and/or their TikTok dataset through TikTok's Events API, server-side; the artist's Meta pixel may also load in the visitor's browser.

For this fan and visitor data, git-royal acts as a data processor on behalf of the artist, who is the controller. The artist is responsible for having a lawful basis and any required consent, and for maintaining their own privacy notice. See our Terms of Service.

Pre-saves (Spotify)

If a fan pre-saves an upcoming release, we collect only what is needed to fulfill it. For a Spotify pre-save, the fan authorizes git-royal through Spotify's official login (OAuth); we receive a Spotify refresh token, store it encrypted, and use it once — when the release goes live — to save the release to the fan's library and/or follow the artist, exactly the action the fan requested. The token is then erased immediately. If the release is already out when they pre-save, we use the token in the moment and never store it at all. For an email-only pre-save, we collect the fan's email address and send them the smart link when the release is out. A fan can revoke git-royal's access at any time in their Spotify account settings (Apps), and can ask us to delete their pre-save data using the contact details below. Like other fan data above, pre-save information is processed on behalf of the artist.

4. Cookies and tracking technologies

On our own marketing site (git-royal.com), we use essential cookies for authentication, and — because we advertise git-royal like any other business — we also use advertising and measurement pixels from Meta (Facebook/Instagram), TikTok, and Reddit to understand which of our ads bring people to the product. These help us measure our own marketing and may be used by those platforms to show you our ads elsewhere.

We also send those same measurement events from our server (Meta’s Conversions API, TikTok’s Events API, Reddit’s Conversions API), not only from your browser. This exists because browser-based pixels are frequently blocked. It is subject to the same consent decision: where consent is required and not given, nothing is sent by either route.

To be precise about what that means, because “the same event” would be too convenient a word: the server sends the same technical signals your browser would have sent (your IP address, your browser’s user-agent string, the advertising cookies already on your device, your screen size) — plus, on the three account events (registration, starting a checkout, and a purchase), a one-way cryptographic hash of your email address. Our browser pixels do not send that. The platforms use the hash to recognise an existing account without either side sharing the address in the clear. We never send your email address itself.

To make that measurement work, we set a first-party visitor ID (the gr_uid cookie): a random identifier that lets us recognise that the same browser visited a page, tried the editor, and later signed up, rather than treating each step as an unrelated stranger. It is a random value — it is not derived from your name, your email, your IP address, or any device fingerprint, and it cannot be turned back into your identity. We share it with the advertising platforms above (as an “external ID”) only where consent allows. We also store the advertising click ID from the ad you arrived on (for example rdt_cid, fbclid), so a later signup can be credited to the right ad.

On pages that artists publish with git-royal, a paid artist may load their own Meta or TikTok pixel to measure their campaigns; there, the artist — not git-royal — decides what runs.

Where consent is required (for example, in the EU, EEA, and UK), non-essential advertising and measurement technologies load only after consent is given. Visitors in those regions are shown a banner and can accept or decline; declining leaves first-party, aggregate analytics running but stops advertising measurement — including the server-side reporting described above.

5. How we use information

• To provide, maintain, and improve the service;
• To process payments and manage subscriptions;
• To communicate with you about your account, updates, and support;
• To measure and secure our service and prevent abuse;
• To comply with legal obligations.

6. How we share information

We do not sell your personal information. We share it only with:

• Service providers that run our platform — including Supabase (database, authentication, file storage), Vercel (hosting, delivery, and site analytics), Stripe (payments), Resend (email), Spotify (pre-save fulfillment, at the fan's direction), and Meta, TikTok, and Reddit (advertising and conversion measurement). These providers process data primarily in the United States;
• An AI provider (Anthropic) — to detect the column layout of royalty statements you upload. We send only the column headers and at most two redacted sample rows — earnings figures are masked and any name/payee/tax columns are blanked before they leave our servers, so the model sees the column shapes, never the full file or your actual figures. Anthropic does not use this data to train its models;
• An AI generation provider (fal.ai) — when you use the Poster studio to generate images or video, we send your text prompt and any image or frame you supply to fal.ai to create the result. This is required for the model to produce what you asked for; see “Data retention” for how long generated files are kept;
• The relevant artist, for engagement data generated on their pages;
• Authorities, where required by law; and
• A successor entity in connection with a merger, acquisition, or sale of assets.

7. Advertising (Meta, TikTok, and Reddit)

Our own marketing pages share data with Meta, TikTok and Reddit to measure our advertising, as described in section 4. Artist pages may share data with Meta and TikTok for advertising measurement and audience building via the artist's pixel; which platform (if any) receives that data depends on what the artist has connected. Each platform's handling of the data is governed by its own policies — see the Meta, TikTok, and Reddit privacy policies.

8. Data retention

We keep personal information for as long as your account is active or as needed to provide the service, then for a reasonable period to meet legal, accounting, or security obligations, after which it is deleted or anonymized. This is enforced by an automated daily job, not by good intentions: advertising click identifiers (fbclid, ttclid, rdt_cid) are stripped from analytics rows after 90 days, the rows themselves are deleted after 400 days, and live visitor records are deleted after 48 hours. The identifier that links a captured fan back to an ad click is stripped from your fan list on the same 90 day clock — you keep the fan, we stop keeping the advertising key.

Poster studio. Artwork you upload to the poster studio, and the posters you build from it, are stored privately in your library until you delete them. Images and video generated by the paid AI tools are kept for 5 days and then permanently deleted, unless you choose to keep one — the Library has a “Keep this” control on every clip, and anything you keep stays until you delete it. Everything else goes on the 5-day schedule automatically. To generate an image or video, your prompt and the frame you built are sent to our AI generation provider (fal.ai), which is required for the model to produce it; that copy is removed from our storage as soon as the video comes back.

When you delete your account (Settings → Delete account), we immediately and permanently remove your profile and everything tied to it from our live systems — your pages, uploads (cover art, audio, and any files you sell), links, analytics, fan list, and royalty data. Residual copies may persist in routine, encrypted database backups, which are on a rolling cycle and are overwritten within 30 days; we do not restore deleted accounts from them. Anonymous, non-identifying analytics that aren't linked to you may be retained.

9. Your rights

Depending on where you live, you may have rights to access, correct, delete, or port your personal data, and to object to or restrict certain processing. To make a request, email us at the address below. For data collected on an artist's page, we may direct your request to that artist as the controller.

10. International transfers

We and our providers may process data in countries other than yours. Where required, we rely on appropriate safeguards for such transfers.

11. Children

git-royal is not directed to children. You must be at least the age of majority in your jurisdiction to hold an account, and in any case we do not knowingly collect data from anyone under 16 (or the higher minimum age required in your country).

12. Security

We use technical and organizational measures designed to protect personal data against unauthorized access, loss, and misuse. These include encryption of data in transit and encryption of sensitive credentials at rest, access controls and isolation between customer accounts, and ongoing monitoring of our systems and code. No method of transmission or storage is completely secure, and we can't guarantee absolute security. For more on how we protect the data you and your fans entrust to us, see our Trust & Security page.

13. Changes to this policy

We may update this policy from time to time. Material changes will be reflected by the “Last updated” date, and where appropriate we will notify you.

14. Contact

Questions or requests? Email support@git-royal.com.