Privacy Policy

1. Who this policy applies to

This policy applies to visitors to our website, users of our web-based software at https://app.atmigrator.com, and anyone who contacts us (including via the contact form or lead flows on pricing). AT Migrator provides software and services to help organizations migrate from Airtable to PostgreSQL.

2. Key points

• We never store your migrated field values. We do not keep your Airtable cell values or any other values from fields you migrate (text, numbers, computed outputs, and the like) on our systems, except in transient processing needed to move that data to your PostgreSQL target (see section 4).
• Attachment files — your choice of storage path. At migration setup you choose either your own S3-compatible storage (files transfer directly to your bucket; we do not retain them on our systems except transient processing) or AT Migrator hosted storage (files stored on infrastructure we operate for the included period on your plan, then optionally on a monthly basis until you export or delete). See section 4.
• We use metrics, not your cell contents. We process counts and similar metrics (for example record counts, field counts) to help run migrations, monitor jobs, and for later product analytics; these are not your cell values (see section 5).
• We collect contact and business information when you submit website forms, so we can respond and run sales and support (see section 3).

3. Information you provide to us (business and support)

When you submit forms (for example “Contact,” email capture, or lead generation), we collect the fields you provide, which typically include name, work email, your message, and may include an optional phone number, company name, and plan or product interest. We use this information to respond to inquiries, perform contracts with you, operate sales, and support the Service. We store these submissions in our customer relationship systems (for example, Airtable) so our team can work your request.

Email and marketing. We may send transactional or service-related email (for example, in response to a form). Unless you have opted in to marketing communications where the law requires consent, we will not use your contact information for unrelated promotional purposes.

4. Migrated field values, attachment files, and processing

Field and cell values — we do not store. The Service moves data you authorize from Airtable into PostgreSQL. We do not store, log, or retain on our systems your table cell values or any other migrated field values (including text, numbers, dates, single- or multi-select values, and formula outputs) after the data has been written to your target or the migration path has completed, except only to the extent needed in transmission or volatile memory to perform the job you requested. Stated differently: we are not a database host for your migrated values.

Attachment files — two storage paths. File attachments are handled differently from ordinary field values because Airtable download URLs expire after a limited time (typically about two hours) and migrations may need stable file locations in PostgreSQL.

Path A — Your storage (direct transfer). If you connect S3-compatible object storage you control, attachment files are transferred directly to your bucket during migration. We do not retain those attachment files on AT Migrator systems except in transient processing needed to complete the transfer.

Path B — AT Migrator hosted storage. If you choose our hosted storage option, attachment files are stored on infrastructure operated for AT Migrator (including cloud object storage operated by subprocessors we use). This lets you complete migration without upfront bucket setup. Your plan includes a defined included hosting period (see our Pricing page). After that period, you may continue hosting with us for a monthly fee, or export files to storage you control at no charge. After a successful export, we delete hosted copies within a reasonable period consistent with our operational practices.

We do not use attachment file contents for marketing or unrelated profiling. We use access controls and encryption in transit and at rest for hosted files, consistent with industry practice for object storage.

Session and job processing. To run a migration, data may be processed in transmission, in working memory, or in temporary storage for the duration of the job, consistent with the paragraphs above. We do not use your migrated field values for our own marketing or unrelated profiling. We may retain metrics (see section 5) that describe volume and structure (counts), not the actual values in your cells.

5. Product analytics and operational metrics

We collect metrics and operational data that are not your cell or field values (see section 4). Examples include:

• Counts and quantities: number of records processed or migrated, counts of fields or of fields by type, and counts of attachment objects (not the files’ contents);
• Schema- or type-level information needed to map and complete the migration (for example field types);
• Migration assistance in real time: the same class of metrics helps us run, monitor, validate, and debug active jobs (for example progress and error classification);
• Later analytics: we also use aggregate or event-level metrics after the fact to understand product usage, capacity, and reliability, and to improve the Service;
• Job metadata: start and completion, success, failure, or error codes, duration, and performance signals;
• Version, platform, and configuration data needed to support and improve the product.

We never use these metrics as a substitute for storing your values. We do not use metrics to recover or store your Airtable or PostgreSQL cell contents. These metrics do not replace or replicate your customer database of values. Where an event is tied to a customer or workspace identifier to allow support or billing, we still treat the underlying field values and attachment handling as described in section 4.

