Skysta Terms of Use, what changed

Four things changed. Two of them are material, which means they change what you agreed to rather than only how it is written down. Thirteen people accepted the previous version of these terms, so this entry says exactly what moved.

• You now have to be 18 or older. The age question is gone. These terms used to set the floor at 13, with a higher floor in some countries, and the app used to ask for a birth month and year on the phone before it would let anybody in. The question has been removed from the app entirely, along with the two yes-or-no values it left on the device. The floor is now 18, everywhere, and it is a promise you make to us rather than a test the app runs. This is a material change and §1 is the whole of it.
• “Show on the map” now starts OFF, for everybody, on every photograph. It used to start on for adults, and off only for somebody the old age question knew was under 18. Nothing seeds it now. This publishes less about you, not more, but it changes what these terms describe, so it is written down here. This is a material change and §7 is the whole of it.
• These terms are now written for United States law only. Skysta will be available on the United States App Store and is not offered anywhere else. Everything that existed only for European Union or United Kingdom law has been removed: the digital-consent ages, the EU and UK consumer section, the Digital Services Act contact point, and the references to representatives that were never appointed. §15 now says plainly that Utah law governs and that the courts of Utah have jurisdiction.
• There is a copyright takedown section now, at §10.1. It says how to send us a notice, what a notice needs to contain, how to send a counter notice, and that we terminate repeat infringers. It also says plainly that we have not yet filed a designated agent with the United States Copyright Office, and does not claim a safe harbour we have not registered for. When that filing is made, the placeholder in §10.1 is replaced with the agent’s name and address and this section gets a new dated entry.

What did not change. Everything else. Skysta is still free. Your photographs are still yours, the licence you grant by sharing still covers only showing the sky inside Skysta, and it still ends when you delete the post. The seven days in the feed and permanence afterwards, the coarse cell on every shared sky, Remove the place, the reporting and blocking rules, the 24-hour moderation commitment, the dormant-backup rule and the deletion behaviour are all exactly as they were. We have not added an arbitration clause or a class-action waiver, and §15 says so.

Two things moved after the entry above was written, on the same day.

• “Show on the map” starts ON again. The entry above records the switch moving to off for everybody. That was reversed the same day. It now starts on for everyone, on every photograph, and you turn it off on the share screen when you would rather not publish the pin. Both entries stay here because both happened, and a change log that quietly tidies itself up is worth less than no change log. If you set your account up this morning and read that the switch started off, this is how you find out that it does not any more. This is a material change and §7 is the whole of it. Nothing was republished and no sky already on the feed changed.
• You can share one sky per capture window. That is a new rule and it is in §9. It limits what you publish, not what you photograph: private captures in your Journal are not limited at all.

What did not change. Every shared sky still carries the coarse cell of about 5.5 km whether the map switch is on or off, so turning the switch off has never taken a sky out of its Local area and it does not now. The cell is still never drawn on a map and it still never becomes a place name. The switch is still per photograph and still one tap either way. The spot tag still comes off with one tap. Remove the place (§7) still takes the pin, the town name, the spot tag and the coarse cell off a shared sky together, and it still cannot be undone.

The age floor goes back to 13. §16.1 above records it moving from 13 to 18 earlier today. That has been reversed, so the floor is 13 or older, which is what it was before this morning and what the thirteen people already using Skysta agreed to when they signed up.

So the material change §16.1 announced on this point has been undone rather than compounded. If you accepted the older terms, the age rule you agreed to is the one in force again.

It is still a promise you make rather than a test the app runs. Nothing about that changed. There is no age question in the app, nothing estimates your age, and email verification proves somebody can read a message, not how old they are. §1 is the whole of it.

One thing was added in the app because of this, and it is worth knowing about. “Show on the map” still starts on. But the first time you share a sky with it on, Skysta stops once and tells you plainly what publishing an exact pin means, and lets you share without it instead. Once you have answered that, it never asks again. It is a one-time explanation rather than a setting, and it does not change what the switch does or how it starts.

