RolePilot Privacy Policy

This Privacy Policy explains how RolePilot collects, uses, stores, discloses, and protects personal information when you use the RolePilot website at https://rolepilot.io, create an account, connect third-party platforms, communicate with us, or otherwise interact with the RolePilot service.

This Policy applies to information we collect directly from you, automatically through your use of the service, and through authorized interactions with connected services or service providers acting on our behalf.

We may collect account and identity information such as your name, email address, login credentials, subscription status, profile settings, and account preferences.

If you sign in with Google, Apple, or another supported third-party identity provider, we receive a limited subset of your provider profile that you authorize during the sign-in consent screen, typically your email address, full or given/family name, and profile photo URL. We use this information solely to create or identify your RolePilot account, pre-fill your display name and avatar inside the product, and link your sign-in session. We do not receive or request access to your inbox, contacts, calendar, drive, photos library, or any other content from the connected provider. You may revoke RolePilot's access at any time from your provider's account settings (for Google, this is at myaccount.google.com under Security → Third-party connections), which will prevent future sign-in but does not by itself delete your RolePilot account; use the Account → Delete Account control inside RolePilot if you also wish to remove your stored data.

We collect the casting profile you build in RolePilot: your legal and stage name, date of birth and playing-age range, gender, email address, phone number, city and additional work locations, biography, union status and member ID where you choose to include it, background-casting agency, credits, reel and social links, languages, accents, and special skills.

Because casting decisions turn on appearance, we also collect physical characteristics you enter: height, weight, eye and hair colour, body type, whether you have visible tattoos, and your ethnicity or ethnic appearance. Where you opt in to vehicle-based background work we collect your vehicle's make, model, year, and colour. We collect your stated willingness to accept roles involving nudity or stunts so that we only submit you to roles matching those choices. Any of these fields may be left blank, which reduces how accurately we can match you to roles.

We store the headshots, size cards, reels, and other media you upload or import, together with any AI-generated description of that media used for matching. For billing we hold your subscription tier, your payment-processor customer and payment-method identifiers, and non-sensitive card metadata: brand, funding type, last four digits, expiry month and year, and issuing country, plus a processor-supplied card fingerprint used solely to detect duplicate or abusive accounts. We never receive or store your full card number or security code; those go directly to our payment processor.

If you connect third-party casting or entertainment platforms, we may collect and store the credentials, account identifiers, saved search preferences, sync history, role data, submission-related metadata, and related platform information necessary to provide the service.

TRIAL-ABUSE AND LINKED-ACCOUNT SIGNALS. When you first link a casting platform, and again when a free trial starts, we record a one-way hash of that platform login: a fixed-length digest computed from the platform name and your username on it, together with, where we have it, a one-way hash of that platform's own profile identifier for your account. When a free trial starts we also record a one-way hash of your email inbox, computed so that variations of the same address (letter case, and dots or plus tags where your email provider ignores them) count as one inbox. We do not store the username, the profile identifier or the email address in these records, and the hashes cannot be decrypted or reversed; they can only be compared against a value presented to us again. Together with the payment-processor card fingerprint described above, they are how we keep each casting login tied to one RolePilot account and tell a member starting a first trial apart from an account taking a second one under a new email address. These records are kept on a different footing from the rest of your data: the record tying a casting login to your account is kept while your account exists and for twenty-four (24) months after it is deleted, and the records that a login or an inbox was used for a free trial are deleted automatically twenty-four (24) months after they were recorded. Section 3 says what they are used for, Section 8 says how long they are kept and why, and Section 10 gives the California basis for keeping them.

We may collect usage and technical data such as browser type, device information, IP address, approximate location based on IP, timestamps, pages viewed, interactions, diagnostics, log data, and other information reasonably necessary for service operation, security, and troubleshooting.

We may collect security telemetry, including signals related to potential probing of client-side code, automated scanner activity, repeated failed authentication, and similar protective indicators. This data is retained for abuse detection, incident response, and enforcement of our Terms of Service.

If you contact us, we may collect the contents of your messages, support requests, feedback, attachments, and related communication records.

If you use Kairo or other in-product AI chat features, we may collect and store the prompts, replies, prior conversation context, account identifiers, subscription tier, device or browser metadata, IP address, timestamps, and related monitoring or safety signals associated with those interactions.

