1. Controller and contact
The intended controller is Stock42 LLC, pending confirmation of its legal and tax details.
- Website: breedercontrol.com.
- Privacy and service email: [email protected].
- Contact address: Mendoza 1826, 6C, Buenos Aires, Argentina.
This address does not establish an LLC's registered office or jurisdiction of incorporation. This policy covers visitors, users, business contacts and people whose information is lawfully added to the service, including those without accounts.
2. Who determines how data is used
BreederControl will determine the processing needed for its accounts, contracts, support, security and legal duties. When a breeder adds buyers' or collaborators' data to manage its business, it will ordinarily determine the purposes of those records and must inform people and establish a valid legal basis. For operations carried out on its behalf, BreederControl will act as a processing service provider under the relevant agreement.
Responsibilities must be documented for each function. Using the platform does not give a breeder general permission for other uses. BreederControl will handle requests within its responsibility and cooperate with the relevant controller, without requiring an account or simply referring people elsewhere without assistance.
3. Data, sources and necessity
The contact form collects name, WhatsApp number, email and message, together with the form language and receipt date. Enquiries are stored in the service database and are available only to active administrators so they can respond. Submitting the form does not publish these details or send an automatic email.
The workspaces store dog and cat profiles and relationships, litters, weights, health, buyer contacts, reservations, manually recorded movements and deliveries. Owners may add private feeding, journal and schedule records. Files, dates, authorship and record permissions are retained. Blog articles become public only when explicitly published. Assistant conversations and action results remain scoped to their user.
A purchase record stores the buyer email, animal name and species, purchase date, breeder and recording user. This links the verified Google identity and calculates the single 30-day trial. Billing records retain Stripe customer, Checkout and subscription references, status, paid invoices and access periods. Price agreements record the amount, date and responsible administrator. Card details are entered in Stripe; BreederControl does not store full card numbers or security codes.
Landing testimonials may include a photo, name, breeder and comment supplied through administration. Publishing makes those details visible to any visitor; withdrawing the entry removes it from the landing and restricts its photo to administrative access. Fictional review examples remain private.
An administrator may create a breeder using its operator’s email. The link is validated when the operator signs in with Google. Free-day grants, their number, date and responsible administrator are also recorded to manage access and prevent duplicates.
Breeder registration also collects first name, last name and breeder name. Email comes from the identity validated with Google; a typed email address does not establish ownership of an existing account. Registration stores the start and end of the 7-day trial and, where relevant, the paid-through date.
When the relevant functions are enabled, processing may include:
| Category | Data and source | Purpose |
|---|---|---|
| Sign-in and account | Google sub identifier, name, email and available profile picture; role, links, status and language. From Google and service registration. | Identify the user, administer the account and permissions. No Google password or Gmail or Drive access is requested. |
| Breeder and contacts | Identifying and contact details of organisations, collaborators and buyers; reservations, invitations, deliveries and financial records supplied by authorised users. | Manage operations and link the correct person to shared information. |
| Animals and care | Species, breed, litters, weights, veterinary history, feeding, diaries, documents and photographs supplied by breeders or owners. | Organise dog and cat histories. A file about an animal may also identify people, veterinarians or families. |
| Assistants | Questions, files, authorised context, answers and actions requested from the assistant. | Answer the query and perform the requested function within permissions. |
| Subscriptions | Necessary billing details, plan, customer and subscription references, payment status and transaction information from the provider. | Manage payments and receipts. Full card details must only be entered into the enabled payment flow, never chats or notes. |
| Support and connection | Enquiries sent to the contact address; IP address, date and time, browser and technical information processed in connections or operational logs. | Respond, deliver the site and address failures or abuse. Cloudflare currently participates in access to the domain. |
Not all data is mandatory. Each function must identify required fields and the consequences of not providing them: for example, an account needs a sign-in identity, and the assistant needs a query to answer. Optional fields must not become a condition for unrelated functions.
Do not upload sensitive human information, identity documents, children's data or other people's data that is unnecessary or lacks lawful authorisation. An animal's health history is not, in itself, a person's medical data.
4. Purposes and legal grounds
Data will be used to provide requested functions, administer permissions and subscriptions, share records according to authorised instructions, answer enquiries, maintain operations and comply with legal duties. Processing must rely on informed consent where required or another applicable legal permission, such as information necessary to perform the contractual relationship or a legal obligation.
Accepting terms, signing in with Google or receiving an invitation does not authorise unrelated purposes. Consent needed for optional uses must be specific and may be withdrawn without affecting prior lawful processing. Optional marketing messages must have an unsubscribe method and remain separate from necessary operational notices.
This policy does not authorise selling personal data, publishing it for advertising or training models on private documents. New purposes require prior disclosure and an appropriate legal basis.
5. Access, recipients and providers
Breeders and owners will access their own scope and information lawfully shared with them. Delivering an animal does not automatically give a breeder access to the new owner's private diaries.
The planned or current providers are:
- Cloudflare: currently involved in access to the domain and technical delivery. Privacy policy.
- Google: sign-in when enabled. Privacy policy.
- DeepSeek: processing queries and context sent to the assistant when enabled; see section 6 and the Open Platform terms.
- Stripe: subscriptions outside Argentina when enabled; depending on the operation and its duties, it may act as controller or processor. Privacy policy.
Provider links supplement this policy; they do not replace the information BreederControl must provide about its own processing. Lawfully required disclosures to authorities will be limited to the applicable request or obligation.
6. AI and international processing
When a message is sent to the assistant, DeepSeek receives the message, authorised workspace context and recent history of that conversation. Tools may retrieve more authorised records and extract text from requested PDF or TXT files. Other accounts’ records and private owner notes are not included in a breeder’s context. The interface explains this before sending. The technical integration is available; this draft does not confirm the retention, use or transfer arrangements discussed below.
The Open Platform terms distinguish third-party applications from DeepSeek's consumer chat. The chat privacy policy alone does not establish the conditions for BreederControl users' data. This draft does not promise that the API neither retains data nor uses it for training, and does not establish that a transfer is valid. Those contractual and technical details must be confirmed before personal data is sent.
Google, Stripe, Cloudflare and other providers may process data outside Argentina or the user's country. We do not claim all data remains in Argentina. Actual destinations and safeguards must be disclosed when each integration is enabled. An adequacy decision, approved contractual clauses or another valid legal mechanism must apply where required. General acceptance of these documents does not replace a valid transfer basis or specific consent where required. Reference: AAIP — international transfers.
7. Cookies and similar technologies
The landing page uses bc_locale to remember your chosen language for up to 365 days from selection. Starting Google sign-in creates bc_oauth, lasting at most 10 minutes, to bind and validate the authentication callback. Successful sign-in creates bc_session, identifying an application session for at most 30 days. Authentication identifiers use HttpOnly cookies and Secure on the HTTPS origin. Signing out invalidates that server session and removes its cookie. You can delete cookies in your browser; public reading remains available and private pages will require sign-in again. Each language also has a direct URL.
We do not implement our own analytics or advertising tools. Cloudflare participates in connections and may process technical data under its services. Optional future technologies require prior disclosure and any applicable choices or consent before activation.
8. Retention, closure and security
Information will be kept only as needed for its disclosed purpose, the user relationship, rights requests and applicable legal duties. Specific periods for records, conversations, files and any backups must be defined and communicated before enabling those functions; this draft does not invent a uniform retention period.
Cancelling payments does not automatically delete all data; closing an account does not require deletion of records that must legally be retained. Deletion exceptions must be limited to their actual purpose and duration.
Appropriate technical and organisational measures must be applied to the data and risks concerned, including access restrictions and confidentiality. This draft does not certify that all planned controls are implemented. No system is completely risk-free; incidents must be addressed and communicated where required by applicable law.
9. Rights and requests
Write to [email protected], stating your request and enough information to locate the record. An active account is not required. Proportionate identity verification may be needed to protect data, without requesting passwords or excessive information.
Under Argentine Law 25,326, rights include information, access, rectification, updating, deletion where applicable and confidentiality. Access must be answered within 10 calendar days and is free at least every 6 months, or sooner where justified by a legitimate interest. Applicable rectification, updating or deletion must take place within 5 working days of the request or discovery of the error. Legal exceptions to deletion must be explained and do not justify rejecting all requests.
Complaints may be made to Argentina's supervisory authority, the Agencia de Acceso a la Información Pública (AAIP), or through the relevant courts. Additional rights under other applicable laws will be handled according to their requirements and time limits; the selected language does not itself determine applicable law.
10. Children and automated decisions
The service is not directed at minors lacking capacity to contract. Their personal data must not be uploaded without necessity and a lawful basis. Suspected improper records can be reported to the privacy contact for assessment and appropriate action.
Assistants are intended as support and their responses require human review. They are not planned for solely automated decisions producing legal effects on people. Any proposed change to that use requires prior disclosure and legal assessment; this document does not presume authorisation.
11. Changes and versions
The policy will be available in Spanish, English, Russian and Brazilian Portuguese with equivalent scope. Its version and effective date must be stated on publication. Material changes must be communicated appropriately, and new purposes need a valid legal basis before use. Version 0.1 describes planned processing and outstanding details; it does not claim that every feature or safeguard is already implemented.
See also the Terms and Conditions.