“Show on the map” starts OFF again. §16.1 records it moving to off. §16.2 records it moving back to on. This entry records it moving to off once more, which makes three settings of one switch in one day, and this is the one Skysta launches with. All three entries stay above this one because all three happened, and a change log that quietly tidies itself up is worth less than no change log. Nothing earlier in this section has been edited to look like it always said this.

This is a material change, and it goes in the direction of publishing less. Nobody reading this needs to worry that they have been publishing more than they thought. Nothing new is published by this change and nothing new is collected. A sky you shared earlier today carried a pin only if the switch was on when you pressed Share, and the share screen said in words what that meant, beside the switch, before you pressed it. Nothing was republished and no sky already on the feed changed. §7 is the whole of it.

How the switch works now. It starts off, for everyone, on every photograph. One tap turns it on for that one photograph, nothing remembers the answer, and the next photograph starts off again. Turn it on and the post carries the exact coordinate the photograph was taken at and the name of the town. Leave it off and it carries neither.

The one-time explanation from §16.3 is still there. The first time you turn the pin on and share, Skysta stops once, tells you plainly what publishing an exact pin means, and lets you share without it instead. Once you have answered, it never asks again. What it is for has shifted: when the switch started on it interrupted a default, and now it confirms a decision you made. It is still an explanation rather than a setting, and it still does not change what the switch does or how it starts.

What did not change. Every shared sky still carries the coarse cell of about 5.5 km whether the map switch is on or off, so the pin has never been what puts a sky in its own area, and turning the pin off has never taken a sky out of the Local feed of people near where it was taken. The cell is still never drawn on a map and it still never becomes a place name. The spot tag still appears on its own near a trusted spot and still comes off with one tap. Remove the place (§7) still takes the pin, the town name, the spot tag and the coarse cell off a shared sky together, and it still cannot be undone. A sky you keep in your Journal still publishes nothing about where it was taken. The age floor is still 13 or older (§16.3), Skysta is still free, and your photographs are still yours.

There is a third document now, and it is the short one. The Community Guidelines say in plain words what belongs on Skysta and what does not. They are not a new rule: every line in them is something these Terms already required or something the report sheet already asked you to flag. What changed is that you can now read the standard you are being asked to hold other people to, and that they are being held to.

If the Guidelines and these Terms ever seem to disagree, these Terms govern, and please write in so the mistake gets fixed.

The Moments feed is now three days long instead of seven. §6.6 says so, and so does the short version at the top. That is the whole of the change and it is the only number that moved.

A shared sky is still permanent, and this is the sentence to hold on to. Leaving the feed has never meant being deleted. A sky that leaves the feed moves, and it stays where it moves to: on your profile, where any signed-in account that taps your name can see your whole archive, oldest to newest, and on the page of the trusted spot it was tagged to, if it carries a tag. A shorter feed is a shorter time being news. It is not a shorter life for the photograph. Nothing is removed automatically, ever. There is still no timer anywhere in Skysta that takes a sky down, and the only two people who can take one down by hand are still you, at any time, from the ⋯ menu, and us, from outside the app, for the four reasons §6.6 lists.

The seven days in §6.3, §10 and §11 are Google’s, and they did not move. Google Cloud Storage still keeps a deleted photograph in a recoverable state for seven days before it destroys it. That window is about destroying a picture we deleted, not about how long a sky sits in the feed, and nothing here touches it. The one hour a deleted record stays readable and the thirty-day rule on our own dated copies are unchanged as well.

What this does to a sky you already shared. A sky more than three days old leaves the feed sooner than the earlier wording said it would. It goes exactly where it was always going to go, and it stays there for good: onto your profile, and onto the trusted spot’s page if it carries a tag. Nothing was republished and nothing was deleted, and no sky already on the feed had anything added to or taken off it.

