Data Processing Addendum
Effective date: November 16, 2026 · Version 2026-11-17-draft
This Data Processing Addendum (“DPA”) is part of the Terms of Service between Infinity Services LLC (“Infinity Services,” “Processor”) and the organizer (“Organizer,” “Controller”). It applies to personal information about vendors and other people that the Organizer, its staff or its vendors put into InfiniMarket (“Vendor Data”). If this DPA conflicts with the Terms on data protection, this DPA controls.
1. Roles
The Organizer decides why and how Vendor Data is collected and used, and is the “controller” (or “business”) under applicable privacy laws, including the Minnesota Consumer Data Privacy Act and similar state laws. Infinity Services processes Vendor Data only on the Organizer’s behalf and is the “processor” (or “service provider”).
2. Details of processing
| Purpose | Providing the Service: vendor applications, document collection and electronic signatures, invoicing through the Organizer’s Square account, waitlists, email notices, and vendor tax reports. |
|---|---|
| People | The Organizer’s vendors and applicants, their contacts, and the Organizer’s staff. |
| Data | Names, business names, email, phone, mailing address, website and social handles, product descriptions, Minnesota tax ID numbers, application details, uploaded documents (such as insurance certificates and permits), electronic signature records including IP address and browser details, invoice and payment status. |
| Sensitive data | The Service is not designed for sensitive data such as health information or Social Security numbers. The Organizer will not ask vendors for it. Tax ID numbers are collected only for required tax filings. |
| Duration | For the term of the Organizer’s account, plus the deletion period in section 9. |
3. Infinity Services’ commitments
- Process Vendor Data only on the Organizer’s documented instructions, which are the Terms, this DPA and the Organizer’s use of the Service’s features, unless the law requires otherwise (in which case we will tell the Organizer first, if the law allows).
- Not sell or share Vendor Data, not use it for our own purposes or for advertising, and not combine it with data from other sources except as needed to provide the Service.
- Make sure anyone who processes Vendor Data for us is bound by a duty of confidentiality.
- Keep each Organizer’s Vendor Data separate from every other Organizer’s.
- Tell the Organizer if we believe an instruction breaks the law.
4. Security
We maintain reasonable technical and organizational measures appropriate to the data, including:
- Encryption of data in transit (HTTPS) and at rest by our hosting providers.
- Database row-level security that restricts every record to the Organizer it belongs to and the vendor it is about.
- Private file storage for uploaded documents.
- Square credentials stored only on the server and never sent to browsers.
- Least-privilege access for our staff, with multi-factor authentication on administrative accounts.
- Tamper-evident signature records that store the exact signed text and its hash.
- Daily database backups, each kept for 7 days, and access and error logs from our hosting providers.
5. Subprocessors
The Organizer authorizes us to use these subprocessors: Vercel Inc. (hosting), Supabase Inc. (database, authentication and file storage), Resend (email delivery) and Proton AG (our support email inbox, for vendor messages sent to us). We will have a written agreement with each that protects Vendor Data at least as well as this DPA, and we remain responsible for their work. We will notify the Organizer at least 30 days before adding or replacing a subprocessor. The Organizer may object on reasonable data protection grounds, and if we cannot resolve the objection, the Organizer may close its account and receive a refund of prepaid fees for the unused period.
Square is not our subprocessor. The Organizer connects its own Square account and has its own agreement with Square, and we send Square invoice information at the Organizer’s direction.
6. Security incidents
If we become aware of unauthorized access to or loss of Vendor Data, we will notify the Organizer without undue delay and within 72 hours, describe what happened and the data affected as far as we know it, take reasonable steps to contain it, and help the Organizer meet any obligation it has to notify vendors or authorities, including under Minn. Stat. § 325E.61.
7. Requests from vendors
If a vendor asks us directly to see, correct or delete their information, we will pass the request to the Organizer and not respond ourselves except to say we have done so. We will help the Organizer respond, taking into account the nature of the processing, including through features that let the Organizer view, export, correct and delete vendor records.
8. Assistance and audits
We will give the Organizer the information reasonably needed to show our compliance with this DPA and to carry out any required data protection assessment. Once a year, or after a security incident, the Organizer may ask reasonable written questions about our practices, and we will answer them in good faith. Any on-site audit must be agreed in advance, at the Organizer’s cost, and subject to confidentiality.
9. Return and deletion
The Organizer can export Vendor Data while its account is active. Within 30 days after the account ends, we will delete Vendor Data from the live Service, and it will be removed from backups as they expire, unless the law requires us to keep it. Signed documents may be kept longer only if the Organizer asks us to, or the law requires it.
10. The Organizer’s responsibilities
- Have a lawful basis for collecting Vendor Data and give vendors any notice the law requires.
- Collect only what it needs, and keep its staff accounts secure.
- Respond to vendor privacy requests, with our help.
- Make sure its instructions to us comply with the law.
11. Location
Vendor Data is stored in the eastern United States. We will not move it outside the United States without notice to the Organizer.