Privacy Policy
Wiredrag ApS
1. Who we are and what this policy covers
Wiredrag ApS (“Wiredrag”, “we”, “us”) sells an API that reads a snapshot of a customer's source code repository and answers questions about every place a named value is held, passed or stored in it. To do that we receive the snapshot, read it with our own models and return an answer that lists files and lines. This policy explains what personal data we handle when we do that, and why.
Registered at Havnegade 20, 8000 Aarhus C, Denmark.
We handle personal data in two different situations, and different rules apply to each:
| Whose data | Our role | What applies | |
|---|---|---|---|
| Part A | People who visit this website, ask about the service or write to us | Controller: we decide why and how the data is used | This policy |
| Part B | Staff of our customers who hold accounts and keys with us; and people whose names or contact details appear incidentally in the source code a customer sends, such as an author named in a code comment, an owner listed in a CODEOWNERS file or an address in a configuration file | Set out in B.1, because it depends on the data | This policy and the data processing agreement we sign with each customer |
If the data processing agreement (“DPA”) and this policy ever disagree about Part B, the DPA wins.
2. Part A: this website and our contact with you
This part covers the personal data we collect for our own purposes: running this website, answering requests, and staying in touch with people who are or might become customers.
A.1 What we collect
What you give us. When you send the form on this site, we collect what you type into it, such as your name, email address, phone number or company, and the fact that you agreed to be contacted. If you email or talk to us, we keep that correspondence and any contact details in it.
What is collected automatically. Our web server records the IP address a request came from, the browser used, the pages requested, the page you came from and the time. These logs exist to keep the site running and secure.
We don’t ask for sensitive data (the “special categories” in Article 9 GDPR) through this website, so please don’t send any through the form.
A.2 Why we use it, and what allows us to
| Why | What | Legal basis (GDPR Art. 6) |
|---|---|---|
| Answering your request and working out whether the service fits | What you sent in the form, our correspondence | Art. 6(1)(b): steps you asked for before a contract |
| Looking after customers, billing and support | Contact details, correspondence | Art. 6(1)(b): carrying out a contract |
| Keeping the site running, secure and free of abuse | Server logs | Art. 6(1)(f): our legitimate interest in running a secure service |
| Contacting you about the service | Email address, company | Art. 6(1)(f): our legitimate interest in business-to-business marketing. You can object at any time |
| Meeting tax, accounting and legal duties | Billing and contract records | Art. 6(1)(c): a legal obligation |
Where we rely on legitimate interest, we have weighed that interest against your rights, and you can ask to see the assessment.
A.3 How long we keep it
- Requests from people who don’t become customers: 12 months from our last contact, then deleted.
- Customer contact and contract records: for the length of the agreement plus five years for accounting records, counted from the end of the financial year, under Denmark's Bookkeeping Act.
- Server logs: 30 days.
- A record that you objected or opted out: kept indefinitely, so we can keep respecting it.
A.4 Your rights
If you are in the EEA or the UK, you can ask to see your data, correct it, have it deleted, limit or object to how we use it, get a copy you can take elsewhere, and withdraw consent where we rely on it. Write to [email protected] and we will answer within one month.
You can also complain to a data protection authority. If you are in the EEA, that can be the authority where you live or work.
3. Part B: data inside the service
This part covers the data that passes through the service itself: the repository snapshots a customer sends, the questions asked of them, the answers we return and the marks engineers set on those answers.
B.1 What we handle, and in what role
For snapshots, questions, answers and marks we act as a processor, on the customer's instructions and under the data processing agreement; the customer decides which repository and commit to send, what to exclude and what to ask. For account details we act as a controller. The service handles the following:
- Repository snapshots. The files of one repository at one commit, sent as a git archive or fetched once with a read-only GitHub or GitLab token the customer supplies for that request. A snapshot carries no commit history. Source code can contain personal data incidentally: an author's name in a comment, a CODEOWNERS file, an email address in a configuration file, names in a test fixture.
- Questions, answers and marks. The question text an engineer sends; the answer we return, which holds file paths, line numbers, the one line of code cited at each hop and a one-sentence reason for each place; and any mark an engineer sets on a place. An answer repeats personal data only where a cited line contains it, and masks anything in a cited line that matches a known key or token format.
- Account details. The names and work email addresses of the people at the customer who hold keys, when each key was issued and revoked, a log of which key sent which snapshot and question and when, the monthly spending cap, and billing contacts.
We do not read commit history, issue trackers, chat, or any repository other than the one sent with the request. A read-only token is used for one fetch of one commit and then discarded; it is never stored, and we install no app and write nothing back to the repository.
We do not combine one customer's snapshots or answers with another's, and one customer's code is never used to answer another customer's question.
No one at Wiredrag looks at a snapshot or an answer in the normal course of the service. An engineer of ours sees one only when the customer asks us in writing to investigate a named answer and grants access to it; every such access is logged, and the log is available to the customer.
B.2 What we do with it
Reading. Each snapshot is decoded and parsed, files set aside by rule are listed with their reasons, and the remaining files are read in one context by our long-context model, with the answer collected directory by directory. All of this runs on cloud GPU capacity we control in Stockholm.
Checking. Every file and line the model cites is opened and checked by our parsers against the snapshot before a place is listed as found, and every name the answer uses for the value is searched for across the snapshot. No person reads a snapshot or an answer as part of this.
Deletion. A snapshot and the model's working state are deleted when its answer is returned, or when the last question held against it is answered, and never later than six hours after upload. Each snapshot is encrypted with its own key, which is destroyed at deletion, and snapshots are never backed up. Answers are kept for 90 days so that a re-ask can be compared with them, then deleted.
No onward sale. We do not sell, rent or share snapshots, questions, answers or marks. The subprocessors that host the service on cloud infrastructure in Stockholm, send our email and take payment are named on our subprocessor list.
B.3 AI models: where they run and what they learn from
Where models run. Every question is read and answered by our long-context reader, an open-weight code model we extended and fine-tuned ourselves, served on cloud GPU capacity we control in Stockholm. The parsers that check its citations run on the same cloud infrastructure in Stockholm. No snapshot, question or answer is sent to a third-party hosted model API at any point, and no such provider is on our subprocessor list for that reason.
Training. We do not train any model on a customer's snapshots, questions, answers or marks. The reader is trained on public open-source repositories only, and on a set our engineers build by hand: every-place questions asked of public repositories, each paired with its complete answer list, checked line by line. That set holds public code only, carries no customer identifier, is not shared with anyone, and trains our own reader and nothing else. From customers we keep only counts of marks by kind of hop and by language, which tell us where the reader lists too little, and they train nothing.
Where a person decides. The model proposes and the engineer who asked decides. A place is listed as found only when every hop from the value's source to it is cited at a file and line our parsers have opened and checked; any place short of that is listed as unconfirmed, with the boundary where its trace stopped, and is never dropped. The service changes no code and makes no automated decision with legal or similarly significant effect on any individual; every change made from an answer is made by the customer's engineers.
B.4 Where the data is kept
Every snapshot, question, answer and mark is stored and processed on cloud infrastructure in Stockholm, in Sweden. Answers and account details are backed up, encrypted, in the same place; snapshots are never backed up.
Payment details are held by our payment provider and never reach our systems. Our registered office in Aarhus holds no customer data.
The suppliers that handle data in the service are named on our subprocessor list, which comes with the data processing agreement and which we send to anyone who asks: write to [email protected].
B.5 How long we keep it, and what deleting can’t remove
A snapshot is deleted when its answer is returned, or, if the customer asked to hold it for further questions, when the last of them is answered, and in every case no later than six hours after upload. It is never backed up and never kept for training.
An answer is kept for 90 days after it is returned, so that a re-ask of the same question can say what changed; a re-ask's own answer is kept for 90 days from its return. A customer can delete any answer sooner through the API, and each deletion returns a notice with its time.
A mark an engineer sets on a place is kept with its answer and deleted with it. Beyond that we keep only counts of marks by kind of hop and by language, with no code, path, question text or customer identifier.
Account details and the request log are kept for the life of the account and 24 months after it closes. Invoices and the accounting records behind them are kept for five years from the end of the financial year they belong to, as Denmark's Bookkeeping Act requires.
B.6 Requests from people whose data is in the service
If your name or contact details appear in source code a customer sent us, that customer controls the code, and the snapshot is deleted within hours of arriving; write to the customer first. We hold such data afterwards only inside an answer that cites the line it is on, and on request we remove it from that answer. If you hold a key on one of our customers' accounts, write to us directly about your account details.
For everyone
4. Moving data between countries
Wiredrag ApS is a company in Denmark, inside the EEA. Section B.4 says where the data in the service is kept. If any personal data we control ever has to leave the EEA, for example because a supplier named on our subprocessor list handles it elsewhere, it is protected by the European Commission’s Standard Contractual Clauses or another safeguard the GDPR accepts. You can ask us for a copy.
5. Security
We protect data in line with the risk. That includes encryption in transit and at rest, access limited to the people and systems that need it, each customer’s data kept separate from every other’s, and a log of every access to production systems.
If a personal data breach affects you, we tell you without undue delay, and at the latest within 36 hours of finding out, with the information you need to meet your own reporting duties.
6. Children
The service is sold to businesses and is not meant for children. We don’t knowingly collect personal data from anyone under 16.
7. Changes to this policy
We may update this policy. If a change matters, we email customers at least 30 days before it takes effect. The version number and date at the top of this page change every time.
8. Contact
Privacy questions and anything else: [email protected]
By post: Wiredrag ApS, Havnegade 20, 8000 Aarhus C, Denmark