What did not change. Everything else. Skysta is still free. Your photographs are still yours, the licence you grant by sharing still covers only showing the sky inside Skysta, and it still ends when you delete the post. The coarse cell on every shared sky, Remove the place, one sky per capture window, the reporting and blocking rules, the 24-hour moderation commitment, the age floor of 13 or older, the dormant-backup rule and the deletion behaviour are all exactly as they were.

Two sentences in §10 had fallen behind the app, and both have been corrected. Nothing in the app changed today; the words caught up with what shipped on 28 August 2026.

• Your profile picture is screened before we accept it. §10 said a profile picture was never checked and called that a gap. Since 28 August the avatar goes through the same on-device check a shared sky does, on the same terms, and is refused before anything is stored if the check flags it. The gap the old sentence described is closed, so the sentence is gone.
• You can report a person, not only a sky. §10 said there was nothing in the app to press about an avatar or a name on its own. Since the same day, tapping somebody’s name or picture on a sky they shared opens their page, and its ⋯ menu has Report this person and Block. The one limit that remains is now stated in its place: somebody who has never shared a sky cannot be reached from any screen in the app, and the answer there is still hello@skystaapp.com.

The Community Guidelines already described reporting a person from their page; these Terms had not caught up, and now they have. Nothing about the licence you grant, the rules in §9, the 24-hour commitment or what deletion reaches moved with this entry.

These terms were split into a short version and a full text. The page at skystaapp.com/terms/ is now a document of ordinary length, about three thousand words, and the text that used to be there, about eleven thousand, is at skystaapp.com/terms/full/. Every section of the short version points to the same numbered section of the full one, and the full one governs where they differ. This page, the record of every change, moved to skystaapp.com/terms/changes/.

Nothing in the agreement moved. No right, no rule, no number and no date changed. The age floor is still 13, Skysta is still free, your photographs are still yours, the licence you grant by sharing still covers only showing the sky inside Skysta, the feed is still three days, the coarse cell, Remove the place, one sky per capture window, the 24-hour commitment, the seven days, the one hour, the thirty days and the six months are all exactly as they were. The designated-agent box in §10.1 is still unfilled and still says so.

Why. The Terms of Use had grown to a hundred and ninety-five phone screens. A document nobody reads protects nobody. The short version keeps every promise and every warning; what it drops is the reasoning behind them, which is still in the full text for anyone who wants it.

A spot can now be suggested from the website. §8 gains one sentence in the short version and one paragraph in the full text saying that a suggestion sent from skystaapp.com/spots/suggest is on the same terms as one sent from the app: the same fields, the same confirmation that the place is public and safe, the same licence, and no obligation on us to publish, credit, or pay. A website suggestion has no account behind it and no status page, and the form says so before you send it.

Nothing else moved. No right, no rule, no number and no date changed anywhere else in these terms.

Two things about where a shared sky says it was taken. One is material: a shared sky now names its town, which it did not before unless you turned the map switch on.

Every shared sky now carries the name of its town. It is worked out from the coarse cell, about 5.5 km across, that a shared sky has always carried, and not from the exact point. Before this, the town went out only when Show on the map was on. You can turn it off, at Settings → Location & units → Name the town, and with it off no place name is published and no point is sent to Apple to be named.

What did not change with it. The exact pin is still the map switch’s alone, still off to begin with, and still a choice on every photograph. The coarse cell still goes on every shared sky either way, as it always has, and is still never drawn on a map. Remove the place (§7) still takes the pin, the town name, the spot tag and the coarse cell off a sky you already shared.

Show on the map can now be set to start on, at the same place in Settings. This is not material: it ships off, it changes only where the switch starts, and one tap on any photograph still decides that photograph.

§4 is reworded for both. It said the switch is “chosen per photograph and never remembered” and that turning it on is what publishes the town. Neither sentence is true any more, and a term that is nearly right is worse than one that is plainly wrong, because nobody checks it.

Nothing else moved. No right, no rule, no number and no date changed anywhere else in these terms.