If you use the AI Reader feature in the Lab, you may grant your browser permission to access your device microphone for the duration of a rehearsal session. The microphone audio is processed by your browser's built-in Web Speech API for the sole purpose of detecting when you have finished speaking your line, so the partner reader can advance automatically. Audio captured by your browser is NOT transmitted to RolePilot servers, NOT stored on RolePilot infrastructure, and NOT used for transcription, training, or any purpose beyond local silence detection. Some browsers (such as Google Chrome) may route Web Speech API audio to the browser vendor's own speech recognition service under that vendor's privacy practices, which RolePilot does not control. You may revoke microphone permission at any time through your browser settings, decline the permission prompt, or use the AI Reader without auto-advance (the manual 'Your Line' button still works without microphone access).

When you paste or upload script text or PDFs into the Lab, that text is sent to the AI model providers we use to generate your scene analysis, audition feedback, or other Lab outputs. An AI audio provider processes the dialogue text needed to generate spoken partner-reader audio for AI Reader rehearsals. We do not retain script content beyond your account history described in this Policy. Each AI provider applies its own data practices.

When you upload or import a headshot, the image is sent to an AI provider to generate a written description used for role matching. That description may record apparent age range, apparent gender, hair and eye colour, complexion, build, and casting archetypes, and is stored on your profile. Match scoring and cover notes send the relevant fields of your profile together with the role listing.

We do not train AI models on your data, and the providers we use are contractually barred from training on data submitted through their APIs. We do use your own activity inside RolePilot, such as the roles you swipe on, submit to, and hear back from, to personalise which roles we surface and submit you to. That analysis is specific to your account. It is not pooled with other members and is not used to build shared models.

We use personal information to provide, operate, maintain, secure, and improve RolePilot, including authenticating users, managing accounts, supporting connected-platform workflows, syncing data, enabling role filtering, generating or storing settings, and supporting submission-related features.

We use personal information to communicate with you about service use, security matters, account issues, support requests, billing, product changes, and legal or compliance matters. These transactional messages are necessary to operate your account.

We may also use your email to send promotional messages such as new features, product updates, tips, and occasional offers. We do not sell or rent your email and we do not send unsolicited bulk spam. You can opt out of promotional email at any time in Settings, Notifications or via the unsubscribe link in every promotional email. Opting out does not stop transactional messages. We honor opt-outs promptly per the CAN-SPAM Act and applicable law.

We use information to detect, prevent, investigate, and address fraud, abuse, unauthorized access, security incidents, technical problems, and violations of our Terms.

Cross-account checking for linked accounts and duplicate trials. Three kinds of signal are compared between accounts rather than within one: the identifier our payment processor assigns to a card, the one-way casting-login and platform-profile hashes, and the one-way email-inbox hash, all described in Section 2. We use them to keep each casting login tied to the first RolePilot account it was linked to, and to refuse a second free trial to a card, casting login or inbox that has already had one. If a duplicate trial starts anyway, it ends right away and the selected plan begins at its normal price, and we email the member to say so. Where the same signal appears on more than one account, those accounts may be grouped for a person at RolePilot to review. Our Terms of Service, Sections 6 and 12, set out the rules this enforces. We do not use these signals for advertising, for scoring or ranking you, or for any purpose other than enforcing those rules and detecting linked accounts, and we do not disclose them to casting platforms or anyone else.

We may use information in aggregated or de-identified form for analytics, service improvement, product planning, performance analysis, and operational reporting, provided that such information is not reasonably used to identify you.

We may review and monitor AI chat interactions for moderation, model and prompt evaluation, incident response, support, workflow debugging, quality control, abuse detection, and compliance with our legal obligations and Terms of Service.

Where applicable, we process personal information because it is necessary to perform our contract with you, because it is necessary for our legitimate interests in operating and securing the service, because you have provided consent, or because processing is required to comply with legal obligations.

You may choose not to provide certain information, but some features may not function without it, including account creation, billing, connected-platform access, and certain sync or automation functions.

We share personal information with vendors that process it only on our written instructions and only to deliver the service you asked for: hosting and database infrastructure, payment processing, transactional email, background job processing, caching, security and abuse prevention, product analytics, connected-platform operations, and the AI providers described below.

Where you connect a casting platform, a service provider acting on our behalf uses your sign-in details to carry out the actions you have asked for, and may keep you signed in between runs. They are contractually bound to use those details for no other purpose. This is the most sensitive processing described in this Section.

