catch a rainbow support
Support
Need help with catch a rainbow? Send a message to support@catcharainbowapp.com.
Thoughtful questions, bug reports, and ideas are welcome. Please keep messages kind and constructive so the issue is easy to understand and the app can keep getting better.
Send feedback
Tell me what happened.
Use this form to send feedback to catch a rainbow support. Please include enough detail to help reproduce the issue.
Common questions
Why does the app ask for location?
The app uses location to estimate local rainbow conditions, calculate sun and weather factors, and show relevant nearby information. Locations shown on the map are general and do not show an exact photo location.
Why does the app use location in the background?
When enabled, location helps keep rainbow alerts relevant even when the app is not open. Rainbow opportunities can be brief, so alerts work best when they are based on the user’s general current area.
Why are rainbow predictions not guaranteed?
Rainbows require sunlight, water droplets, direction, timing, and visibility to line up at once. Weather can change quickly and across very small areas, so the app provides a helpful estimate rather than a guarantee. It must not replace official weather or safety information.
How do I delete my account?
Signed in users can open Settings in the app and choose the account deletion option. This permanently deletes the account and associated app data. Contact support if you need help completing the process.
Can I delete a photo I uploaded?
Yes. Users can delete their own uploaded photos in the app. You can also make a photo private if you prefer not to show it publicly.
How does the app help keep the community safe?
Safeguards include account based upload tools, photo visibility options, general map locations for privacy, duplicate checks, moderation tools, and ways to review or remove uploaded content.
How do I report a problem?
Use the feedback form above. Include a short description of the issue, the device you are using, and what you were trying to do when the issue happened.