Copyright notices go to a person, not to a process. The copyright section used to describe a United States DMCA notice-and-takedown: a designated agent, statements under penalty of perjury, a counter notice consenting to a federal court, and a citation to 17 U.S.C. §512(f). Skysta is not registered under the DMCA and does not claim its safe harbour, so that machinery was describing something that did not exist, and it asked you to swear an oath to report a stolen photograph.

It now says what is true: write to hello@skystaapp.com, Cy Liassides reads it, tell him what was taken and how to reach you, and he takes it down. The person who posted it is told and can reply. Accounts that infringe repeatedly are closed. Nothing was weakened by the change except the paperwork.

One correction to §16.10 above, and it is about the map. That entry says the coarse cell is still never drawn on a map. That stopped being true the same day it was written. A sky shared with the map switch off now appears on the map as a town-sized area, about 5.5 km across, with the town’s name on it. It is never a point. Nothing new is published; the map shows what the record already said. §7 has said so since 8 September. The entry above is left as it was written, because entries are never edited.

§7 is reworded. It said that leaving the map switch off publishes no place name, and that turning it on is what publishes the town. The town does not depend on the map switch: it is worked out from the coarse cell and published under Name the town. §7 now says that, and says that the cell is drawn on the map as a town-sized area.

§6.8 is reworded. It still described a sheet that asked whether to send the picture and told you when a sky was pinned. That sheet was removed on 7 September; sharing your own sky is one tap and nothing is asked. It also said the card carries the town a published sky was named with. The card takes its place name from the trusted spot tag only, and the town is not on it. §6 in the short version says the same.

§6.6 says how your profile page draws. It shows your newest sixty skies, and a spot’s page shows its newest forty. Older ones are not deleted and still open from their own link. Nothing about permanence moved.

The sky rating is gone, and so is the sentence in §11 saying a rating could not be removed even by hand. No part of the app asks how a sky turned out, and no rating is written anywhere. §12 no longer says that ratings ride with the app counts answer.

§11 names the Lock Screen record. Deleting your account also deletes the record behind the Lock Screen card, and stops if it cannot, because a server reads that record on a timer. The app already did this; the terms now say it.

§10 says the server removes a deleted photograph too. Whenever a shared sky’s record is deleted, from any door, our server removes its photograph, and tries again if that fails.

§12 names more of the services. Apple’s push service starts and ends the Lock Screen card with the app closed, Apple’s geocoder names towns, a scheduled Firebase function reads the card record, Firebase serves the website, and Google Maps can be your choice for directions to a trusted spot.

Settings paths. The block list is Settings → Blocked people, your suggestions are at Settings → Help → My suggestions, and feedback at Settings → Help → Share feedback.

The short version’s §11 now matches the full text: sections 3, 6.3, 8, 12, 13 and 15 survive the end of the agreement. The short version had said all of §6.

What changed in the app today, for the record. The sky rating is gone. The weekly note is gone. The camera-opens switch is gone from Settings, and the one-off reminder you arm from the shutter stays. Leave by is a switch, Tell me when to leave, rather than a timing choice. The record behind the Lock Screen card is described in full, with the end push the server sends. The six-cards rule is gone. The Device ID row on the privacy label is linked to you. The Privacy Policy’s changes page, at §16.18, has each of them. None of them changes a term.

Nothing else moved. No right, no rule, no number and no date changed anywhere else in these terms. Skysta is still free, your photographs are still yours, the licence you grant by sharing still covers only showing the sky inside Skysta, and the age floor is still 13.

§5 says how a trusted spot actually gets into the catalogue. It used to say only that we make a real effort to verify a spot’s coordinates and public access. That was true, and it was half the story. Each spot is researched first, from maps, satellite pictures and official park, city and land-manager pages, and then approved by a person one fact at a time. A fact about parking, hours, fees or hazards only reaches the app once a person has marked that they checked it, and a spot whose kind of public access nobody recorded is not published at all. Anything that looks closed, private or too hard to reach is turned down rather than published with a caveat. §5 says all of that now, in both versions.