THE VENDORS WE USE. We work with service providers in these categories: cloud hosting and scheduled processing; database, authentication and file storage; payment processing; transactional email delivery; connected-platform operations, which is the category that receives your casting-platform sign-in details; AI model providers for text generation and the in-app assistant; AI providers for image generation and for spoken audio in the Audition Lab; cookieless product analytics; and an IP geolocation lookup used for security and abuse prevention, which receives the IP address of a request in order to return an approximate country and region. Each processes personal information only on our written instructions and only to deliver the service you asked for. This list covers every category of vendor that processes personal information on our behalf as of the date at the top of this Policy; we will update it here when it changes. If you want to know which specific provider sits in any of these categories, email hello@rolepilot.io and we will tell you.

We do not share personal information with advertising networks, data brokers, or social platforms, and we do not sell or share it as those terms are defined under California law.

Our product analytics providers, one for cookieless event analytics and one for cookieless site-usage measurement, are US-based. Both run in a cookieless mode under default service-provider terms, set no advertising identifiers, and we do not enable cross-site re-targeting or advertising features.

We may disclose information when reasonably necessary to comply with law, regulation, court order, subpoena, lawful request, or legal process, or to protect the rights, safety, property, users, or integrity of RolePilot and others.

We may disclose information in connection with a merger, acquisition, financing, reorganization, sale of assets, or similar corporate transaction, subject to customary confidentiality and legal protections.

RolePilot does not engage in cross-context behavioral advertising and does not enable advertising features in our analytics providers. We use product-analytics services under their default terms as service providers. Under CCPA and CPRA, these are service-provider relationships, not sales of personal information. If you wish to opt out of personal-information sharing of any kind, see the 'Do Not Sell or Share My Personal Information' link in our footer.

California residents have the right to opt out of the sharing of personal information for cross-context behavioral advertising. RolePilot does not engage in this practice, but if you wish to make this opt-out explicit you may submit a request at /dnsmpi or email hello@rolepilot.io with the subject 'DNSMPI Opt-Out'.

RolePilot may process login credentials or related authentication materials for connected third-party casting platforms at your direction. We use those credentials solely to automate submissions and sync roles on your behalf. We do not use your credentials for any other purpose, and we do not sell or share them with third parties.

Connected account credentials are encrypted before being stored and are decrypted only within RolePilot's secured server environment at the time of performing the automation action you requested. We apply industry-standard symmetric encryption and limit decryption to server-side processes. We review and improve our encryption practices over time.

You may disconnect any connected account and request deletion of your stored credentials at any time through the Connect Accounts settings. Disconnecting removes your credentials from our system and stops all related automations.

What disconnecting does not remove. Disconnecting erases the credentials themselves. It does not erase the one-way hash that ties that casting login to your RolePilot account, or the record that the login was used for a free trial, both described in Section 2. Those hashes cannot be reversed back into your username, and Sections 8 and 10 explain how long they are kept.

THIRD-PARTY PLATFORM ENFORCEMENT. When you connect a casting platform account, RolePilot performs automated actions (such as role syncing and submission) on your behalf using the credentials you provide. Third-party platforms may independently monitor account activity and may restrict, suspend, or permanently ban accounts they determine have engaged in activity that violates their terms of service. RolePilot does not receive advance notice of, and has no ability to prevent, any enforcement action taken by a third-party platform. We do not share information with third-party platforms for the purpose of triggering enforcement actions. Please review our Terms of Service, Section 5 for a full description of platform-related risks and your assumption of those risks.

AVAILABILITY AND SCHEDULING DATA. Some connected platforms collect your availability for specific shoot dates rather than applications. Where you enable automation for such a platform, we process and store the availability submitted on your behalf, the dates and listings concerned, and the platform's response. If you connect a calendar, we may read availability from it solely to decide whether to submit on your behalf. We do not guarantee that any availability submission results in a hold, booking, or payment, and you remain responsible for your own schedule. See Terms of Service, Sections 5 and 12.

Even with reasonable safeguards, no system can be guaranteed to be completely secure. You should use strong, unique passwords for any accounts you connect, protect your own devices, and notify us promptly at hello@rolepilot.io if you suspect unauthorized access.

We and our service providers may use cookies, local storage, session tokens, log files, and similar technologies to keep you signed in, remember settings, maintain security, measure performance, and support core product functionality.