6. Website analytics, cookies, and similar technologies

We use Microsoft Clarity (and, where we configure them, similar tools) to understand how visitors use our public pages and certain in-product flows (for example interaction patterns, so we can improve UX). Those technologies may use cookies or similar local storage and are subject to the provider’s documentation and settings. We configure such tools to focus on product improvement, not on collecting unnecessary personal information beyond what the provider processes as part of its service.

You may be able to control cookies through your browser. Where the law requires, we will obtain consent for non-essential cookies or analytics in line with the mechanism we make available in your region.

7. How we use personal information (lawful bases)

We use personal information for the following purposes, as applicable:

• Performance of a contract or pre-contractual steps—to provide the Service and respond to you;
• Legitimate interests—to secure the Service, prevent fraud, understand aggregate usage, support customers, and improve the product, where not overridden by your rights;
• Compliance with law—where we are required to retain or disclose data;
• Consent—where we ask for it (for example, certain marketing or optional non-essential cookies, depending on your region); you may withdraw consent where applicable.

If you are in the EEA, UK, or Switzerland, you may have additional rights under the GDPR or local law (see section 10).

8. How we share information

We do not sell your personal information. We may disclose information only as follows:

• Service providers. We use sub-processors (hosting, CRM such as Airtable for lead data, email, support tooling, and product analytics such as Clarity) that process data on our behalf in accordance with our instructions and appropriate contractual terms.
• Legal. We may disclose information to comply with law, valid legal process, or to protect rights, safety, and the security of the Service.
• Business transaction. If we are involved in a merger, acquisition, or asset sale, information may be transferred as part of that transaction, subject to safeguards consistent with this policy.

9. Retention

Contact and CRM records are kept for the period needed to serve our relationship, meet legal obligations, and resolve disputes, unless a shorter period is required by law.

Product and operational records (including analytics metrics described in section 5) are retained for as long as necessary for operations, security, and improvement, in line with our retention schedule and then deleted or aggregated.

Migrated field values (cells) are not retained on our systems as described in section 4. Attachment files on Path A (your storage) are not retained by us after transfer. Attachment files on Path B (hosted storage) are retained for your plan’s included hosting period and, if you continue, for the duration of paid monthly hosting, until you export to your storage or request deletion, after which we delete or overwrite them in line with our practices and the Terms.

10. Your privacy rights and choices

Depending on your location, you may have the right to access, correct, delete, or port certain personal information; to object to or restrict certain processing; and to obtain more detail about collection. To make a request, use our contact form and describe the request. We will verify and respond in accordance with applicable law. You may also have the right to complain to a supervisory authority.

11. United States: California and other state privacy

If you are a California resident, the California Consumer Privacy Act (as amended by the CPRA) may grant you the rights to know, delete, and correct certain personal information, and to opt out of “sale” or “sharing” (as those terms are defined in California law). We do not sell personal information for monetary consideration. If other U.S. state laws apply, we will extend comparable rights as required. Submit requests through our contact page. We will not discriminate against you for exercising privacy rights, where that prohibition applies.

12. International transfers

We may process and store information in the United States and in other countries where we or our vendors operate. If we transfer personal data from the EEA, UK, or Switzerland, we will implement appropriate safeguards, such as standard contractual clauses, where required by law.

13. Security

We implement appropriate technical and organizational measures designed to protect personal information. No system is perfectly secure; we work to keep risk commensurate with the nature of the Service and the data involved.

14. Children

The Service is not directed to children, and we do not knowingly collect personal information from anyone under 16. If you believe we have such information, contact us and we will take appropriate steps to delete it.

15. Changes to this policy

We may update this policy from time to time. The “last updated” date at the top will change when we do. We will post the revised version on this page and, where the law requires, provide additional notice for material changes.

16. How to contact us

Privacy-related questions and requests: Contact. We will route your inquiry to the appropriate person internally.

Legal notice. This document is a privacy disclosure for the Service described on this site. It is not legal advice, and it does not create rights for third parties. A qualified attorney should review this policy, your use cases (including if you process personal or regulated data), and any agreements you sign with AT Migrator.