And it says plainly that nobody goes to the place. The work above happens at a desk. “Verify” could be read as somebody standing at the overlook, and it never meant that, so §5 now rules it out in its own sentence rather than leaving it to be guessed.

The safety position did not change and was not softened. §5 still says, in the same bold as before, that we do not inspect trusted spots for safety and that we do not control them. It now adds that turning down what looks wrong is a screen and not a promise that a place we publish is safe. That is a limit on the new sentences, not a new promise. §13 is untouched, and no warranty is given anywhere in §5.

§8 says what verifying a suggestion means. It said we may verify, rewrite, move, or reject any suggestion. It now says verifying means reading public sources and checking the pin on a map from a desk, and that nobody goes to the place. What you confirm when you send one has not changed.

Is it material? No. It is a clarification. Nothing you may or may not do changed, no right changed hands, and the liability position is exactly where it was. It is written down here because this page promises every change is written down and dated.

Nothing else moved. No other section changed, no number changed, and no date in any other entry changed. Nothing about how a spot is reviewed changed either, only what these terms say about it. The community guidelines were reworded the same day to match, and they are not part of these terms.

Section 6 gains one paragraph, and it narrows rather than widens. You can now send a photograph from your journal to exactly one person without publishing it. The paragraph says what that grants us: the same licence as a share, limited to storing the picture and showing it to that one account and to you, ending when you take it back, delete the photograph, or delete your account. It says the community and reporting rules apply to it, and it says plainly that we cannot stop the recipient screenshotting it.

What did NOT change. Everything about sharing to the feed. Nothing about ownership: the photograph stays yours. No new right for us.

The effective date at the top moves to 15 September 2026 with this entry. The community guidelines gained one sentence the same day, saying they apply to a sky sent to one person, and carry the same date.

One sentence in section 6 was wrong for a day. The private copy of your journal has carried the coordinate since the morning of 15 September, and the short and full texts still said it was not part of the copy and was never uploaded. Both now say it is, readable by your account and no other, and point to the privacy policy’s 2.2 for why. Nothing about ownership or licence moved.

Also today: deleting a photograph you sent to one person now takes that copy back too, and account deletion sweeps those skies (section 11).

The effective date stays 15 September 2026.

This one takes things back, and that is the point. Section 10 made three commitments that nothing behind the app could keep, and they are now written as what actually happens.

The 24 hours is an aim, and the text says what is behind it. It used to read that reports of objectionable content ARE acted on within 24 hours. It now says we aim at that and in practice meet it, and then says plainly: one person reads the reports, from a queue that orders them oldest first and shows how long each has waited; there is no team, no rotation, no overnight shift; nothing alerts anybody when a report arrives. If that person is ill or travelling it takes longer. The commitment stays. The staffed desk it could be read as implying never existed.

There is no automatic receipt when you file a report, and the text used to say there was. “We confirm by email, to the address on your account, that your report reached us” was never true: nothing in Skysta has ever sent that email. What happens is that the app confirms on screen that the report was sent. When we have acted, a person emails you and says what was decided, and you can write at any time and get an answer.

The notice we send an author is written by hand. Section 10 still promises that if we act on something of yours we tell you what came down, the ground, and how to contest it. That promise is kept and is worth keeping. What is added is one true clause: a person writes that email, it is not generated and not sent automatically.

Why now. A review of the app against its own legal text found all three. They were made in good faith and never noticed, because nobody had asked what machine was behind each sentence. The tool the owner reads reports in now has a button for each email, prefilled, so the two promises that remain are one click rather than a blank page.

What did NOT change. Every rule about what may be posted, blocking, reporting, the seven day recovery window, and what deletion reaches. Nothing about ownership or licence. The community guidelines carry the same three corrections in fewer words and keep their date.

The effective date stays 15 September 2026.

Entry 16.11 said the formal machinery would come back when the filing was made. It has been made, and it is back.

