Pack'n'Camp — Privacy Policy
Version 1.6 — Effective date: November 13, 2026
Pack'n'Camp is a camping planning and organization application developed and operated by Sarp Süerdaş, an independent developer based in Türkiye.
This Privacy Policy covers Pack'n'Camp for Android and iOS. It explains what information Pack'n'Camp collects, how it is used, where it is stored, when it may be shared, and what choices you have regarding your information.
For privacy questions, contact info@packncamp.com.
1. Who Can Use Pack'n'Camp
Pack'n'Camp is intended for people aged 18 and older. It is not designed for children, and we do not knowingly collect personal information from anyone under 18.
An account is required to use the application, including when you choose to keep your camping data only on your device.
2. Information We Collect
Account information
When you create an account, we process your email address, account identifier, username and selected data-storage mode.
You may also provide optional information such as a display name, city and country.
We use this information to authenticate you, maintain your account and support the application's features.
Camping information
Pack'n'Camp allows you to organize camping trips, equipment, packing lists, vehicles, locations, photographs, checklists and camping history.
Personal camping records are stored locally on your device. Private cloud synchronization is not currently available.
Shared Camps
When you participate in Shared Camps, information needed for collaboration is stored in our cloud database. This may include camp names, dates, location descriptions, optional coordinates or map links, participant names, invitations, notes, shared equipment, responsibilities and completion records.
Other authorized participants in a Shared Camp may see information associated with that camp.
Shared Camp photographs are not uploaded to our cloud service.
Location information
With your permission, Pack'n'Camp may access your approximate or precise device location to display local weather, calculate distances and help you choose locations on a map.
Location access is requested when you use a relevant feature. Pack'n'Camp does not collect device location in the background.
When weather information is requested, geographic coordinates may be transmitted to Open-Meteo. Your Pack'n'Camp account identity is not included in these weather requests.
Feedback
When you send feedback through the application, we process your message, feedback category, application version, platform information and account email address.
Feedback is delivered to our support mailbox using Resend. Your email address may be used as the reply-to address so we can respond.
Crash diagnostics on Android
Android releases containing Firebase Crashlytics may record technical crash information locally on your device. This can include exception messages and stack traces, application and operating-system versions, device model, memory and disk information, and randomly generated diagnostic identifiers.
Automatic crash-report upload is disabled in the current Android configuration. The application currently provides no control that enables diagnostic uploads.
We do not add your email address, username, Pack'n'Camp account identifier, camping records, photographs or precise location as custom diagnostic fields.
Reports and safety records
When you report Shared Camps content or a participant, we process a report reference, the selected reason, relevant shared-content or account identifiers, and any explanation you choose to provide. Reports use our authenticated Feedback service. Support receives your verified account email when available so we can respond. The app does not automatically attach content excerpts, precise locations, photos or invitation tokens. Free-text explanations may contain personal information you enter; they are not automatically anonymized.
For safety investigations and appeals, authorized operators may review the reported shared material and necessary context. We keep limited restriction and enforcement records, including target identifiers, reason codes, decision/version information, case references, operator identity and timestamps. These records are personal data where linked to an account, even when they contain no name or email.
In the updated iOS app, unsent report drafts are encrypted and stored on the device for the relevant account. Closing the report screen keeps the draft. Confirmed delivery clears only the unchanged draft under its still-current account/session scope. Confirmed account deletion retires that account’s local report-draft encryption material. Reports already submitted to support follow the report/evidence retention schedule and exceptions described in this policy.
3. Where Your Information Is Stored
Pack'n'Camp uses a combination of local device storage and cloud services.
Personal camping records and photographs are stored on your device in this release.
Account information and Shared Camp records are stored using Supabase.
On Android, authentication sessions are stored securely on your device using Android's security mechanisms.
On iOS, account authentication secrets and account-specific local encryption material are protected using the Apple Keychain. This does not change the separately disclosed server-side handling of account and support data.
You can export your local information into a .pnc backup file or import a previously exported file. These exported files are not encrypted by Pack'n'Camp. You are responsible for keeping them in a secure location.
Android's automatic application backup and device-transfer backup are disabled for Pack'n'Camp.
4. How We Use Information
We process information to:
- Create, authenticate and maintain user accounts.
- Provide camping planning, equipment organization and logbook features.
- Enable Shared Camps and participant collaboration.
- Display maps, distances and weather information.
- Process invitations and account deletion requests.
- Respond to feedback and support requests.
- Maintain application security, prevent misuse and troubleshoot problems.
We do not sell your personal information.
Pack'n'Camp does not include advertising SDKs or advertising trackers. Google Analytics is not enabled. Android releases containing Firebase Crashlytics use it for technical crash diagnostics as described in this policy.
We use reports and limited enforcement records to investigate abuse, protect participants, apply and review Shared Camps restrictions, answer appeals, and meet applicable legal or security obligations. Reports do not automatically trigger disciplinary action.
5. Third-Party Services
Pack'n'Camp uses external services to provide certain features:
- Supabase: Authentication, account management, cloud database and server functions.
- Resend: Delivery of feedback emails.
- Open-Meteo: Weather information based on geographic coordinates.
- OpenFreeMap and OpenStreetMap: Map data and map tiles.
- Google Maps: Processing certain map links and displaying related content.
- Android system services: Location-related functionality, geocoding, photo selection, calendar integration and sharing.
- Apple platform services — iOS: Native maps, search and geocoding, foreground location when authorized, photo selection, calendar editing and document selection use iOS system interfaces. Map and search requests can contain the region, coordinates or search text needed by the selected feature. The app does not append Pack'n'Camp account credentials to these provider requests.
- Google Firebase Crashlytics — Android: Technical crash diagnostics, including required Firebase Installations and Firebase Sessions support libraries. Automatic report upload is currently disabled. If reporting is enabled in a future release, we will explain the information transmitted and obtain any required permission before enabling it.
These providers may process technical information necessary to deliver their services, such as IP addresses, request information or geographic coordinates.
Their handling of information is also subject to their respective privacy policies.
Weather providers receive requested coordinates and dates. Map providers receive requests identifying the viewed area and zoom. Requests also expose connection IP addresses and technical request information. These support delivery, troubleshooting and security; OpenStreetMap Foundation additionally documents summarized service-usage research and planning. Pack'n'Camp does not include account emails, account identifiers or camp titles in these requests.
Open-Meteo documents 90-day request-log retention. OpenFreeMap documents seven-day error logs and security IP logging for up to 30 days. The OpenStreetMap fallback follows OSMF's separate policy. Its stated 180-day detailed-usage retention concerns Piwik; it is not a verified universal retention period for raster-tile logs. Provider log periods do not establish complete residual-backup deletion deadlines.
These are provider-side processing purposes. They do not mean Pack'n'Camp includes an in-app analytics SDK or tracks general in-app activity.
Reports are delivered through our existing email delivery provider to our support mailbox. Report mail, necessary case evidence and operational case records are accessible only to authorized support personnel in our approved support workspace. Supabase stores the limited restriction and enforcement metadata needed to enforce Shared Camps rules. No new advertising or analytics service is enabled by reporting.
6. Sharing Information With Other Users
Shared Camps are collaborative spaces.
Information you enter into a Shared Camp may be visible to its authorized participants, including names, notes, camping arrangements and equipment responsibilities.
If a camp owner enables location sharing, the camp's coordinates or map link may be visible to the camp's authorized participants. Coordinates and map links are not shown in public invitation previews.
Anyone possessing a valid Shared Camp invitation link may be able to view limited invitation information, such as the camp name, dates, inviter name, participant slot names and participant count, before signing in.
Please avoid including sensitive personal information in shared notes or invitation details.
Reports, reporter email addresses and internal investigation evidence are not shared through Shared Camps with camp owners or reported users. Affected users may receive their own restriction reason, case reference and appeal instructions. Other affected participants may see only a general temporary-unavailability message. Participants may infer a report's source from circumstances; we cannot guarantee that identity cannot be guessed.
Blocking or enforcement may restrict live shared access without deleting original camping records, transferring ownership or rewriting already sealed personal history.
7. Data Security
We use measures intended to protect your information, including HTTPS connections, access controls and database row-level security. On Android, these measures also include encrypted local authentication sessions.
Access to cloud data is restricted according to account permissions and application functionality.
No system can guarantee absolute security. We encourage you to protect your device, email account and exported backup files.
8. Data Retention
We retain account and Shared Camp information while it is needed to operate the application, provide requested features and meet applicable legal or security obligations.
Feedback emails may remain in our support mailbox until they are no longer needed for support or legitimate recordkeeping purposes.
Technical logs and backups may be retained temporarily by our service providers or within our secured operational backups.
Retention periods can vary depending on the type of information, the service involved and applicable legal requirements.
Previously used usernames are permanently reserved to prevent their reassignment, including after account deletion.
Locally retained Android crash information is separate from your account-scoped camping records. It may remain until removed by the SDK or until the application's local data is removed.
For diagnostic reports transmitted to Firebase, Google documents retention of Crashlytics crash traces and associated identifiers for 90 days before beginning removal from live and backup systems. This is not a guarantee of complete deletion on day 90.
Active report emails, explanations and necessary case evidence are normally deleted from copies we control 90 days after final case closure, including any appeal. Minimal enforcement-audit records remain while needed for an active restriction and normally for 12 months after the later of restriction ending or final case closure. Current restriction state remains while effective. Any longer retention of active records requires a separately documented legal or safety reason and periodic review; provider backups alone do not extend these active-record periods.
Deleting an active copy starts a separate provider deletion/recovery lifecycle. Dropbox Professional normally retains deleted files and recoverable versions for 180 days; its normal deletion process follows the recovery window within 90 days, with possible additional processing time. Marking a file for permanent deletion starts server deletion and ends normal recovery, but is not an immediate all-backup erasure guarantee. Earlier versions created when a file is changed have a separate version-history lifecycle.
In Google Workspace Gmail, moving a message to Trash starts a normal 30-day Trash period. Removing it from Trash starts a further administrator recovery period of up to 25 days. Vault retention or holds may preserve copies longer. Google separately states that customer-deleted data is removed from its systems as soon as reasonably practicable and within a maximum 180 days; the end of mailbox recovery is not proof of residual-backup erasure. Archiving a message does not delete it.
Resend Free separately retains email content and logs for 30 days in its transport service; this is a transport-record lifecycle, not a period measured from case closure. Its point-in-time backups persist seven days. These separate periods do not establish a universal deadline for every copy. Account termination and dashboard account deletion have separate provider processes and are not our case-deletion procedure.
Actual recovery extensions, Vault rules, forwarding, exports and separate backups have not been verified for these accounts. We do not promise one deletion deadline across all providers, recoverable versions and residual backups. Known controlled copies remain subject to the active-record schedule; residual copies must not be restored or reused to extend it. Original camping records, including hidden shared records and sealed Logbook/completion history, follow their separate camping-data arrangements. Documented legal retention may also apply.
9. Account and Data Deletion
You can request account deletion from within Pack'n'Camp or by contacting info@packncamp.com.
When your account is deleted, the application removes your authentication account, account profile, cloud records associated with camps you own, and other eligible account-related cloud information.
However, some information may remain:
- Usernames previously associated with your account remain permanently reserved.
- Notes, invitations or participant names that you added to Shared Camps owned by other people may remain in those camps.
- Although these retained records are no longer linked to your account, their text or names may still identify you.
- Information in operational backups or records that must be retained for applicable legal or security reasons may remain for a limited period.
You can separately choose whether to delete local application data from your device when using the in-app deletion feature.
We aim to complete eligible account deletion requests within 30 days. This target does not override the retention exceptions described above.
Signing out or deleting your Pack'n'Camp account does not, by itself, remove separately retained diagnostic information. Such information follows the retention arrangements described above.
For information about deleting your account without accessing the application, visit:
https://packncamp.com/delete-account
Deleting your account does not automatically erase independently retained reports, appeal material or limited enforcement records that are still needed under the safety, legal and retention arrangements above. We assess deletion requests, minimize retained personal information where appropriate, and apply those retention limits. This does not change the existing disclosures about permanent username reservation or retained Shared Camps history.
10. Your Privacy Rights
Depending on the laws applicable to you, you may have rights to access, correct, delete or request information about your personal data, object to certain processing, or request data portability.
You may also withdraw location permission through your device settings.
To exercise applicable privacy rights, contact info@packncamp.com.
We may need to verify your identity before responding to requests involving account information.
11. International Data Processing
Pack'n'Camp is operated from Türkiye and uses third-party infrastructure and services that may process information in other countries.
When applicable, we take reasonable steps to address relevant data protection requirements for international processing.
12. Changes to This Policy
We may update this Privacy Policy when the application, its services or applicable requirements change.
The updated policy will be published at https://packncamp.com/privacy, with its revision date.
Material changes may also be communicated through the application or other appropriate channels.
13. Contact
Data Controller: Sarp Süerdaş
Application: Pack'n'Camp
Country: Türkiye
Email: info@packncamp.com
Website: https://packncamp.com