Peregra by Elseward
Privacy Policy
Last updated: 25 August 2026
This policy explains how Peregra accesses, uses, stores and shares information. Peregra is developed and operated by Craig Rutter under the Elseward brand. Questions or privacy requests can be sent to privacy@peregra.co.uk.
Information stored on the iPad
Peregra stores the content needed to provide its canvas features locally on the user's iPad. This may include:
- classes, reusable courses, topics, lesson canvases and colour choices;
- Apple Pencil drawings, inserted objects, imported resources and rendered document pages;
- page size, orientation, templates, bookmarks and recent canvas position;
- Google link metadata, including course IDs, Drive file IDs, Classroom material or assignment IDs, file names, folder names and update dates.
Google authentication credentials are stored using the iOS Keychain. Peregra does not include advertising or third-party behavioural analytics in the current build.
Google user data
Google features are optional. When a teacher connects Google, Peregra may access the following information for the purposes shown:
- Basic account identity: name and email address, to identify the connected account.
- Classroom courses: active courses taught by the user, so the teacher can create or link local Peregra classes.
- Selected Drive files: resources the teacher chooses through Google Picker, so the selected file can be imported to a canvas.
- A teacher-confirmed Drive course folder: file and folder names, types, sizes and supported resource contents inside the folder the teacher explicitly confirms with Use this folder, so Peregra can propose an editable course.
- Drive files created with Peregra: PDFs the teacher exports, so Peregra can create or update them.
- Temporary conversion copies: when a selected course resource is a supported PowerPoint or Word file, Peregra creates a named temporary Google Slides or Docs copy, exports it as PDF and removes the temporary copy.
- Classroom topics, materials and assignments: to create a topic or publish and update a PDF material or assignment when the teacher explicitly requests it.
Single-file import and export use the limited drive.file permission. Bring in a course separately requests drive.readonly, which technically permits read-only access across the chosen Google account. Peregra limits its interface and processing to the teaching folder the teacher explicitly confirms and its descendants; it does not provide whole-account search or silently scan the account. This separate token is short-lived, is not saved as a refresh token and does not replace the account connected to Classroom.
Bringing in a course
Peregra first checks names, folder structure, file types and sizes in the confirmed folder. Resource contents are accessed only after the teacher chooses Prepare and organise resources. Matching uses folder names, filenames, lesson prefixes and available document metadata on the iPad. Peregra shows an editable proposal and creates no course until the teacher confirms Create course.
Original Drive files are not renamed, moved, changed or deleted. Working copies and converted PDFs are held temporarily on the iPad during review. Approved resources are retained locally in the reusable course; abandoned temporary working copies are discarded. Teachers should select teaching-resource folders only and should not select folders containing pupil work or personal information.
How Google data is used and shared
Google user data is used only to provide the Google-connected feature selected by the teacher. Peregra does not sell Google user data, use it for advertising, or disclose it to unrelated third parties.
The app does not currently send canvas content or Google user data to an Elseward-operated cloud server. Information is stored locally and is sent to Google only when needed for sign-in, a selected import, disclosed temporary document conversion, a Drive export/update, course synchronisation, or a Classroom action requested by the teacher.
Peregra's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Lawful purpose and retention
Information is processed to provide features requested by the user, to keep the app working securely, and to support the legitimate operation and improvement of the private beta. Confirmed courses and resources remain on the iPad until the user deletes them or removes the app. Saved Classroom credentials remain in Keychain until they expire, are revoked, or the user disconnects Google. The separate course-folder token is not retained after the selected operation.
Files and materials created in Google remain subject to the user's Google Workspace or Google Account settings and retention controls.
Security
Peregra uses Apple's application sandbox and Keychain for local credential protection, encrypted HTTPS connections for Google API requests, and narrowly scoped Google permissions. No system can be guaranteed completely secure; users should keep iPadOS updated and protect their device and Google account.
Your choices and rights
Users can delete local content in Peregra, disconnect Google, revoke access in their Google Account, and delete exported files or Classroom posts in Google. See the data deletion instructions.
Depending on the circumstances, UK data-protection law may provide rights to be informed, access information, correct inaccurate information, erase information, restrict or object to processing, and data portability. Send a request to privacy@peregra.co.uk. You may also raise a concern with the UK Information Commissioner's Office at ico.org.uk.
Children and school use
Peregra is not directed to children and pupils do not sign in. Teachers and schools remain responsible for deciding what lesson content is imported or published and for following their organisation's policies, copyright rules and data-protection procedures. New roster, rewards or management-information-system features will require a separate privacy and data-protection review before release.
Changes and contact
This policy may change as Peregra develops. Material changes will be dated on this page. Privacy enquiries: privacy@peregra.co.uk. General support: support@peregra.co.uk.