Skysta is registered with the United States Copyright Office, registration number DMCA-1079417, effective 15 September 2026, with Cy Liassides as the designated agent. Section 10.1 now carries the formal route beside the plain one: what a notice under 17 U.S.C. §512(c)(3) must contain, including the statement made under penalty of perjury; what we do when one arrives; how to send a counter notification and what that must contain, including consent to a federal district court; and the 10 to 14 business day window in which material goes back up if nobody files an action. §512(f) is named, because a knowingly false notice is actionable and people should know that before they send one.

The plain route is unchanged and comes first. Write to hello@skystaapp.com and say what the work is, what is infringing it, that you can act for the owner, and how to reach you. No oath, no court, same result. Most people should use it. The formal route exists for anybody who needs the statute’s protections.

The agent’s address is published in section 17, because §512(c)(2) requires it to be somewhere public on the site, and it is in the Copyright Office’s public directory for the same reason.

One real change came out of writing it, and it is in your favour. Section 10.1 promises that a valid counter notification puts material back within 10 to 14 business days. That is about three calendar weeks, and the storage service keeps a destroyed file recoverable for only seven days, so the promise could not have been kept: the picture would have been gone before the window to answer closed. A takedown now DISABLES ACCESS and keeps the photograph rather than destroying it. The sky still comes off the feed, the profile and the spot gallery at once and no link reaches it. What changed is that a wrong decision, or a counter notification that arrives late, can now put the sky back exactly as it was. Sections 6 and 10 say so. Destruction is still what happens where destruction is the point: illegal material, or your own request to have a photograph gone.

What this changes for you otherwise: nothing. The registration changes what protection Skysta has if somebody sues over a photograph a user posted. It grants us no new right in your photographs, and section 6 is untouched.

The effective date stays 15 September 2026.

The registration in entry 16.17 has been amended, and section 10.1 no longer carries a date that would go stale.

What changed at the Copyright Office. The designated agent’s record now carries hello@skystaapp.com, the address this site has always published for copyright notices, and names the agent in full. The registration number is unchanged, DMCA-1079417. The Office stamped the amended designation 16 September 2026.

Nothing changed about who the agent is or how to reach one. Sections 10.1 and 17 have published the same name, postal address, telephone number and email since they were written, and those are what the Office’s public directory now shows. If you were ever going to send a notice, it goes to exactly the same place it did yesterday.

What changed in the text. The agent’s block in section 10.1 used to end “effective 15 September 2026”. That date described the first designation, and amending a designation gives it a new one, so the line would have been wrong again after the next correction. The block now gives the registration number and says the Office’s public directory carries the same details, which stays true however often the record is amended. The sentence above it still tells you the agent has existed since 15 September 2026.

Nothing else moved. No right, no promise and no obligation changed, and section 6 is untouched. The effective date stays 15 September 2026.

These terms were wrong about location for six days, and this entry says so rather than quietly re-describing them.

Section 7 and the full text both said the coarse cell, about 5.5 km across, is “what the town name is worked out from”. That stopped being true on 13 September 2026, when the app began naming towns from a separate, finer point rounded to about 1.1 km. The privacy policy was corrected that day and records it at its own §16.21. These terms were not, so for six days the two documents disagreed and these ones described a behaviour the app no longer had.

What the app actually does, and has done since 13 September. The cell it publishes is unchanged at about 5.5 km, it still rides on every shared sky with a coordinate, and it is still drawn on the map as a town-sized area and never as a point. The town name comes from a different point, about 1.1 km, which is sent to Apple’s geocoder to be named and is never stored and never published.

Why the app changed. The coarse rounding named the wrong town about one time in four. A photograph taken in Draper was published as Lehi because the rounding moved the question across a county line. A wrong town is a false statement about where somebody stood, published to strangers and kept.

Nothing else moved. No new recipient, no new stored value, and no change to what you control: Name the town still turns the name off, the exact pin is still the map switch’s alone and still off to begin with, and Remove the place still takes all of it off a sky you already shared.