You may be able to control some cookies through your browser or device settings. However, disabling certain technologies may impair essential parts of the service.

RolePilot does not engage in cross-context behavioral advertising and does not enable advertising features in our analytics providers. We use product-analytics services under their default terms as service providers. Under CCPA and CPRA, these are service-provider relationships, not sales of personal information. If you wish to opt out of personal-information sharing of any kind, see the 'Do Not Sell or Share My Personal Information' link in our footer.

Our analytics run in a cookieless mode and do not set advertising cookies. To opt out of all analytics on RolePilot, use the 'Do Not Sell or Share My Personal Information' link in our footer, or enable Global Privacy Control (GPC) in your browser. We honor the GPC signal automatically and stop loading analytics for that browser.

We retain personal information for as long as reasonably necessary to provide the service, maintain your account, comply with our legal obligations, resolve disputes, enforce agreements, and protect the integrity and security of RolePilot.

Retention periods may vary depending on the type of information, the purpose for which it was collected, technical needs, account status, and legal or compliance requirements.

Inactive free accounts. Where we identify a free account (an account that has never held a paid subscription or free trial) as inactive, defined as no sign-in, no API call, and no automated submission activity for at least twelve (12) consecutive months, we may delete the personal information associated with that account, subject to the legal-hold, billing-record, and security-log retention exceptions described in this Policy. We will send at least one notice to the account email approximately thirty (30) days before deletion takes effect, and signing in resets the inactivity period. An account that holds or has ever held a paid subscription or trial is not subject to this automatic inactivity deletion; we retain its data only as long as needed for the purposes described in this Policy and applicable billing-record obligations, and you may still request deletion at any time under Section 9.

Chat logs, monitoring records, security logs, and moderation data may be retained for longer periods where reasonably necessary for fraud prevention, abuse investigation, legal compliance, dispute resolution, service integrity, or enforcement of our Terms.

Trial-abuse and linked-account signals are kept after deletion, for a limited time. The card fingerprint, the one-way casting-login and platform-profile hashes, and the one-way email-inbox hash described in Section 2 are retained after you disconnect a platform and after your RolePilot account is deleted. The record tying a casting login to your account is kept for twenty-four (24) months after your account is deleted, and the records that a login or an inbox was used for a free trial are kept for twenty-four (24) months from the date they were recorded; both are then deleted automatically, whether or not you ask us to. Twenty-four months is the period we can justify: repeat free trials and re-used logins come back within weeks or months, so a longer window would keep the records past the point they are doing anything. We are stating that plainly because it is the one place our retention does not follow your account: a record that disappears the moment somebody disconnects or deletes cannot detect what it exists to detect, which is the same card, casting login or inbox coming back for another free trial under a new account. None of these records holds your name, your email address, your card number, or your platform username. The hashes cannot be reversed and are only ever compared against a value presented to us again. We keep them for this purpose and no other, and we never sell or share them. Section 10 gives the California basis for this.

Deletion grace period. When you request deletion of your account, we stop all automated submission activity immediately and permanently erase your data thirty (30) days later. The delay exists so that a deletion made in error, or by someone other than you, can be reversed by signing in and cancelling the request before it takes effect. Deletion completes well inside the 45-day response deadline described in Section 9. You may ask us to complete the deletion sooner by writing to hello@rolepilot.io.

Record of privacy requests. California regulations require us to keep a record of every consumer privacy request and how we handled it for twenty-four (24) months. That record contains the email address associated with the request, the type of request, the date we received it, and the date we fulfilled it. It is stored separately from your account and is deliberately preserved after the account itself is erased, because it is the evidence that we honored your request. It is used only to demonstrate compliance and for no other purpose.

Depending on where you live, you may have the right to request access to personal information we hold about you, request deletion, request correction, request portability, or object to or limit certain processing, subject to applicable exceptions.

You may also request to close your account or disconnect third-party services. Some information may be retained where legally required or reasonably necessary for security, billing, fraud prevention, dispute resolution, or compliance purposes.

To make a privacy request, contact us through our support channels or by email at hello@rolepilot.io. We may take reasonable steps to verify your identity before fulfilling a request. We will respond to verifiable requests within 45 days of receipt. If we need additional time (up to 45 more days), we will notify you of the extension and the reason within the initial 45-day period.

We acknowledge receipt of a privacy request in writing within ten (10) business days and tell you how we intend to process it. You can submit a request from inside the product under Account, by email to hello@rolepilot.io, or through the Do Not Sell or Share form linked in our footer.

