{"version":"3.1","effective":"2026-11-04","text":"# AyWOS — Privacy Policy\n**Version 3.1 · Effective 2026-11-04**\n\n*What changed in version 3.1: Section 1 now describes two security records, the\nsecurity event log on your account and the security flags (our evidence of requests\nthat look like an attack), and Section 5 says how long each is kept. Nothing else has\nchanged.*\n\nThis Privacy Policy explains what information AyWOS LLC (\"Company,\" \"we\") collects\nthrough the AyWOS website at aywos.com, our\napplications, and services (the \"Service\"), how we use it, and the choices you\nhave. By creating an account, accepting this policy, or using the Service, you\nagree to it. If you do not agree, do not use the Service.\n\n## 1. Information we collect\n\n**Account information.** Email address and a one-way HASH of your password (we\nnever store your password itself), your role, account status, and timestamps.\n\n**Profile information (optional, provided by you).** Name, company,\ncountry/region/city, and work phone, if you choose to enter them.\n\n**Access-voucher information.** If your account was created with an access\nvoucher: the voucher id and the first and last name the voucher was issued to.\n\n**Legal-acceptance records.** When you accept the Terms of Use, this Privacy\nPolicy, or sign a Non-Disclosure Agreement, we record the version, timestamp, your\naccount email, device identifier, IP address, browser user-agent, and (for the\nNDA) the exact name you typed as your electronic signature and the approximate\ncity, region and country of the IP address you signed from (worked out on our own\nservers).\n\n**SMS consent records.** If you enroll for text alerts, we record — **from you\ndirectly** — your mobile number, the timestamp of your consent, the method and\nsource of enrollment, the IP address you consented from, the approximate city,\nregion and country of that address (worked out on our own servers), the exact\nconsent language displayed to you, and which alert categories you consented to.\nWe record each subsequent change, including any withdrawal of consent and the date\nand method by which it was received. These records are kept as evidence of consent.\n\n**SMS alert information.** Your name, mobile number, and the sites you subscribed\nto, for the alert categories you consented to.\n\n**Alert-programme release.** If you also sign the alert programme's separate\nassumption-of-risk agreement, we record the name you type as your signature, your\nfirst and last name, employer and role, the version of the agreement and a\nfingerprint of its exact wording, the time, the IP address you signed from, and an\napproximate city derived from that address.\n\n**Device/seat information.** A device identifier and label for each device you\nregister (this is how paid seats are counted), with first and last-seen\ntimestamps.\n\n**Seat activity.** For each licensed seat we record how many minutes per day that\nseat spent actively using the Service, on which device, and how many times it was\nopened. We do not record what was looked at: this is a meter, not a record of your\nwork. It is used to administer licences — to see whether a plan is being used,\nwhether seats are idle, and whether a contract is the right size — and it is visible\nonly to the master owner of AyWOS LLC. It is kept for four hundred (400)\ndays.\n\nWhere you use the Service under an organizational customer's plan, that customer is\nthe controller of this information about its own personnel and we act as processor;\nthe legal basis for our own administration of the licence is our legitimate interest\nin knowing whether the service we supply is being used.\n\n**Notification subscriptions.** If you turn on alerts in your browser, your browser\ngives us a push subscription: an address at your browser maker's push service and\nthe keys needed to encrypt messages to it. We keep it with your account email, the\nsites you chose, your browser's user-agent string, and when a message last reached\nit. If you use our mobile app and allow notifications, we keep the device token that\nApple or Google issues for the same purpose.\n\n**Work schedule (optional).** If you use Work schedule, we keep the days you mark as\n\"on rotation\", your choice between receiving lightning alerts always or only on those\ndays, and the time zone of the device you saved it on. We use them only to decide\nwhether to send you a lightning alert on a given day: on a day you have not marked,\nwhile you have chosen \"only on rotation\", no lightning alert is sent to you by text,\nWhatsApp, push or e-mail. You can change or clear your schedule at any time.\n\n**Lightning alerts by e-mail (optional).** If you switch them on, we send lightning\nalerts to your account's e-mail address, from lightning@aywos.com, for the same sites\nas your other lightning alerts. Each e-mail has a link to stop them; you can also\nswitch them off in Work schedule.\n\n**Position reports (optional).** Some plans include a crew-safety board that shows\nwho is at which turbine or asset. Your device reports its position (latitude,\nlongitude, accuracy and the time of the fix) only if you turn that feature on in our\nmobile app. We keep your most recent report and a log of when you arrived at and\nleft each asset. Members of your own organization's plan can see who is on which\nasset, and its administrators can see the arrival and departure log. No other\ncustomer can see either; our own staff can, when operating and supporting the\nService. You can see your own log in your account.\n\n**Technical logs.** Standard server logs (IP address, requested path, timestamp,\nstatus) and in-browser error reports (which include your account email when you are\nsigned in), kept for security and reliability.\n\n**Security event log.** To protect your account and to investigate misuse, we keep a\nrecord of security events on it: sign-ins (successful and failed), sign-in codes sent\nand used, the second sign-in step, password resets and changes, sign-outs, changes to\nyour role or access, device registrations and removals, and the deletion of the\naccount. Each record holds the time, your account email, what happened, the network\n(IP) address it came from and the device (its identifier and browser type). Only the\nAyWOS owner can see it.\n\n**Security flags.** To protect the Service, our servers check every request they\nreceive, whether or not the sender is signed in, for the signs of an attack, such as\nan attempt to inject code (for example through the sign-in or request forms), to\nreach files or data without the rights, or to take over an account. Ordinary use\nleaves no record of this kind. When a request looks like an attack, we keep it as\nevidence: the time, the network (IP) address and any other addresses the sender gave,\nthe registered owner, country and abuse contact of that network (looked up in the\npublic registration records of internet addresses, which receive only that address),\nthe account and device when the request was signed in, any e-mail address typed into\nthe form, the browser and its user-agent string, the request with every password,\ncode, token and other secret removed, and what the Service answered. Only the AyWOS\nowner can see it. We may give this evidence to law enforcement, and to the provider\nof the network the attack came from, to report and stop the attack.\n\n**Usage measurement.** We count visits to our website and use of our console so we\ncan see which pages and features are used and improve them. This is measured by our\nown software on our own servers: there is no Google Analytics, no third-party\nanalytics tag, no advertising network, and no data about your visit leaves our\nsystems. We do not set a cookie for it and we do not store your IP address or your\nbrowser's user-agent string. To tell one visit apart from another WITHIN A SINGLE\nDAY, our server computes a one-way hash of your connection using a random key that\nis generated for that day and destroyed two days later; once the key is gone the hash\ncannot be linked back to anyone, by us or by anybody else. What we keep is the page\nor view opened, how long it was open, the approximate country, a coarse device,\noperating-system and browser class, and the WEBSITE (not the full address) that\nlinked you to us. We also count visits by approximate state or province and city,\nas counts only: a state or city is never kept with the record of a visit. These\nplaces are worked out from the network (IP) address your device connects from, on\nour own servers, using a geolocation database we hold (the country may instead be\nsupplied by our hosting provider's network, which carries your connection to us);\nthe address itself is not stored and is not sent to anyone. A place worked out this\nway is approximate: it usually shows your internet provider's nearest hub, which for\nmobile and satellite connections can be far from where you are. It is never linked\nto your account or your name. If your browser sends a Global Privacy Control or Do\nNot Track signal, your visit is not counted at all. Detailed records are deleted\nafter ninety (90) days; beyond that we keep only counts, and the unlinkable\nday-hashes used to count unique visitors.\n\n**Feedback.** If you send us feedback or a problem report through the Service, we\nkeep what you write, any images you attach, your account email, and our replies.\n\n**Access and demo requests.** If you ask for access or a demo through our website, we\nkeep what you give us — name, email, company, country, work phone, the plan and\nnumber of seats you are interested in, how you would prefer to pay, and your message\n— with the IP address and browser user-agent string the request came from, and our\nnotes on it.\n\n**Information you enter about other people.** Some features let you record details\nof other people — for example a crew manifest with names, email addresses and phone\nnumbers, which the Service can send to them. Enter only what you are entitled to\nshare. For that information we act on behalf of the organizational customer whose\nplan you use (Section 3).\n\n**What we do NOT collect.** We do not collect your device's precise location (its\nGPS position) unless you turn on the position reports described above (wind-farm\ncoordinates in the Service are business data about sites, not about you). The\napproximate place we work out from your network address is described under \"Usage\nmeasurement\" and in the signature and consent records above. We do not collect\npayment card numbers (payments, when launched, go directly to the payment\nprocessor); we do not use advertising identifiers; and we do not run third-party\nadvertising or cross-site tracking of any kind. Our usage measurement is\nfirst-party and same-day only: nothing we record can follow you between websites,\nor from one day to the next.\n\n## 2. How we use information\n\nTo provide, secure, and operate the Service (authentication, seat licensing,\nfeature access); to send service messages you request or that the Service\nrequires (password resets, sign-in codes, text alerts you consented to,\noperational reports); to enforce our agreements and protect against fraud, abuse,\nand security incidents; to maintain legally required records, including consent\nand acceptance evidence; and to improve reliability. We do NOT sell or rent\npersonal information, and we do not share it for cross-context behavioral\nadvertising.\n\n**Mobile information.** No mobile information will be shared or sold to third\nparties or affiliates for promotional or marketing purposes. Mobile numbers and\nSMS consent are used only to deliver the alerts you consented to, and are shared\nsolely with the SMS carrier service needed to transmit those messages.\n\n## 3. Legal bases for processing (where GDPR or UK GDPR applies)\n\nWhere the EU or UK General Data Protection Regulation applies, we rely on:\n**contract** (Art 6(1)(b)) to provide the Service to you; **legitimate interests**\n(Art 6(1)(f)) for security, abuse prevention, and reliability; **consent**\n(Art 6(1)(a)) for text alerts, which you may withdraw at any time as described in\nSection 6; and **legal obligation** (Art 6(1)(c)) for retention of consent and\nacceptance records.\n\nWhere we process personal data on behalf of an organizational customer — for\nexample the details of that customer's personnel — that customer is the\ncontroller and we act as processor. **We will enter into a data processing\nagreement with any customer who requests one; contact\nadmin@aywos.com.**\n\n## 4. Service providers (processors)\n\nWe use a small number of infrastructure providers that process data on our\nbehalf: cloud hosting and database (Render), email delivery (our SMTP provider),\nand — if text alerts are enabled — an SMS carrier service (e.g., Telnyx) that\nreceives the recipient name and phone number needed to deliver the message.\nWeather data requests to our weather-data provider contain WIND-FARM coordinates\nonly, never your personal information. We work out approximate places from\nnetwork addresses ourselves, with a geolocation database we hold (IP Geolocation by\nDB-IP); no network address is sent to an outside geolocation service.\nIf you turn on notifications, alert messages are delivered through the push service\nrun by your browser or device maker (for example Google, Apple or Mozilla), which\nreceives the encrypted message and the subscription address it issued, and nothing\nelse. Providers are bound to use data only to provide their service to us.\n\n## 5. Retention\n\n| Category | Retention period |\n|---|---|\n| Account, profile and device data | While your account exists, then deleted within 30 days of account deletion |\n| Legal-acceptance records (Terms, Privacy, NDA) | Six (6) years from the end of the account relationship, as evidence of execution |\n| SMS consent and revocation records | Six (6) years from the date consent ended, as evidence of consent |\n| SMS subscriber entries (active list) | Until you withdraw consent or the feature is discontinued, then removed within ten (10) business days |\n| Server logs | Thirty (30) days |\n| Detailed usage records (page or view, time open, country, device class) | Ninety (90) days |\n| Unique-visit day-hashes (unlinkable once that day's key is destroyed, after two days) | Four hundred (400) days |\n| Aggregate usage counts (no identifier of any kind) | Retained indefinitely |\n| Seat activity records (minutes per licensed seat per day) | Four hundred (400) days |\n| Notification subscriptions | Until you turn notifications off, the push service reports the subscription as expired, or your account is deleted |\n| Work schedule and e-mail alert choice | Until you change or clear them, or your account is deleted |\n| Most recent position report | Until your next report replaces it, or your account is deleted |\n| Asset arrival and departure log | Twelve (12) months |\n| Feedback, attachments and replies | While your account exists, then deleted with it |\n| Access and demo requests | Until you ask us to delete them, or your account is deleted |\n| In-browser error reports | Ninety (90) days |\n| Security event log, with network addresses | One (1) year from the event, also after the account is deleted |\n| Security flags (evidence of suspected attacks) | Two (2) years from an incident's last activity; an incident reported to the authorities, until the matter is closed |\n| Other security and incident records | Two (2) years |\n\nWhere a longer period is required by law, by a legal hold, or to establish,\nexercise or defend legal claims, we retain the relevant records for that longer\nperiod and delete them when it ends.\n\n## 6. Text alerts: your consent and how to stop them\n\n**How consent works.** We send text alerts only to a person who has consented\ndirectly to receive them. An administrator at your organization may invite you,\nbut **your consent is given by you, to us, and is recorded as described in\nSection 1.**\n\n**Separate categories.** Where we offer more than one category of message, we ask\nfor and record your consent separately for each. Consent to one category is not\nconsent to another.\n\n**How to stop them.**\n\n- You may withdraw consent **by any reasonable means**, at any time.\n- Replying with **STOP, QUIT, END, REVOKE, OPT OUT, CANCEL or UNSUBSCRIBE** to\n  any message from us withdraws your consent.\n- **Other wording also works.** If you reply in any words a reasonable person\n  would understand as a request to stop, we will treat that as a withdrawal of\n  consent.\n- You may also withdraw consent by emailing **admin@aywos.com**, by\n  replying to any message from us, or by telling us by any other reasonable\n  method. **We do not require you to use any particular method, and we do not\n  designate any method as the only way to opt out.**\n- **We will honour any withdrawal within ten (10) business days of receiving it**,\n  and in practice we act sooner.\n- We may send you **one** message confirming that we have stopped, which will\n  contain no promotional content. If you consented to more than one category, that\n  message may ask which categories you meant, and we will stop all of them unless\n  you tell us otherwise.\n\n**If two-way texting is unavailable.** If we ever send from a number that cannot\nreceive replies, we will say so clearly in every message and give you an\nalternative way to opt out in that message.\n\n**You do not need to go through your administrator to stop messages, and we will\nnever refuse a request because it did not come through them.**\n\n## 7. Your rights and choices\n\n**Access and deletion.** You may delete your account at any time in the app\n(Account → Delete account); this permanently removes your credentials, profile,\ndevices and seats, active sessions, saved preferences, notification subscriptions,\nyour work schedule and e-mail alert choice, position reports and arrival log,\nseat-activity records, feedback and access\nrequests. You can also ask for deletion without signing in, at\naywos.com/account/delete. Legal-acceptance and consent records are retained as\ndescribed in Section 5. You may also contact us at\nadmin@aywos.com to exercise rights of access, correction, deletion,\nportability, restriction, and objection, and the right not to be discriminated\nagainst for exercising them, where applicable law grants them.\n\nWe respond to verified requests within the time required by applicable law — 30\ndays under the GDPR and UK GDPR (extendable by two further months for complex\nrequests, with notice), and 45 days under the CCPA/CPRA (extendable once by a\nfurther 45 days, with notice).\n\n**We do not \"sell\" or \"share\" personal information** as those terms are defined\nby the CCPA/CPRA, and we have not done so in the preceding twelve months.\n\n**Complaints.** If you are in the EU or UK you may lodge a complaint with your\nlocal supervisory authority. We ask that you contact us first so we can try to\nresolve the matter.\n\n## 8. Security and incident notification\n\nPasswords are stored only as salted PBKDF2 hashes; access tokens are opaque and\nexpire; privileged functions require elevated roles; and acceptance, consent and\nsecurity events are logged. No method of transmission or storage is completely\nsecure, but we apply administrative and technical safeguards appropriate to the\ndata we hold.\n\n**If a security incident affects your personal information**, we will notify you\nwithout unreasonable delay once we have determined that notification is\nappropriate or required, and in any event within the period required by applicable\nlaw. Where the GDPR or UK GDPR applies and the incident is a reportable personal\ndata breach, we will notify the competent supervisory authority within 72 hours of\nbecoming aware of it. Where we act as processor for an organizational customer, we\nwill notify that customer without undue delay so it can meet its own obligations.\nOur notice will describe, so far as known, what happened, what information was\ninvolved, what we have done, and what you can do.\n\n## 9. International transfers\n\nThe Service is operated from the United States, and your information is processed\nthere.\n\n**Where we transfer personal data from the European Economic Area, the United\nKingdom or Switzerland to the United States, we rely on the European Commission's\nStandard Contractual Clauses (Decision 2021/914), together with the UK\nInternational Data Transfer Addendum where the transfer originates in the United\nKingdom, supplemented by a transfer impact assessment. A copy of the relevant\nsafeguards is available on request from admin@aywos.com.**\n\nWe do not claim certification under the EU-U.S. Data Privacy Framework. We are not\nself-certified to it, and we will not state otherwise unless and until that\ncertification is actually completed with the U.S. Department of Commerce.\n\nWe do not currently offer the Service to individuals in the European Union, and we\nhave not appointed a representative under Article 27 GDPR. If we begin offering the\nService to EU data subjects, we will appoint one and name them here before doing so.\n\n## 10. Children\n\nThe Service is a professional tool intended for adults and is not directed to\nanyone under 18. We do not knowingly collect personal information from children.\nIf you believe a child has provided information, contact\nadmin@aywos.com and we will delete it.\n\n## 11. Changes to this policy\n\nWe may update this policy; the version and effective date above change when we do.\nMaterial changes are presented in-app for re-acceptance before continued\nsigned-in use, using the same mechanism as our Terms of Use. We keep superseded\nversions, and the version you accepted governs the period during which you\naccepted it.\n\n## 12. Contact\n\nAyWOS LLC · admin@aywos.com ·\n2222 W Grand River Ave STE A, Okemos, MI 48864\n\n==============================================================================\n"}