Three additions, and Apple asked for all of them. Skysta’s forecasts come from Apple’s WeatherKit service, and the agreement that lets us use it says what the terms of an app or a website built on it have to contain. Ours were missing these.

• These terms now cover the website as well as the app. The opening paragraph used to be about the app alone, accepted by creating an account. It now covers skystaapp.com too, accepted there by using the website, because the Sky Score on the website is made from Apple’s weather data and Apple asks for terms wherever that data is shown. The website still asks nobody for an account.
• §4 now carries Apple’s notice, in Apple’s own words: YOUR USE OF THIS REAL TIME WEATHER GUIDANCE APPLICATION OR WEBSITE IS AT YOUR SOLE RISK. WEATHER DATA MAY NOT BE ACCURATE. Apple Weather Data may vary from actual conditions due to variable factors, such as signal issues and geopolitical events, that can affect the accuracy of Apple Weather Data. It covers the app and the Sky Score on skystaapp.com. §4 already said the Sky Score is a prediction and not a fact; this says the same of the weather data underneath it.
• §3 now says you may not reverse-engineer the weather data in the app or on the website, or the weather service it comes from, as well as the app itself. Apple’s agreement does not let us allow it.

None of this is material for anyone with an account. Nothing takes away anything the app or the website ever let you do, nothing new is collected, and the app works exactly as it did yesterday. Somebody who only visits the website is now covered by these terms too.

Two small changes, and neither is material.

• §12 now names the services the website uses as well as the app. Since 16.20 these terms cover skystaapp.com too, so the list of services we do not run now says that Open-Meteo also supplies the website’s cloud layers and its place search, and that OpenStreetMap names the town for a rounded position and OpenFreeMap draws the map of spots, on the website only. Nothing about what the website does changed; the Privacy Policy already described all of it.
• §10 now says that Cy Liassides reads copyright notices personally, in words that no longer use a pronoun for them.

The community guidelines were corrected the same day: §1 now says your public page shows how many skies you chose to share, and §7 no longer uses a pronoun for the person who reads reports. They are not part of these terms, and they carry the same date.

Nothing takes away anything the app or the website let you do, and nothing new is collected.

A review of these terms against the app, the website and the tools behind them found sentences that had stopped being true. Each is now written as what actually happens. Entries are never edited, so this one corrects 16.14, 16.15 and 16.16 where they no longer hold.