What deletion removes. When a deletion completes we erase your profile, submission history, saved media, and AI history from our database and file storage; we delete the stored sign-in data for your connected casting platforms; and we delete your customer record with our payment processor. We also direct our service providers to delete the personal information they hold on our behalf, including our product-analytics provider, and we strip your email address and message content from our transactional email records. Some information may be retained where an exception applies, including records our payment processor must keep for tax and chargeback purposes, security and abuse-investigation logs, the trial-abuse and linked-account signals described in Sections 2 and 8, the privacy-request record described in Section 8, and aggregated or de-identified statistics that no longer reasonably identify you.

If you are a California resident, California law may provide you with the following rights, subject to applicable exceptions: (1) Right to Know: the categories and specific pieces of personal information collected about you, the sources and purposes for collection, and categories of third parties with whom we share it; (2) Right to Delete: request deletion of personal information we collected from you; (3) Right to Correct: request correction of inaccurate personal information; (4) Right to Opt-Out of Sale or Sharing: we treat our analytics relationships as service-provider relationships and do not engage in cross-context behavioral advertising, but you may submit an explicit opt-out request at /dnsmpi; (5) Right to Non-Discrimination: we will not discriminate against you for exercising your California privacy rights.

We collect the categories of information described in this Policy for the business and commercial purposes described above. We may disclose those categories to service providers and contractors that assist with infrastructure, hosting, authentication, support, billing, communications, product operations, and security.

We do not knowingly sell personal information for monetary value. We treat our product-analytics relationships as service-provider relationships under CCPA and CPRA, and we do not enable cross-context behavioral advertising features within those tools.

Fraud-prevention signals kept after a deletion request. California law allows a business to retain personal information it needs in order to detect security incidents and to prevent, and prosecute those responsible for, malicious, deceptive, fraudulent or illegal activity, notwithstanding a deletion request (Civil Code § 1798.105(d)). We rely on that exception for the signals described in Section 2 and nothing else: the payment-method fingerprint supplied by our payment processor, the one-way hashes of a connected casting-platform login and its platform profile identifier, and the one-way hash of your email inbox. We keep them so that a casting login stays tied to one account and the same card, casting login or inbox cannot take repeated free trials through new accounts. We keep them for that reason alone, and not indefinitely: they are deleted automatically on the twenty-four (24) month schedule described in Section 8, which is the period we can justify for the purpose rather than an open-ended one. None can be reversed into your card number, platform username or email address, none is sold or shared, none is used for cross-context behavioral advertising, and none is disclosed to casting platforms. Everything else covered by your deletion request is erased as described in Section 9. If you believe we are holding one of these records about you in error, write to hello@rolepilot.io.

Shine the Light (California Civil Code §1798.83): We do not share personal information with third parties for their own direct marketing purposes. California residents who wish to confirm this may contact us at hello@rolepilot.io.

Sensitive Personal Information: We collect account credentials for the platforms you connect; racial or ethnic origin, because casting breakdowns specify it; your stated willingness to accept roles involving nudity; and, in the limited circumstance described in the next paragraph, information concerning mental health. We use each of these solely to provide the matching and submission service you requested, to secure your account, and to meet the safety obligation described below. We do not use or disclose sensitive personal information for any purpose that would give rise to a right to limit its use under California law, and we do not sell or share it.

Crisis safety records. When a message you send to our in-product assistant indicates a possible mental-health crisis, the assistant stops and replies with crisis resources instead of an ordinary answer, and we record that the event happened, when it happened, and which part of the product it happened on. We keep that record for one reason: California and New York law require an operator of a chatbot like ours to maintain a protocol for responding to expressions of suicidal ideation or self-harm and to refer you to crisis services, and this is how we show that the protocol actually ran. The record does not contain your message, a copy of it, or any description of what you wrote; the conversation itself stays in your chat history and is governed by Section 8. We do not attach your IP address to it. We retain these records for ninety (90) days and then delete them, they are erased with your account if you ask us to delete it, and we never sell or share them. We do not diagnose you, do not monitor you for signs of distress outside of what you type to the assistant, and do not provide treatment or counseling of any kind.

