Privacy Policy
This notice explains the current Auspivia preview’s beta-interest and feedback collection. Fictional astrology examples do not constitute personalised reports.
Who is responsible for your data
Auspivia is the name of this planning and date-selection preview. The person or organisation responsible for its personal data processing must be identified below.
[REQUIRED BEFORE PUBLICATION: operator’s legal name, business/contact address and applicable jurisdiction.]
[REQUIRED BEFORE PUBLICATION: working privacy contact email or other monitored contact channel. Add a data protection officer or representative contact only if applicable.]
[REQUIRED BEFORE PUBLICATION: policy effective date and last-reviewed date.]
Beta registration
If you request a beta invitation, the form asks for your email address and, optionally, whether you are interested in daily planning, date selection or both. These details are used to manage the interest list and communicate about early access. Registration expresses interest; it does not create an account, purchase a subscription or guarantee an invitation.
Providing your email is voluntary, but it is required to receive a beta invitation. Your planning form values and birth details are not attached to the registration submission.
[REQUIRED BEFORE PUBLICATION: confirm the lawful basis for beta registration and invitation communications, including any consent or withdrawal process that applies.]
Feedback collection
The feedback form asks which workflow you tried: planning a day/week, checking one date or finding dates. You may give a rating, a comment, or both; at least one is required. Feedback is used to understand and improve the preview. The form does not request your email address or birth information.
Please do not include birth details, sensitive information, identifying details or personal astrology requests in a feedback comment. Free-text comments may contain personal data if you choose to include it. Feedback submission is optional and is not required to explore examples.
[REQUIRED BEFORE PUBLICATION: confirm the lawful basis for feedback processing and any legitimate interests relied upon, if applicable.]
Formspree and other service providers
When a collection form is configured and you submit it, its fields are sent to Formspree for processing and made available to the Auspivia operator through the configured submission and notification service. Formspree may process technical request information, such as an IP address, browser information and timestamps, under its own privacy terms. A confirmation on this website means the service acknowledged the request; it does not guarantee notification-email delivery.
The operator’s notification mailbox and any authorised exports or backups can hold additional copies. The website is hosted using Cloudflare Workers. Hosting and security services may process technical request information to deliver and protect the site.
[REQUIRED BEFORE PUBLICATION: confirm the operator’s actual provider/recipient list, mailbox provider, access arrangements and any exports or additional sharing. Confirm applicable processing locations and safeguards for transfers outside the user’s country, including any EEA transfers. Do not assume a particular transfer mechanism is in place.]
How long information is kept
Retention must reflect the purpose of each record and any applicable obligations. No retention period has yet been supplied for this draft. The operator must specify the periods or clear decision criteria below before publication.
[REQUIRED BEFORE PUBLICATION: beta-interest retention period or criteria, when the period starts, and what happens when an invitation is declined, interest is withdrawn or the beta ends.]
[REQUIRED BEFORE PUBLICATION: feedback retention period or criteria and the process for deleting or anonymising comments that contain personal data.]
[REQUIRED BEFORE PUBLICATION: retention and deletion arrangements for Formspree submissions, notification emails, exports/backups and hosting/security records, including any legally required exceptions. Verify actual provider settings; deleting one copy may not remove all copies.]
Example inputs, browser storage and analytics
The current preview uses fixed fictional scenarios and precomputed practical-only examples. Editable planning and optional birth-profile fields stay in the current page’s memory; they do not personalise the fictional story and are not included in beta or feedback submissions. Leaving or refreshing the page clears these advice drafts. No persistent advice storage or live personal report service is enabled by this preview.
An optional analytics adapter supports workflow and collection events without attaching email addresses, comments, birth details or form values. Analytics is disabled in the tracked default configuration; the deployed settings must be confirmed rather than assumed. If enabled, a separate web-analytics service may process technical usage information under its own terms.
[REQUIRED BEFORE PUBLICATION: confirm deployed analytics/cookie settings, any enabled analytics provider, its purposes and retention, and any consent or opt-out choices that apply. Update this notice before changing how personal advice inputs are processed.]
Request access, correction or deletion
Depending on the law that applies, you may request confirmation of whether your personal data is held, access to a copy, correction of inaccurate information or deletion. You may also have rights to restrict processing, object, receive portable data or withdraw consent where processing relies on consent. These rights have legal conditions; deletion may be limited where information must be kept for a lawful reason.
Use the privacy contact in the operator section to request access or deletion, or to stop receiving beta invitations. Identify whether your request concerns beta registration or feedback. For registration, the email you used can help locate the record; for feedback, an approximate date and workflow may help. Do not send birth details or unnecessary sensitive documents. Proportionate identity checks may be needed to protect your information.
The operator must review relevant copies held in Formspree and its own systems when handling a request, explain any applicable retention exception, and respond within the timeframe required by the applicable law.
[REQUIRED BEFORE PUBLICATION: supply and test the privacy contact channel and the operator’s request-handling process. This draft does not provide a working access/deletion contact yet.]
Questions, complaints and policy updates
You can contact the operator about privacy questions using the contact channel above. Where applicable, you can complain to a competent data protection authority, including one in the place where you live or work. Changes to collection purposes or providers should be reflected in an updated notice.
[REQUIRED BEFORE PUBLICATION: identify the relevant supervisory authority and its official contact/complaint link, as applicable. Complete the policy dates and verify that this notice matches the service actually offered.]