Paddock Companion is the Discord bot for Paddock Records. It connects racing records, league tools and configured ticket workflows. Each server chooses which features to enable.
Operated as a personal project by Artūrs Brūvers, Latvia. Contact: [email protected].
1. Using Paddock Companion
These terms apply when you install, configure or use Paddock Companion and its connected bot features. “We”, “us” and “our” mean Artūrs Brūvers operating Paddock Records. The Privacy Policy explains how information about you is handled, including information supplied by a league or another participant.
You must meet Discord’s age and account requirements, including any higher minimum age that applies in your country, and have the capacity or parental permission required by applicable law. You must also follow Discord’s rules and the relevant server’s rules. Separate website terms apply to website accounts, uploads and any paid services.
You may stop using the bot at any time. An administrator may disable individual features or remove the bot. Doing so stops the relevant future activity but does not automatically erase previously stored records; contact us for a privacy request.
2. Features and scope
Available features include race check-ins, Driver Record linking, driver showcase previews and deliberate sharing, qualifying announcements, configured ticket archives, and managed reports and appeals. Availability depends on server configuration, access permissions, website integration and the data supplied.
Paddock Companion is an independent project. It is not endorsed by Discord, a racing game publisher, Formula 1 or a motorsport governing body. A “Paddock qualifying record” is a record within the relevant Paddock dataset, game and category, not a verified worldwide game record.
3. Server and league responsibilities
Only configure a server or league you are authorised to manage. Select the intended channels and roles, give the bot only the permissions its enabled features need, and keep staff and archive-server access up to date.
Before enabling recording or importing existing open tickets, explain to participants that messages, edits and supported media are captured, media is copied to an archive Discord, and authorised staff can review the resulting archive. Make the Privacy Policy easy to find. Installing the bot is not a substitute for a lawful basis to process participants’ information.
You must have appropriate rights and a lawful basis to submit racing data, names, evidence, images, videos and branding. Do not enable recording for unrelated conversations or upload unnecessary sensitive information. Discord server owners and members with Administrator permissions may retain access to otherwise private Discord channels.
4. Acceptable use
Do not use the service for harassment, discrimination, doxxing, impersonation, false evidence, unlawful surveillance, spam, malicious files or infringement of another person’s rights. Do not bypass access controls, claim another person’s account, deliberately falsify racing records or overload the service.
Protect your account and credentials. Report a suspected security issue privately to [email protected]; do not publish someone else’s private evidence or credentials when reporting it.
5. Racing records, links and public cards
Records and rankings reflect the available submitted and published data. History can be incomplete, provisional or later corrected. Automated name matches are suggestions for authorised staff to review; a similar name does not prove identity. A staff-confirmed Discord association does not grant ownership of a website account.
Profile commands open a private preview for the requester. Choosing Share my card or Share driver card deliberately posts the selected driver’s public racing overview in the destination channel. You may share another driver’s public card, but must not misrepresent it or use it to target them.
Shared cards are dated snapshots and may remain visible after the underlying record changes. Public posts can be copied or reshared by people who can see the channel. Contact support to correct an association or record, or to request removal of a post we control.
6. Tickets, reports and evidence
Recording applies to configured channels and accessible threads. It can include available history from existing open tickets. Captured edits, deletion markers and previous content can remain in the archive after a source message is edited or deleted. Closing a ticket or deleting its source channel does not delete its archive.
Archives and report evidence have restricted access as described in the Privacy Policy. A submitted evidence snapshot preserves the captured material at submission; later ordinary edits do not rewrite it. Privacy and legal removal requests must still be handled separately.
A ticket submission does not automatically issue a strike. Where the Driver Reports process is used, league-owner approval precedes Paddock Records staff review, and only authorised reviewers decide on account strikes. Managed league cases and appeals follow their configured review process. Contact the reviewing league about sporting decisions, or Paddock Records support about our account decisions, privacy or access.
7. Your content
You keep any rights you have in submitted content. To provide the features you request, you permit us to store, reproduce, format, transmit and display that content to the intended audience, including making the disclosed archive-media copies. This permission is limited to operating the service and remains subject to applicable privacy, deletion and intellectual-property rights.
Submitting someone else’s material does not give you ownership of it. Send copyright or other rights complaints to support with enough information to identify the material and your concern.
8. Availability and limitations
This is a personal project and no uninterrupted service or permanent storage is promised. Discord outages, permission changes, upload limits, expired or removed media, restarts and incomplete source history can interrupt capture, playback or announcements. External video links are retained as links; they are not a backup of the linked video.
Keep your own copy of important evidence and racing data. Review recording gaps and media status before relying on an archive. The service cannot recover content that was never captured and is no longer accessible.
To the extent permitted by law, features are provided on an “as available” basis without a guarantee that every result or archive is complete or error-free. Nothing in these terms excludes liability that cannot lawfully be excluded, limits mandatory consumer rights, or removes your data-protection rights.
9. Access restrictions and ending service
We may restrict a feature, server connection or account where reasonably necessary to address misuse, security, rights complaints, platform requirements or service operation. We may correct or remove inaccurate or unlawful material. Contact support if you believe a restriction is mistaken.
Ending access does not make private transcripts public. Retention and deletion are governed by the Privacy Policy and applicable requirements, including Discord’s requirements for API data.
10. Contact and changes
Contact Artūrs Brūvers, Latvia at [email protected] for questions, complaints, appeals or rights requests. You can also find general help in the Paddock Records support Discord. Use email for private information.
These terms may change as features or requirements change. We will update the date on this page and communicate material changes through the website or relevant bot notices. Changes do not remove rights already provided by applicable law.