California UCL and CLRA Disclosure: Under California Business and Professions Code § 17200 (Unfair Competition Law) and Civil Code § 1750 (Consumer Legal Remedies Act), we are required to make transparent material disclosures about our service. We disclose that using RolePilot's automated submission and sync features in connection with third-party casting platforms carries the risk that those platforms may restrict or ban your account. This risk is described in detail in our Terms of Service, Section 5. We make this disclosure so you can make an informed choice. RolePilot does not engage in deceptive advertising or conceal material risks from California consumers.

RolePilot is for adults. The service is intended for users 18 years of age and older only. We do not knowingly accept registrations from anyone under 18. During account activation we require a date of birth and enforce an 18-and-older floor at the application layer. We additionally enforce a hard 13-year COPPA floor at the database layer.

RolePilot is not directed to children under 13, and we do not knowingly collect personal information from children under 13 through the service. If we learn that we collected personal information from a child under 13 without legally valid authorization, we will take reasonable steps to delete it. For users between 13 and 18 who attempt to activate an account, we refuse activation and delete the date-of-birth entry without storing it for later use.

If you believe a person under 18 has created or attempted to create an account, please contact hello@rolepilot.io. We will investigate and, when warranted, terminate the account and delete associated personal information.

RolePilot is operated from the United States. If you access the service from another jurisdiction, you understand that your information may be transferred to, stored in, and processed in the United States and other locations where our service providers operate, subject to applicable legal safeguards.

We use safeguards designed to protect personal information against unauthorized access, destruction, loss, alteration, or disclosure. Those measures may include encryption, authentication controls, access limitations, environment separation, and monitoring appropriate to the type of information and risk presented.

Because no system is completely secure, we cannot guarantee absolute security. You are responsible for safeguarding your own account credentials and notifying us promptly of any suspected unauthorized use.

We may update this Privacy Policy from time to time. If we make material changes, we may provide notice through the website, the application, or by email when appropriate. The "Effective date" above reflects the current version.

Your continued use of the service after changes become effective means the revised Policy will apply to your future use of RolePilot.

When you use AI features such as Kairo, Smart Match, AI Cover Notes, match reasoning, or audition lab tools, your inputs and the resulting outputs are transmitted to third-party AI model providers for inference. We use these providers under their default API terms, which contractually prohibit the use of customer data submitted through their APIs to train provider foundation models.

We do not train any AI model, third-party or our own, on your inputs or outputs. We do not sell AI inputs or outputs.

We retain AI inputs and outputs in our own systems as part of your account history, conversation continuity, analytics, debugging, abuse prevention, safety review, and product improvement through human review and product iteration. Retained AI history is treated as personal information under this Policy and is subject to the same access, deletion, and correction rights described in Section 9.

AI features are designed for casting and audition workflows. You should not submit medical, legal, financial, biometric, government-issued identifiers, or other highly sensitive information into AI surfaces. We are not responsible for the consequences of voluntarily submitting such information to AI features.

AI-generated content is produced as a draft for your review. AI models can produce errors, omissions, hallucinations, or content that is plausible but factually wrong. You are responsible for reviewing AI-generated content before sending it on your behalf or submitting it to any third party. By enabling automated features (such as Auto Apply or AI Cover Notes auto-submission), you consent to AI-generated content being sent under your standing pre-approval, and you accept responsibility for the content of every submission generated and sent under those settings.

If you delete your account, we delete the personal data associated with it, including your AI history, within 30 days, subject to retention exceptions described elsewhere in this Policy. Aggregated or de-identified statistics derived prior to deletion that no longer reasonably identify you may be retained.

Brand names, logos, and trademarks belonging to third-party casting platforms, including Actors Access (Breakdown Services, Ltd.), Backstage (Backstage LLC), Casting Networks (Talent Systems, LLC), and Commercial Extras, are the property of their respective owners. We use those names and visual marks descriptively to identify which platforms RolePilot integrates with so users can recognize the surface they are connecting.

Their inclusion in our website, application, or this Policy does not imply endorsement, sponsorship, partnership, certification, or affiliation. RolePilot is an independent service and is not owned by, controlled by, or formally affiliated with any of these companies.

If you are a rights-holder and believe a mark of yours has been used in a way that exceeds nominative fair use, contact hello@rolepilot.io and we will review promptly.

Questions or requests about this Privacy Policy may be sent through our support channels or by email to hello@rolepilot.io.

This Privacy Policy applies to RolePilot services offered through https://rolepilot.io and product experiences that link to this Policy.