TOS for api token in personal projects?

Support
,
#1

Hi Rubin Team, I have acquired a Rubin Token via the API aspect and have made a personal project that uses the SIA endpoint to fetch images in the i, r, g bands and composite together an RGB image (given a central coordinate, using DP1 data).

I have the project hosted as an Azure web app (at an obscure URL) and have added additional security checks to ensure the service can only be used by me at this point in time (additionally the token is in an Azure key vault and is not checked into any git history).

I would absolutely love to share this project with the community, use it as a portfolio booster, and/or open it up as a repo that others can contribute to (after some more modifications), but I want to make sure I’m not violating any TOS and using the token that I have responsibly.

Are 3rd party, OSS applications that utilize Rubin data with an api token allowed to be publicly shared? Is there a pattern or best practice for what “side-projects” can be worked on with the API aspect and/or who they can be distributed to?

I’d be happy to share further clarifying details and/or repository code as needed. This is a bit of a followup to this previous post I made earlier in the year: Plans on more API aspect tutorials? - #3 by JohnStorgion

Thanks,
John S

#2

Hi @JohnStorgion, thanks for this question. The Rubin images have a two-year proprietary period, and access to the Rubin Science Platform is also proprietary. “Proprietary” meaning, for Rubin data rights holders only (scientists/students employed/enrolled at US or Chilean institutes, and named member of international teams, doing non-profit scientific research). No data rights holder may use their RSP API key to give others access to the RSP, or access to Rubin data in the way that you describe.

Please review the Data Policy | Rubin Observatory for details.