• A sky sent to one person is gone from these terms. Entry 16.14 added it on 15 September. The way to send one was taken out of the app the next day, before any version reached anybody, so nobody has ever been able to use it. §6 now says only a sky you have shared can be sent, and that Skysta has no way to send a sky privately to one person. The line entry 16.15 added, that deleting a photograph takes back a copy sent to one person, describes a part of the server that is still there for any sky made in testing.
• The card your own sky sends is described as it is. Since 16 September 2026 it carries the photograph, your name and profile picture, and whether it was a sunrise or a sunset. It no longer carries the Sky Score, the light or the spot’s name, and the Sky Score was never public on the sky. The light travels as one line in the message. The button is called Send this sky, and a sky kept in your Journal cannot be sent. §6.
• Apple accounts see the name screen. Since 28 August 2026 the app does not take your name from Apple; it fills it in as a suggestion you can change. §2 said Apple accounts usually skip that screen.
• Our dated database copies do get deleted. §6.3 and §11 said the thirty-day rule had never deleted anything. That was true until 20 September 2026. Since then the oldest copies age out on their own, and the tool runs all the time rather than when it is opened.
• The report queue lists the newest first, not the oldest, and a check three times a day puts up a notification when a report is waiting. Entry 16.16 said otherwise. §10.
• A picture we take down stays at its own address. No screen or link in Skysta shows it, but somebody who already holds that address can still open it until we destroy it or put it back. Its record is kept where no copy of the app can read it. §10.
• §7 named the town from the wrong point in one sentence. It comes from the finer point, as the rest of §7 says.
• §12 counts the app’s events honestly: nine of our own, plus a few Firebase records by itself. It also names the server job that removes a deleted sky’s photograph and OpenStreetMap’s map under the website’s.
• §4 says what happens without an air-quality reading: the score judges haze on visibility alone and says so, rather than showing nothing.
• Who these terms are for. The app is offered only in the United States. The website, whose Sky Score works for any place and whose home page shows cities around the world, can be read from anywhere, but Skysta is run from the United States, under United States law, and is not aimed at people in any other country. The top of these terms, §1 and §17.
• Smaller additions. §8 says a suggestion can be best at both lights, that a website suggestion can carry an email address for a reply, and that sending a suggestion is the promise that it is public and safe. §10 says a block also covers a person’s page, links and your Lock Screen card. §11 says deletion also needs your online record gone, tries to disconnect Sign in with Apple, and does not reach a sky we took down. §14 carries Apple’s full wording on embargoes and on Apple’s right to enforce these terms, and §17 says questions, complaints and claims can also go by post or phone. §10.1 follows the statute’s own words on contact details and service. §6 names Make private beside Delete, says the licence covers Skysta’s Lock Screen card, which can show other people’s skies, says what the top of your public page shows, and says we may use our access to put back a sky we took down.
• The full text no longer opens with its own summary. The short terms are the short version, and the website links the two. The full text’s first lines also said the short terms say the same things in a tenth of the words; they take a fraction of them, under half, so they now say that.

Nothing here takes away anything you could do, and nothing new is collected. The community guidelines were corrected the same day and carry the same date: their opening, §1, §3, §6 and §7 now say what the app and the person reading reports actually do, and their line about a sky sent to one person now says Skysta has no way to send one.

A few sentences had stopped being true, and now say what the app and the website do. Entries are never edited, so this one says what changed.

• The sensitive content check also runs when Communication Safety is on, not only Sensitive Content Warning, as the Privacy Policy already said. §10, in both the full and the short terms.
• An Apple account deleted inside two minutes of signing in is still sent through the Apple sheet when Skysta has been closed and opened since, because the app needs a fresh code from Apple to disconnect Sign in with Apple. §11.
• Remove the place is on the menu of a sky opened from the feed or your public page. §6, §7 and the short terms.
• The U.S. Geological Survey is named among the services Skysta relies on: on the website, the map’s new Satellite switch shows its aerial photographs. §12 and the short terms.

The community guidelines were corrected the same day and carry the same date: §7 now says the check runs when either setting is on.

Nothing here takes away anything you could do, and nothing new is collected.

Skysta now lets you thank somebody for a sky, and these terms say how that may be used. From the version of the app that brings them, tapping the heart on somebody else’s shared sky sends its author an appreciation: a private thank-you that only the two of you can see, and, if the author allows it, a notification saying so.

• Appreciations must not be used to harass anybody. Appreciating somebody’s skies over and over when they do not want it is misuse, under the same rule as any other harassment. §9, in both the full and the short terms.
• Blocking someone stops their notices. Once you block somebody, you are not notified about their appreciations and they are not shown to you. §10.
• The report and block tools you already have apply. From every appreciation in your Activity list you can reach Report and Block for whoever sent it, so a person who has never shared a sky can now be reported and blocked from there. §10.
• Deleting your account deletes the appreciations you sent and received. §11.
• §12 now says that Apple’s push service delivers the notification that somebody appreciated your sky, and that a Firebase server job records each appreciation and sends it.

The community guidelines were corrected the same day and carry the same date: §1 now says there are no public likes, no counts anyone else can see and no followers, and that an appreciation is a private thank-you only the sky’s author sees; §2, §5 and §6 say how the rules on harassment, reporting and blocking reach appreciations.

Nothing here takes away anything you could do. What an appreciation records, and who receives it, is in the Privacy Policy, entry 16.35.