Artemis Outdoors Privacy Policy
1. Who operates Artemis Outdoors
Artemis Outdoors is operated by Pixel Nomads, the personal information controller. Contact our privacy representative through the contact form.
This policy covers Artemis's web and mobile services and explains how we handle information under applicable privacy law, including the Philippine Data Privacy Act of 2012. Features and controls vary by platform and app version, and the app may not yet be publicly available on every platform. External providers apply their own policies.
2. Information we handle
- Account information: name, email address, account identifier, sign-in provider and authentication information. Firebase Authentication handles email and password sign-in and, on the web, Google sign-in. You can add a display name, an optional photo, your experience and pace, home region and a role.
- Personal records (private to you): hikes and notes, hike photos, conquered peaks and ascents, goals, equipment, personal budgets, saved peaks and trails, saved filters, your packing checklist template, settings, appearance choices and offline packs and kept routes saved on your device.
- Event participation: join requests, your self-reported experience, answers to organizer requirements and readiness questions, waitlist status, agreed price records, payment entries and optional payment proof images, attendance, pickup choices, event chat messages and announcement acknowledgments.
- Emergency contact: an optional emergency contact and medical note you enter. Event staff can read it only through a protected request for an event where you hold a place.
- Routes and community content: GPX files you upload and their sharing setting, peak and trail submissions, corrections and photos, reviews, group posts and group targets.
- Social features (only if you opt in): a public profile with the fields you choose, follows, blocks, items you share to the community feed, private messages and message pictures, and reports.
- Support and operations: feedback threads with the screen, platform and app version, notification device tokens, rate-limit counters, audit entries for sensitive staff actions and the status of account deletion jobs.
Provide only information needed for a feature. Do not put passwords, payment credentials, government identifiers or another person's private contact details into profiles, events, notes or chat. If you contact us, we also receive the correspondence you provide.
3. Location, photos, calendar and notifications
Location: Artemis reads your device location only while you are using a feature that needs it, such as sorting nearby events or following a route. It is not tracked in the background, and the position is read on your device and is not uploaded or stored by Artemis. A meeting point or pin that an organizer adds to an event is event information and is saved with the event.
Photos: Artemis asks for photo access when you choose pictures for hike memories, event covers, peak photos, message pictures or your profile. You can deny or revoke access in your device settings.
Calendar: if you choose to add an event to your calendar, Artemis creates and updates that entry. It does not read your other calendar entries.
Notifications: notifications appear in the app. Push notifications, where enabled by the operator, use your device's notification service and a stored device token. You choose which kinds you receive and can turn them off.
Artemis and its authentication services use device storage for sessions, preferences and caches. Clearing local data may sign you out or reset on-device preferences; it does not delete cloud records.
4. Purposes and processing grounds
We use account details to authenticate you; personal records to provide your tracker and recaps; event, registration, fee, checklist and attendance records to organize hikes; messages and announcements to coordinate participants; community content for moderated listings and sharing you request; and operational records for reliability, abuse prevention and security.
Depending on the purpose, processing of ordinary personal information rests on providing the requested service, legal obligations, consent or legitimate interests such as security, subject to your rights. Sensitive information requires a separately applicable legal ground. Consent, where relied on, can be withdrawn through the relevant control or by contacting us. Agreeing to the Terms does not give blanket permission for unrelated processing.
Readiness summaries, waitlist offers, capacity counts and achievements are feature calculations based on the information entered. They are not medical assessments, safety certifications or decisions about credit, employment or insurance. Organizers decide who joins their events.
5. Information other people can see
- Nothing is public by default. A public profile exists only if you publish one. It shows the name, handle and bio, and totals or badges only if you select them. A record appears in the community feed only when you choose to share it, with only the fields you select.
- Events and groups: your name and profile photo are shown to other signed-in people on events you join and in groups. Event chat is visible to eligible participants of that event.
- Organizers and event staff see your request, your answers to their requirements, your payment entries to them and your attendance, according to their role. They do not see your private hikes. Pickup group phone numbers are shared only with members of that group.
- Route links: a GPX file shared by link can be opened by anyone with the link until you reset the link, change the setting or delete the file. A public file can be seen by anyone.
- Private messages can be read only by the two people in the conversation. If someone reports a conversation, a copy of up to the last 20 messages is stored as evidence. Only Artemis moderators can open it, only for that report, and each time one does is logged.
Blocking a person removes follows between you and hides profiles and shared items in both directions. Recipients can keep screenshots or copies outside Artemis; we cannot directly remove those copies.
6. Providers and disclosures
- Google Firebase and Google Cloud: authentication, the application database, file storage, serverless functions and hosting. See Firebase privacy information and the Google Privacy Policy.
- Google sign-in (web): supplies the identity information you authorize through that service. Your Google account remains subject to Google's terms and controls.
- Push notification services: where push is enabled, notification delivery uses Expo's push service together with your device platform's notification service.
- Optional place suggestions: off unless the operator connects a provider. If one is connected, the point you search around is sent to that provider and only names and positions are kept from the response. No basemap tile provider or bulk map download is enabled by default. A configured satellite-image host can receive the displayed peak’s catalog position and normal image-request information, including IP address; this is not an upload of your live location. Optional place suggestions can send the searched point to a configured provider. Provider use and availability depend on the release and operator settings.
- Optional AI wording in Ask Artemis: available only if the operator enables and configures it. Each model request requires explicit consent for that question and sends the question plus up to three curated help topics to Anthropic. The request does not automatically attach profile, hike, event or private-message records. Information you type can still be personal or sensitive, so avoid including unnecessary details. Artemis does not intentionally save the help question/answer as a chat history; it does keep rate-limit counters, and the provider processes requests under its own terms and retention practices. See Anthropic's Privacy Policy. Curated help can be shown without a model request.
- External links: maps, organizer sites, shops and sources open third-party websites with their own privacy practices.
We may disclose relevant information when required by law or necessary and lawful to investigate abuse, protect people, or establish or defend claims. We limit disclosures to their purpose.
We do not sell personal information. Artemis does not run a third-party in-app advertising program. Necessary infrastructure processing still occurs.
7. Storage and security
Information is stored in cloud systems and, where needed, on your device. Providers may process information outside your country; locations depend on the configured service. We remain responsible for information under our control and use appropriate provider arrangements and access controls.
Workflow records such as events, registrations, payments, announcements and notifications can be changed only by Artemis's server functions, and database rules restrict who can read private and sensitive records. No system is completely secure. We investigate security incidents and provide notifications required by law.
8. Retention and remaining records
Private account records generally remain while needed for the requested feature, until you or an authorized process removes them. The implemented maintenance job targets private-message text and pictures older than 180 days and resolved message-report evidence 90 days after resolution. Unresolved reports remain for review. These are scheduled cleanup rules, not a guarantee that every copy, provider log or backup disappears at the exact same moment.
Deletion removes or clears many account records and de-identifies some shared event information, but some references can remain linkable. Organizer ledgers, registration document paths, event/group audit entries, approved listing claims, staff notes, reports about an account, editorial/import accountability records and deletion-job status are not all erased by the account job. Removing a displayed name is not necessarily irreversible anonymization, and no universal automatic expiry is implemented for every retained category.
We retain information only as appropriate for service operation, security, safeguarding, legal obligations or resolving disputes. Request review of identifying data that remains; we explain the purpose and period or criterion for any lawful retention. Shared use and a technical limitation do not create a blanket exemption from deletion. Providers and independent recipients can retain their own records under their policies. Recovery copies should not be used to restart unrelated processing of deleted data.
9. Account deletion and requests without the app
Open Profile → Delete account, resolve the listed blockers, sign in again if asked, and type DELETE MY ACCOUNT to confirm. The implemented request requires a sign-in from within the previous five minutes. Deletion is blocked by live organized events, groups you own with other members, active/paused series and shared budgets others still use; resolve or transfer the relevant responsibilities as the screen explains.
The server disables sign-in, records checkpoints and attempts to remove personal hikes, notes, photos, goals, equipment, personal budgets, settings, devices, notifications, saved items, follows, GPX files/share links, feed items, feedback and your private-message content. Other people's messages and shared records are treated separately. The device clears its account-scoped data after an accepted request, even if server cleanup is still running.
Registrations and payment records on other people's events can remain with the display name “Former member”; the job removes personal answers and attempts removal of payment-proof images. Event chat text can remain with attribution cleared, and past organized events can show “Former organizer”. Some identifiers, document paths, audit and administrative records remain; these are not guaranteed anonymous. See the retention section and ask us to review any remaining personal information.
A running job resumes unfinished checkpoints through scheduled retries. After 12 attempts, a job still incomplete is marked needs_attention and requires operator review. An in-app “Deletion has started” message is not proof of completion. If cleanup stalls, fails or its outcome is unclear, use the Account & Data Deletion page. Do not assume the process retries forever or restores information already removed.
The website form also accepts specific-data deletion and remaining-data review without app installation or sign-in. We verify ownership proportionately and aim to respond within 30 days after we can verify and understand the request, subject to applicable legal deadlines and explained limitations. Uninstalling is not account deletion. Deletion does not itself refund event costs, cancel an external arrangement or erase another provider's independent records.
10. Your rights
Subject to applicable law, you may request information about processing, access, correction, objection, erasure or blocking, portability and withdrawal of consent. Use the contact form to reach our privacy representative. We will explain any lawful restriction. You may complain to the Philippine National Privacy Commission and seek remedies available under law.
11. Younger users
Artemis Outdoors is intended for users aged 18 or older. An under-18 person must not independently create or maintain an account without the legally valid authorization and arrangements required under applicable law. A parent or legal guardian should contact us before providing a child's information or arranging account access.
This policy does not claim that Artemis has an automated age-verification or verified parental-consent system. Contact us if a child has provided information contrary to these requirements. We will investigate and arrange appropriate restriction, correction or deletion. An organizer's youth hike does not itself authorize creation of a child's Artemis account.
12. Changes and contact
We publish updated policies with a revised date. Material changes receive appropriate notice, and any consent required for a new purpose must be obtained before that processing. Contact Pixel Nomads through the contact form below.