Aerava Privacy Policy
This Privacy Policy explains how Tempo Quest, Inc. (“TempoQuest,” “we,” “us,” or “our”) collects, uses, shares and keeps personal data when you use Aerava (the “Service”): the website at aerava.ai, the Aerava app, and the emails it sends. The “Book a live demo” form has its own privacy notice for demo requests, which adds to this policy. If you or your organization have a separate written data processing agreement with Tempo Quest, Inc., that agreement controls where it conflicts with this policy.
1) Who we are
The controller of your personal data is Tempo Quest, Inc., 1434 Spruce St., Suite 100, Boulder, CO 80302, USA. Contact: support@tempoquest.com.
2) The short version
- Aerava is a business service, for people aged 18 or over who act for a business or organization.
- To create an account we ask only for your email address and a password. We do not ask for your name, company, job title, phone number or postal address.
- The Service stores the sites you save, including their locations, and the forecasts you order.
- We use no analytics, advertising or tracking cookies, and Aerava’s notification emails contain no tracking pixels.
- We do not sell your personal data or share it for advertising.
- Aerava’s database, forecast computing and file storage are in the United States.
- You can ask us at any time to see, correct, export or delete your data (Section 13).
3) What we collect
- Account data: your email address; your password, which our sign-in server stores only as a one-way hash; a random account ID; the times you signed up, confirmed your email and signed in; and your plan, subscription status and credit balance.
- Legal acceptance records: your account ID, which versions of the Terms and this policy you accepted, and when we recorded it. We do not record your IP address or browser details with it.
- Sites and location data: for each site you save, its name, type and location (latitude and longitude), an optional radius, heights and display units, the limits you set (including any reference, revision and “issued by” notes you enter for a limit), details for its type (such as turbine count, rotor diameter and cut-out speed; crane boom-tip limit; or runway heading, length and crosswind limit), and storm thresholds. Each time you save a site, we keep the earlier version as history, including earlier locations. A site can be a home: setup offers a “Home” preset, so a saved location may show where a person lives.
- Before you sign up: on the setup page (/start), your draft site (map pin, site type, name and settings) and the email address you type are kept only in your browser until you sign up and save (Section 7). Text you type into the place search is sent from your browser to MapTiler to find the place.
- Forecast requests and runs: the product, site, area (a point or a box), forecast length, model cycle, output heights and other settings you choose; the quote; and run records such as status, times, error codes and processing job IDs. The input files we prepare for a run include the location of its center. For most products, these files and the run’s outputs are stored under your account ID; for the worldwide preview, they are stored under the run’s own ID or a content hash of its plan. Cached terrain files may be prepared from the run’s location and stored under your account ID.
- Outputs: the forecast files, maps, tables and data packs produced for your runs, stored as described in the previous item.
- Standing watch and Logbook: records of what Aerava’s checks found for each of your sites and forecast cycles, and the notes and decisions you add (free text, which can be linked to a site or run).
- Notifications: your notification settings; a different notification email address, if one has been set; your in-app notifications; and a log of the emails we send you (recipient address, type of email, the details used to write it, which can include a site name and location, and whether our email provider accepted it for sending). If a different notification address is set, we send to it without verifying it, and that address is stored in our email log.
- Billing data: your Stripe customer and subscription IDs, plan, subscription status, trial end and current period end dates, and a ledger of credits added, held, spent and returned, with the related Stripe invoice and payment IDs. Stripe collects your card and billing details directly; we never see or store your full card number.
- Technical data: your IP address, browser type (user agent), and the time of each request and the page or address requested. Our hosting provider and the AWS gateway receive these when your browser contacts them (Section 6). The AWS gateway’s access log keeps only a request ID, status and any gateway error message, not your IP address or the address requested. Requests reach our database gateway and sign-in server through the AWS gateway, which can pass your IP address on to them. Their operational logs keep your browser type and the addresses requested (which can include your account ID), and can also include your IP address. The sign-in server’s log also includes your email address. The sign-in server also keeps session records (your browser type and a network address, which can be your IP address) and a security log of sign-in events that includes your email address and can include your IP address. Section 9 says how long each is kept. Aerava’s own application tables do not store raw IP addresses. When you visit the aerava.ai home page, our hosting provider may also use the language your browser asks for and, for some countries, the country derived from your IP address to choose the language of that page. Logs from forecast runs can include your account ID as part of file paths, and may include details of the run’s area. Map requests to MapTiler, and image requests to TempoQuest’s AceCAST Cloud server, also reveal your IP address and browser type to those servers, and map requests reveal which area of the map you are looking at.
- Communications: emails you send to us and our replies.
We do not collect analytics or advertising identifiers. We do not ask for sensitive personal data, such as health or financial account details, and we ask you not to put any into site names, notes or other free-text fields.
4) Why we use your data, and our legal bases
Where data protection laws such as the GDPR or UK GDPR apply, we rely on the legal bases listed below. “Contract” means the processing is needed to provide the Service you signed up for, or to take steps you ask for before signing up.
- Create your account, sign you in and keep your account secure. Contract; legitimate interests (keeping accounts secure).
- Provide the Service: saved sites, forecasts, the standing watch, Weather Risk, the Logbook and your outputs. Contract.
- Show maps and find places you search for (through MapTiler). Contract; for the setup page before sign-up, legitimate interests (helping you set up a site you asked to set up).
- Send run, alert and low-credit notifications by email and in the app. These are on by default, and you can switch each one off on your Account page. Aerava may also show an in-app notice, which can’t be switched off, when the standing watch could not check your sites. Contract; legitimate interests (telling you about the sites and runs you set up).
- Send account emails, such as email confirmation and password reset. Contract.
- Take payments and manage trials, subscriptions and credits. Contract; legal obligation (keeping accounting and tax records).
- Record which versions of the Terms and this policy you accepted. Legitimate interests (being able to show what was agreed); legal obligation where it applies.
- Prevent fraud and abuse, keep the Service secure and fix faults, using logs and run records. Legitimate interests (a secure and reliable service).
- Where aerava.ai does this, show its home page in a likely language, using your browser language and, for some countries, the country derived from your IP address. Legitimate interests (a readable first page).
- Remember the language you picked on aerava.ai. Legitimate interests (showing the page in the language you chose).
- Answer your questions and your privacy requests. Contract; legal obligation.
- Comply with the law, enforce our Terms and deal with legal claims. Legal obligation; legitimate interests.
We do not use your data for advertising or marketing profiles, and Aerava does not send marketing emails. You need to give us an email address and a password to create an account; without them we cannot provide the Service. Where we rely on legitimate interests, you can object (Section 13).
5) Emails we send
- Notifications from Aerava: run finished, run failed, alerts from the standing watch, and low credits. They are sent through Amazon Simple Email Service (SES) from the no-reply address Aerava <noreply@wrfondemand.com>. Replies to that address are not read; write to support@tempoquest.com instead.
- Account emails: email confirmation and password reset, sent by our sign-in server through Amazon SES from the same no-reply address, noreply@wrfondemand.com.
- Payment emails: Stripe sends receipts and a reminder before a free trial ends, and may send other payment emails.
Aerava’s notification emails and its account email templates contain no images or tracking pixels, and we do not track whether you open notification emails or click their links. Amazon SES keeps a list of addresses that bounced or reported our emails as spam, so that we stop sending to them.
6) Who receives your data
We share personal data only as described here. Service providers process it on our behalf to run the Service.
- Amazon Web Services (AWS), United States. TempoQuest runs Aerava’s database and sign-in server itself, on a server in its own AWS account. They, the AWS gateway your browser uses to reach them, email sending (Amazon SES) and encrypted database backups (Amazon S3) are in the US East (N. Virginia) region. Forecast computing (AWS Batch), file storage for run inputs and outputs (Amazon S3) and run logs (Amazon CloudWatch) are in the US East (Ohio) region.
- Netlify, United States. Netlify hosts the aerava.ai website and runs the server functions that handle most of the app’s requests, such as saving sites, ordering forecasts, billing and notifications, so it receives your IP address and the details of those requests. Signing in, and reading your account record, go from your browser to the AWS gateway described above. Netlify’s servers may also choose the language of the aerava.ai home page from your browser language and, for some countries, the country derived from your IP address. Netlify may process this data in the United States and other countries.
- Stripe. Stripe processes payments and runs the checkout and customer portal pages. We send Stripe your account email, your account ID and the plan or pack you chose. You give your card and billing details to Stripe directly. Stripe also uses some data for its own purposes, such as fraud prevention, under its own privacy policy. TempoQuest uses one Stripe account for Aerava and for its AceCAST Cloud service.
- MapTiler (Switzerland). MapTiler provides maps, satellite imagery, terrain and place search. Your browser contacts MapTiler directly on the setup page and in the app’s map views (not on the aerava.ai home page). MapTiler receives your IP address, browser type, the site that made the request (aerava.ai), the map areas you view and any place-search text you type. Aerava sends MapTiler no other information about you or your sites.
- TempoQuest’s AceCAST Cloud. The storm map images on the Weather Risk page are loaded by your browser from acecastcloud.tempoquest.com, another TempoQuest system. It receives your IP address and browser type, but not your account details or site locations.
- Email providers: Amazon SES sends Aerava’s notifications and account emails. Emails you send to support@tempoquest.com are handled by TempoQuest’s email provider.
- Weather data providers receive none of your data. We download weather data from NOAA (including NOAA’s public data on AWS), the National Weather Service and the German weather service (DWD) as whole files, whole data fields or national feeds, and match it to your sites on our own systems. We do not send your site locations to them.
- Supabase. Our database and sign-in server use open-source Supabase software that TempoQuest runs itself. Supabase, Inc. does not host the Service and does not receive your data.
- Others, when necessary: professional advisers, auditors and insurers; authorities or courts where the law requires it or to protect rights and safety; and a buyer or successor if TempoQuest is involved in a merger, acquisition or sale of assets.
Within TempoQuest, only a small number of administrators can access Aerava’s production database, through AWS single sign-on and AWS access controls (IAM). The Service’s own server functions also reach the database, using credentials kept in our hosting provider’s protected settings. The database server also runs other TempoQuest databases, which are kept separate from Aerava’s.
7) Cookies and browser storage
Aerava uses one cookie and some browser storage, only for features you use. We use no analytics, advertising or tracking cookies, and no third-party scripts that track you.
- Cookie
nf_lang: remembers the language you pick with the language switcher on aerava.ai. Set only when you pick a language. Kept for 1 year. - Local storage
aerava-auth-v1: keeps you signed in (your sign-in tokens, account ID and email address). Removed when you sign out. - Local storage
aerava-auth-v1-code-verifier: a one-time security code created when you sign up or ask to reset your password, and used when you open the link we email you. Removed once the link is used in that browser. - Local storage
aerava.basemap.v1: remembers the map style you chose. Kept until you clear your browser storage. - Local storage
aerava-onboarding-draft-v1: your draft site from the setup page (map pin, site type, name, settings and the email address you typed). Removed after a successful save, and ignored once it is more than 7 days old. - Session storage
aerava.pending-signup-consent.v1: your email address, your acceptance of the Terms and this policy, and a random request ID, kept in that tab until you close it, so that your acceptance can be recorded when you confirm your account. - Session storage
aerava.pending-site-save.v1andaerava.pending-forecast-confirm.v1: keep a site save or a forecast order from being lost or repeated if the page reloads. - Session storage
aerava.stale-bundle-reload.v1: the time the page last reloaded itself to pick up a new version of the app, so it does not reload repeatedly.
Session storage is cleared when you close the tab. Stripe sets its own cookies on its checkout and portal pages, under its own policy.
8) Where your data is processed
Aerava is run from the United States, and its data is hosted there. Aerava’s database, sign-in server, forecast computing, file storage, backups and email sending run in AWS data centers in the United States. Netlify, which hosts the website and runs the app’s server functions, may process data in the United States and other countries. Stripe may process payment data in the United States and other countries, and MapTiler is based in Switzerland. If you use the Service from outside the United States, including from the European Economic Area or the United Kingdom, your data is transferred to and processed in the United States, whose data protection laws may differ from those where you live. The United States is not covered by a general adequacy decision of the European Commission, the United Kingdom or Switzerland. Our service providers process personal data under their own data processing terms. You can ask us for more information.
9) How long we keep your data
- Account data, saved sites (with their history), runs, Logbook, notifications and notification settings: while your account is open. We do not delete inactive accounts automatically.
-
Run files (stored under your account ID or, for the worldwide preview, under the run’s ID or
a content hash of its plan).
Section 17 of the Terms of Service gives the full rules; the rule for a
run depends on the plan your account was on when the run was made.
- Maps, charts, point series, the tables the app shows from those point series, and Logbook history: until you ask us to delete them or your account is closed.
- Raw model output and full data packages (including downloadable table exports) from runs made on Starter or with no plan (including after canceling): at least 30 days after the run, after which we may delete them.
- Raw model output and full data packages from runs made on Pro: while your account is on Pro (after 30 days they may be moved to archive storage) and for 90 days after your Pro plan ends, after which we may delete them.
- Run input files, which include the location of the run’s center, and cached terrain files prepared from it: no longer than your account, and we may delete them from 30 days after the run.
- Leftover files from a run that failed: we may delete them 7 days after it failed.
- Forecast quotes (which include the requested location): kept with billing and credit records, including after your account is closed, because they record the price of each run.
- Legal acceptance records: kept after your account is closed, for as long as we may need to show what was agreed, for example until legal claims about it can no longer be brought.
- Billing and credit records: kept after your account is closed, for as long as accounting, tax and other laws require, and while a dispute about a payment could still arise.
- Stripe records: kept by Stripe under its own policy. Closing your Aerava account does not delete your Stripe customer record automatically.
-
Server and security logs:
- Logs of the app’s server functions, kept by our hosting provider (Netlify): short-term, up to about a week.
- Logs of forecast runs (Amazon CloudWatch), which can include your account ID and details of the run’s area: 14 days.
- The AWS gateway’s access log (a request ID, status and any gateway error message, without your IP address or the address requested): about 90 days.
- The sign-in server’s security log of sign-in events, which includes your email address and can include your IP address: deleted after 90 days, including after your account is closed. Copies in our backups are deleted about 35 days later, when those backups expire.
- The sign-in server’s session records (your browser type and a network address, which can be your IP address): until you sign out or your account is deleted.
- Operational logs kept on our database server by the database gateway and the sign-in server. These record your browser type and the addresses requested (which can include your account ID), and can also include your IP address. The sign-in server’s log also includes your email address. These logs do not yet have a fixed deletion period: today they are kept until the software that writes them is reinstalled, for example during an update.
- Backups: we back up Aerava’s database every night to Amazon S3 in the US East (N. Virginia) region, encrypted. Backups include account and sign-in records. Database backups are deleted automatically about 35 days after they are made, so data deleted from the Service can remain in backups until then. Copies kept on the database server itself are deleted after a few days.
- Support emails: kept in TempoQuest’s mailbox for as long as they may be needed to help you, to keep a record of requests such as cancellations and deletions, or to deal with legal claims.
- In your browser: as listed in Section 7. Download links for outputs expire after a short time.
- Demo requests: as described in the demo-request notice.
10) When your account is closed
The Service has no button to close an account. Email support@tempoquest.com from your account email, and please cancel any subscription in the customer portal first; if one is still running when we close the account, we cancel it too. When we close an account, we delete:
- the account and its sign-in sessions;
- your saved sites, with their history;
- your runs, Logbook, notifications, notification settings, email log and subscription record;
- your run files: maps, charts, point series, full data packages, raw model output (including archived files), run input files (including worldwide-preview plans stored under a content hash) and cached terrain files.
We keep the following, for the reasons and periods in Section 9:
- legal acceptance records (your account ID and the versions you accepted), to show what was agreed;
- billing and credit records, including forecast quotes (which include the requested location), for accounting and tax duties and possible payment disputes;
- the sign-in server’s security log, which includes your email address and can include your IP address, until each entry is deleted 90 days after the event;
- backups, until they are deleted about 35 days after they are made;
- server and run logs, which can include your IP address, for the periods in Section 9 (the operational logs on our database server have no fixed deletion period yet);
- support emails, as described in Section 9;
- your Stripe customer record, which Stripe keeps under its own policy (closing your Aerava account does not delete it automatically);
- Amazon SES’s entry for your address, if it bounced or reported our emails as spam (Section 5).
If you ask us to delete your data, we will delete or anonymize it unless the law requires or allows us to keep it, and we will tell you what we kept and why.
11) Security
- Connections to aerava.ai and to our servers use HTTPS.
- Passwords are stored only as one-way hashes.
- Card details are entered only on Stripe’s pages and never reach our servers.
- Links to download outputs expire after a short time.
- Aerava’s data is kept in its own database, on a server in TempoQuest’s own AWS account. The server also runs other TempoQuest databases, which are separate from Aerava’s. Only a small number of TempoQuest administrators can access it, through AWS single sign-on and AWS access controls (IAM); there is no direct login to the server (Section 6).
- Database backups are encrypted (Section 9).
No system is completely secure, and we cannot guarantee the security of your data. If a security incident affects your personal data, we will tell you and the authorities where the law requires it.
12) Automated processing
Aerava automatically compares weather data with the limits set for your sites to give each site a status (Clear, Watch, Warning, Blocked or No data) and to send alerts. These are assessments of weather at your assets, not decisions about you. Some account features are also applied automatically, such as trial credits, saved-site allowances and limits that protect the Service from abuse. We make no decisions based solely on automated processing that have legal or similarly significant effects on you, and we do not build marketing profiles.
13) Your rights and how to use them
In the app, you can see your saved sites, runs, Logbook, notifications and transactions; edit your sites; change your notification settings; and reset your password. For anything else, including a copy or export of your data, a correction (such as a change of account email), deleting sites, notes or your account, or objecting to or restricting how we use your data, email support@tempoquest.com from your account email.
We reply to emails at support@tempoquest.com within 2 business days. We may need to confirm your identity before acting on a privacy request, and we will answer it within the time the law sets (for example, one month under the GDPR). Requests are free unless they are clearly unfounded or excessive. You may use an authorized agent where the law allows; we may ask the agent for proof that you authorized them.
14) More information for the European Economic Area, the United Kingdom and Switzerland
- You have the right to access your data, to have it corrected or erased, to restrict its use, to receive it in a portable format, and to object to processing based on legitimate interests. Where we rely on consent, you can withdraw it at any time.
- You can complain to a data protection authority, in particular in the country where you live or work, or where you think the law was broken. In the UK, that is the Information Commissioner’s Office; in Switzerland, the Federal Data Protection and Information Commissioner. We would appreciate the chance to help first.
- We ask you to accept this policy when you sign up so that we can record that you saw it. Our legal bases for using your data are the ones in Section 4, not that acceptance.
- This policy is in English only. Translated pages of aerava.ai are for convenience.
15) More information for California and other US states
- What we collect: in the last 12 months we collected identifiers (email address, account ID, IP address), customer and commercial records (plan, purchases, credit history and Stripe IDs), internet and network activity (request, session and security logs kept by us and by our hosting and infrastructure providers), geolocation data (the site locations you save, which may be precise), and the content of your communications with us. Sensitive personal information we collect is limited to your account login (email and password) and, where a saved site shows where a person is, precise geolocation. We use these only to provide the Service as described in Section 4, not to infer characteristics about you.
- Where it comes from: you, your browser, and Stripe (payment and subscription status).
- Who receives it: the service providers and others listed in Section 6, for the business purposes in Section 4.
- No sale or sharing: we do not sell personal information, and we do not share it for cross-context behavioral advertising. Because we do not sell or share personal information, a Global Privacy Control signal has nothing to opt you out of; we treat every visitor as opted out of sale and sharing. We have no actual knowledge of selling or sharing the personal information of anyone under 16.
- How long we keep it: see Section 9.
- Your rights: to know and access what we collect, to delete it, to correct it, and not to be treated differently for using your rights. Use them as described in Section 13.
- Other US states: if you live in a state with a consumer privacy law, you have similar rights. If we decline your request, you can appeal by replying to our decision, and we will answer your appeal within the time the law sets.
16) Children
The Service is for adults acting for a business or organization. It is not directed to anyone under 18, and the sign-up form does not ask for age. If we learn that we have collected personal data from a child, we will delete it. If you believe a child has given us personal data, contact us.
17) Demo requests
If you use the “Book a live demo” form, the privacy notice for demo requests explains what we collect, why, and how long we keep it. This policy covers everything else, including who receives your data, who can access it (Section 6) and your rights.
18) AI features
No feature of Aerava processes your text or your data with an AI language model today. Before we turn on any such feature, we will update this policy and name the provider. The standing watch uses StormScope, a machine-learning weather model that TempoQuest runs on weather data; it does not process your personal data.
19) Changes to this policy
Each version of this policy has a date and its own address. This version is at /legal/privacy-2026-10-06.html, and earlier versions stay published at their own addresses. When we publish a new version, your Account page will show it and ask you to accept it together with the Terms. For changes that materially affect you, we will also try to tell you by email before the new version takes effect.
20) Contact
Questions about privacy, or a request about your data? Contact support@tempoquest.com or write to Tempo Quest, Inc., 1434 Spruce St., Suite 100, Boulder, CO 80302, USA.